Advanced Search

The outputs are probably NPN which means your load needs to go between  the output pin and ground and common will need to be +24V

Hi Grotius,
I have been trying to find out the physical meaning of curvature and how to imagin G2 continuity in higher dimensions. I have not been having much success in that endavour.
This recently published paper I have found claims to use splines for filleting in 5 axis: A Novel Local Smoothing Method for Five-Axis
Machining With Time-Synchronization
Feedrate Scheduling ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=9085380

I was hoping for some help to find some references on how to do filleting in higher dimensions to reduce the tangential jerk.

-automata

Im Still working away modifying the Hal file.

Went back to review RotarySMP's wonderful Maho thread and 90% of the answers i needed were right there in his HAL file.
I am stuck on a couple of points though.

I have copied the 2 sections below out of Mark's HAL and done what i thought were the required modifications.  The modified version of the code i found to suit the Deckel is half in german which is tough for a simple Aussie.

What files will these pins refer back to when opening linux CNC? at the moment unless i comment out like below it throws an error upon opening e.g. cant find pin FP4-gearbox.reducer-motor.
This will be due to a different naming syntax between the below and whatever file it references i would assume but i need to know what it is so i can modify correctly.


# --- GEARBOX CONTROL ---
#net sig_return_actual_speed     FP4-gearbox.spindle-speed-out   => motion.spindle-speed-in
#net sig_return_spindle-at-speed FP4-gearbox.spindle-at-speed    => motion.spindle-at-speed
#net sig_stop_spindle            FP4-gearbox.stop-spindle        => motion.spindle-on
#net set-gear-shift-start        FP4-gearbox.start-gear-shift    => hm2_5i25.0.7i84.0.2.output-05
#net activate-vorgelege_motor      FP4-gearbox.reducer-motor       => hm2_7i96s.0.7i84.0.0.output-00
#net activate-block2_motor      FP4-gearbox.midrange-motor      => hm2_7i96s.0.7i84.0.0.output-01
#net set-shaft-motor-lowspeed    FP4-gearbox.motor-lowspeed      => hm2_7i96s.0.7i84.0.0.output-03
#net activate-block1_motor  FP4-gearbox.input-stage-motor   => hm2_7i96s.0.7i84.0.0.output-02
net activate-spindle-twitch-cw  FP4-gearbox.twitch-cw           => hm2_7i96s.0.7i84.0.0.output-04
net activate-spindle-twitch-ccw FP4-gearbox.twitch-ccw          => hm2_7i96s.0.7i84.0.0.output-05

# --- GEARBOX CONTROL ---
#net sig_get_commanded_speed  FP4-gearbox.spindle-speed-in-abs    <= motion.spindle-speed-out-abs
#net sig_spindle_status       FP4-gearbox.spindle-stopped     <= hm2_5i25.0.7i84.0.2.input-19
#net sig_vorgelege_vorne        FP4-gearbox.reducer-front        <= hm2_7i96s.0.inm.00.input-02
#net sig_vorgelege_mitte        FP4-gearbox.reducer-center       <= hm2_7i96s.0.inm.00.input-03
#net sig_vorgelege_hinten       FP4-gearbox.reducer-back      <= hm2_7i96s.0.inm.00.input-04

#net sig_block2_vorne         FP4-gearbox.middle-front         <= hm2_7i96s.0.inm.00.input-05
#net sig_block2_mitte         FP4-gearbox.middle-center        <= hm2_7i96s.0.inm.00.input-06
#net sig_block2_hinten       FP4-gearbox.middle-back       <= hm2_7i96s.0.inm.00.input-07

#net sig_block1_vorne           FP4-gearbox.input-front         <= hm2_7i96s.0.inm.00.input-08
#net sig_block1_mitte          FP4-gearbox.input-center         <= hm2_7i96s.0.inm.00.input-09
#net sig_block1_hinten         FP4-gearbox.input-back       <= hm2_7i96s.0.inm.00.input-10

Thanks for being patient with me.

tommylight wrote:

Are the motors brushed DC or brushless, or steppers?
If brushed DC there are also "extreme limits" that also cut power to drives.

Well I’m getting rid of anything and everything VFD related here lol.  Its a 100% stepper system.  The drives are cheap all though the new spindle drive is pretty nice just is difficult to understand how to configure it and all.  I’m pretty sure the spindle drive has some kind of limits functionality that can be programed into it, maybe even an estop command can be sent to it.  As far the other drives they only take power and step/dir input.  

I’m staring to think go with kill all drive drives power including spindle drive but leave the control board running and also get it to receive the estop signal.

Also do you know of any good 220v relays that are din mountable that don’t hum loudly when they are on? 

Thanks

i bought this IO module and i have problem with the output ports, i am using out16,15,14 i connected 24V to power supply of this group ( second group ) and i connect my load to the pins and when i try to sent high signal the LED in the module turns on but there is no voltage on the output pin , when i measure the voltage its 0 on high signal and when low signal it gives about 7V

Bump as it seems it has been missed.

All drives that take step/dir or pulse/dir signals work with Mesa 7i96S and other Mesa boards, be it single ended or differential inputs as Mesa can do both.
And you can add a Mesa 7i85S to 7i96S and have 4 more stepper outputs, add a 7i84 and get 32 inputs and 16 outputs.
If you do add 7i85S, get also the required cable.
7i84 can be wired with a normal LAN cable cut in half.

In general, never ever switch of the DC side of things.
Leaving the controller on even on E-stop is a good advice as you can check what went wrong.
E-stop should kill power to drives and spindle, and must be considered as the last resort in case something goes wrong.
Are the motors brushed DC or brushless, or steppers?
If brushed DC there are also "extreme limits" that also cut power to drives.

For drivers with only one power input, I would kill the power input to each drive with estop.

Cutting power to control board only is not reliable way. What if stepper driver is faulty and runs away with no input? Need to cut power to the stepper driver.

Hi all
Not sure this is the right place to post my problem. So, moderators, feel free to move it to the correct place.

I have a small three axis router that has a tool length sensor sitting idle for the last few years. I want to make use of it. So digging up the forums, I came accross "examples/sample-configs/sim/axis/remap/manual-toolchange-with-tool-length-switch" to get familiar with it. This "sim" just worked on 2.8.4. runing debian buster.

I upgraded to bookworm and 2.9.2. Same "manual-toolchange-with-tool-length-switch" does not work anymore. OK, using gitzip, I downloaded the latest source from github , unpacked in a new directory and ran it again, to no avail. I positively verified that all files downloaded *ARE* really the same as on  github .

os: debian bookworm
LCNC: 2.9.2
user/group cnc:users
owner/group of manual-toolchange-with-tool-length-switch: cnc:users
when I run: "linuxcnc manualtoolchange.ini", I get the following errors (full messages attached)

• [GladeVCP.QTVCP.QT_ISTAT][WARNING]  INI Parsing Error, No DEFAULT_LINEAR_VELOCITY Entry in DISPLAY, Using: 25 (qt_istat.py:532)
  ... couple of similar warnings more
  Guess, as warning only ignorable
• [GladeVCP][DEBUG]  **** GLADE VCP INFO:    Not a builder project, trying to load as a lib glade project (gladevcp:205)
  Problem?
• gtk-builder-error-quark: manualtoolchange.ui:13:38 Invalid property: HAL_Table.n_rows (11)
  Problem?
• **** GLADE VCP ERROR:    With xml file: manualtoolchange.ui : 'gi.repository.Gtk' object has no attribute 'glade'
  Guess, that's where it fails?
• <commandline>:0: gladevcp exited without becoming ready
  Guess, my guess confirmed?
• Embeded tab command "halcmd loadusr -Wn gladevcp gladevcp -c gladevcp -d -x 79691919 -u python/gladevcp-handler.py manualtoolchange.ui" exited with error: 1
  

How can I get this up and running again?
Any help greatly appreciated

greez chris




 

Hi, I am building a CNC adhesive dispenser. Two closed loop stepper motors will be used to control the X-axis, one will be used to control the Y-axis and one to control the Z-axis. Here are the 4 motors: P Series Nema 17 Closed Loop Stepper Motor 72Ncm(101.96oz.in) with Encoder 1000PPR(4000CPR) - 17E1K-07|STEPPERONLINE (omc-stepperonline.com) And here are the 4 drivers: Closed Loop Stepper Driver V4.1 0-8.0A 24-48VDC for Nema 17, 23, 24 Stepper Motor - CL57T-V41|STEPPERONLINE (omc-stepperonline.com) I was wondering if these motors and drivers will be compatible to interface with MESA 7i96s: eusurplus.com/index.php?route=product/product&product_id=159 and LinuxCNC. And additionally if this is the most suitable MESA card choice for my build (note that I might also need to connect up an additional motor and driver). I am working on doing this for my company (budget isn’t an issue) but I am very hesitant to buy anything without being certain that it is the right choice. And yes I have read the description that the 7i96s can control up to 5 stepper motors, I just wanted some extra clarification from someone with more experience on the topic as I am only a couple weeks deep into learning about CNC.Any help would be greatly appreciated.

Check dmesg output and search for parport.
Check lspci (-v), which ports are listed for the card.

is this the same card: forum.linuxcnc.org/16-stepconf-wizard/46...card-ax99100?start=0

pippin88 wrote:

The ideal setup is estop kills the servo drive motor power input, and spindle power input.
Most servo drives have two power inputs: control power, and motor power

Estop circuit should signal to Linuxcnc that estop has occurred.

Most servo drives will have a digital input that can be configured as estop/fault

 

Ok well on the new spindle drive that I’m working with it has something in the manual that talks about estop signal but there’s no documentation on how to use it.  The other drives for the stepper motors to the axis's XYZ have no such thing.  I really think my machine was originally so old and cheap that the stepper drives didn’t have a control power option built in when manufactured, so it was designed to kill the control board all together instead.  I might have to do the same thing here with this estop or do something at least with figuring out how to signal the spindle drive to receive the estop alert then on the control board signal it the estop function but not completely kill the power to it?

I posted this on Facebook's LinuxCNC users but figured I'd try here too:

I recently purchased a parallel port based 6040 router and at the recommendation of a coworker I'm trying to run LinuxCNC to control it and finding it problematic. I'm using a Dell Inspiron 3668 with a StarTech PCIe card (I only have PCIe slots) with an AX99100 based port. Latency appears to be about 19000, although it's mostly not more than 4000.

I downloaded the Linux driver from Asix websites, and made it, and then did the install as they suggested. It seems to install on base address 0xd010. After install of the driver LinuxCNC no longer complains about the port not being configured. I turn ESTOP off and turn on the machine (via the interface) and nothing happens. I put an o-scope on pins 2 and 3 (X direction and step) and they look like they are low even when commanded to move on the X-axis. So it looks like it's not the router here but something weird about LinuxCNC or the parallel port.

Also worth adding that for whatever reason I had rmmod the parport_pc module and reinstall after a reboot..

Any thoughts on the next step diagnose and fix?
 

Askjerry wrote:

RODW -> The pin you specified requests the machine to home, not return when homed.

ACIERA ->

I put a line in the custom_postgui.hal file...  <= motion.is.all.homed but when I run it, I get the following...

Debug File Information:
custom_postgui.hal :70: motion.is-all-homed does not exist.

The text you referred to says it should exist... but it's not there. I may have to save my configuration and update...
this is Axis 2.7.14 on this machine.


 
 

"Update: I could NOT find the signal for all homed... or any variant of it. I can find individual axis... but not "all"."
-> combine all individual axes with an and component to get all_homed bit should work

Another idea: create a simple python hal component that runs the commands after all axes are homed.
I used that in my lathe setup. It has a serial port controlled tool changer and the hal component handles tool changes. But the relevant part here is that you can wait in a loop that all axes are homed and then execute a command. Then sleep forever.
Code is here: forum.linuxcnc.org/24-hal-components/364...trol?start=20#151315