Advanced Search

Linuxcnc Version?
IMO this is a bug in the source code, i have this error disabled in the codebase I use for work

I understand your concern now. I only use probing to find my Z height. X/Y is handled by a crosshair laser. Once centered on the starting position of the cut, a button attached to g-code computes the actual position by applying offsets for both X and Y to the current location of the laser. Offsets are stored in my INI file and can be changed if needed without touching the code.

Er, no. It’s not that simple; LinuxCNC isn’t plug-and-play. If you don’t have any prior knowledge, you should put the A6 aside for now and start with simple stepper motors. You’ll first need to learn how the system works and what each component does. With EtherCAT, you’re moving beyond the hobbyist level, and even professionals sometimes find it frustrating.

Hakan wrote:

In what way do you see 2x50k as a better way than 1x100k?

 

Keeps the high power stuff more isolated in case of wire break/short, making it much safer.
I always put those 3 resistors on the plasma source of in a box behind it.

yes, mesaflash still says 5i25 not found

 

Did you try running mesaflash after running LinuxCNC?
 

The problem isn't the 50ms, it's that during that time the machine is *moving*. I.e. where you home depends on the bouncing of the sensor, which means it's unpredictable, which means every other position is also unreliable.
If you "hit" on the first contact, instead of waiting for the physics to settle down, you get a more predictable "moment" when the machine is in the known state.
You'd think it wouldn't matter, but I've seen my probe go measurably past the right spot before it "hits", and my probing routines actually probe in both directions (G38.2 then G38.4, and take the average) to try to eliminate this overshoot.
With a "first hit" debouncer, you could set the debounce time to 3 seconds and still get the right value.

I don't see a problem with de-bouncing a signal when homing since the purpose of homing is to put the machine in a known state and stop before doing anything else. If that takes an extra 50ms to insure the starting position of all axes, it is a non sequitur since the result is the machine is stopped. It might be a minor issues when hitting a limit switch while machining, but I'd rather error on fact rather than bounce.

Just my two cents worth.

Flex GUI has nothing to do with halui.

This is my code for my BP external Estop.
JT

And you can now set the jog increments using the keyboard.
gnipsel.com/linuxcnc/flexgui/ini.html#keyboard-shortcuts

JT

That's a LinuxCNC issue the joints are numbered 0-8 for xyzabcuvw so c is joint 5.

Maybe a jog axis button would work. I'd have to test.

JT

This may not help but this 2017 post shows how to update a gmoccappy screen handler from gcode which sounds like your problem 1
forum.linuxcnc.org/plasma-laser/32691-settings-from-g-code-file
Here different values are set using an analog input which is decoded and used to modify screen elements. eg 900 and 999 change screen settings.

kind of weird that i can see it talking to a 5i25 in the error file

still cant seem to find the board 

Yes, you need to install firmware that matches the 7I77

You first need to download the 5i25.zip from

 www.mesanet.com/software/parallel/5i25.zip

unzip and then change to the configs/hostmot2 directory and then

sudo mesaflash --device 5i25 --write 5i25_7i77x2.bit --reload