Advanced Search

Thanks Wischi, now works like it should.
I had not thought to go back to the ini file ! Getting old !

Not sure what you meant by "popup in the right hand corner".
My install starts clean without a pop-up.

I do get a warning when the code reaches the tool change that the bell is not connected (it isn't).
I will soon get a bell, or de-select it.

Hey there, JB-Motoring,

how did you manage to get the encoders in working order? Did you end up buying 5 IBV boxes? From past experiences EXE ones work better, but they are rather expensive. Or did you somehow directly connect them to the 7i97T card?

I have a similar machine I am looking to retrofit (DMU 50M, same encoders) and am wondering what hardware to buy.

Thanks.

The more I think about this, It could very well be the PWM conversion onboard the EC500 is just to slow. It may not be able to keep up with the CSS speed adjustments. Any idea how to set the EC500 to output PWM instead and I'll hook up a PWM to Analog conversion board to test it. I know in the documentation you can switch it using Mach3 software.

forum.linuxcnc.org/10-advanced-configura...glass-scale-feedback

Reading Work Coordinates When Loading a New NGC File  

When loading a new `.ngc` file in LinuxCNC, is it possible to read the work coordinates at that stage? Since the G-code has not been executed yet, the work coordinates might not be applied.  

Would it be possible to create a custom button, similar to "WCS Sync," that reads the `.ngc` file and sends commands like `G55` to MDI?  

Has anyone implemented something similar, or does LinuxCNC provide a built-in way to achieve this? Any insights or suggestions would be greatly appreciated.

Thanks!

I had been using it without much thought, but it seems better to remove G43H0 G54.
The tool length offset is unintentionally canceled, and the work coordinate system switches."