Advanced Search

After a couple of hours fiddiling with my vfd to get it working using modbus my pi4 died on me... not really sure what happened it just suddenly went black so i purschased a mini pc witth a celeron j4125 with dual ethernet ports.

Ah, good to know. Thank you for the reply (and for Remora)!

Those are just templates, you need to define and edit for your machines sensors and requirements. My machine uses two sensors one for clamped and one for released because it's only reporting when the plunger is actual at the released or clamped height. If you're have just one sensor that's high or low, than you may need to remove a line from the macro. The best thing to do is to map everything out and then review your sensors and the macro sensor inputs and ensure everything is accounted for.

Hmm.. I see. I checked the clamp tool.ngc? I see that the script waits for the sensor to be high. As I connected the "release" sensor, my sensor is high when the spindle is released and not when the tool is clamped. Could this be the issue?

Does PB use two different scripts for releasing (which works) and clamping (which fails in my case)? Anyway, it looks like I need to invert the value in the script. However, then the debug text in the script should say "(abort, Failed to clamp  tool) ; abort if the sensor does not activate in 2 seconds". Correct?

EDIT: Got it working by changing the LT to GT (waiting for it to be low). Is there a current list about the expected signals in PB? Like ATC drawbar to be connected to motion.digital-out-02, sensor to x, another sensor to y etc.