Advanced Search

I'm now running into exactly the same problem and aren't at all keen on having to resort to a clean install.

Hopefully somebody has an explanation and an easier solution......

MaHa wrote:

Now found the error.

5401-5409 - Currently applied tool length offset for X, Y, Z, A, B, C, U, V & W. Set by G43/G43.1/G43.2, cleared by G49. Volatile.

So i don't have access to toollength #5403 anymore, except i use G43/G49 to load the variables.
Thats f*** crapy update

Why i am upset?
Since version 2.5 this parameter are in use, now it changed overnight, instead creating a new set of parameter, if someone needs that. Like that it breaks configurations with probing routines and parts, when offsets are set wrong, without warning. And i am not going to set G43/G49 in probing routines. The only place to do that is in gcode. Don't want this risk for crash, when unwanted, toollength is cancelled. 

Can anyone else confirm this?
And more importantly, if true, how this happened?

Now found the error.

5401-5409 - Currently applied tool length offset for X, Y, Z, A, B, C, U, V & W. Set by G43/G43.1/G43.2, cleared by G49. Volatile.

So i don't have access to toollength #5403 anymore, except i use G43/G49 to load the variables.
Thats f*** crapy update

Why i am upset?
Since version 2.5 this parameter are in use, now it changed overnight, instead creating a new set of parameter, if someone needs that. Like that it breaks configurations with probing routines and parts, when offsets are set wrong, without warning. And i am not going to set G43/G49 in probing routines. The only place to do that is in gcode. Don't want this risk for crash, when unwanted, toollength is cancelled. 

Thanks Benb, I did figure out the e stop input and did tie the input into my ui e stop.

I guess it’s not a true e stop as I’m only killing the enable, but everything does work the way I want it to.

I pasted all my configuration files into my build thread.

This iso installation is more than 1 year old. The other day, there was an update for another software available, i did sudo apt update and sudo apt dist-upgrade. Some updates coming in, afterwards linuxcnc was 2.9.9
Since then, my long time working probing routines set z-offset somewhere (at least) above the part.
 

How did you install 2.9.9? The ISO installer is still a work in progress. Not that that should matter for internal code 

What version of linuxcnc are you using?

There are a couple issues here:

1. 7I90 J1 pinout has swapped TX/RX lines since its intended for use as a sserial remote, not a sserial host
(fixable with cable  wiring changes)

2. More serious: the current hostmot2 driver does not enumerate sserial ports on local I/O pins
and unfortunately the J1 serial interface on the 7I90 is on local IO (LIO) pins so will not be seen.

Easiest solution would be to add a SP491 etc to some GPIO pins
 

Can you please test the same conditions, but without using glade?
Thank you.

Gateway, set it to 10.10.10.1 as in the how to, or just delete it as it is not used in this case when you set it for local network use, that you did not set, and that is OK if you do not use any other network but should be set nontheless.
Also, did you set the jumpers on Mesa board for 10.10.10.10? Default is 192.168.1.121, see Mesa manual.

Hello, can anyone help me? I'm using a Mesa 7i90hd card in epp mode and I want to connect a 7i84u serial card to it, but using the serial port J1 of the 7i90. Can you help me with the bit file? also p2 connector is connected the 7i98 card. Thanks.

I was able to work on the machine having the jogging problems today. I forgot/ran out of time to try the fix on it. But I was able to notice a situation that seems to always cause the sticking problem. Any time that there is an alarm or pop-up message window left open at the bottom right corner of the screen, the jog keys will stick.

Did the update to 2.9.9 change behaviour of G38 ? First i blamed my cam and redid the job, but its definitely the probing. Finally had to do manual touch off.
How can i get back the behaviour pre this update?

No need to find an ancient board with a pci slot. PCIe to PCI adapter works also, here is my controller with 5i25, still working fine.
Adapter is "ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 04)".
Built into an old topfield 5100 case

 

Seems the component is setup to only handle a maximum of 16 messages:
github.com/LinuxCNC/linuxcnc/blob/master...nts/message.comp#L90

Note that there is an enhanced message component in master that supports up to 64 messages which you might be able to install on your system using the 'halcompile' tool. (this tool will require installation of the 'linuxcnc-dev' package)
github.com/LinuxCNC/linuxcnc/blob/master...ponents/pushmsg.comp