Advanced Search

There is this bracket ']' to remove:


line 27
#<y_gap_o> = #<_ini[tool_slot_delta]y_gap>]


line 72
#<y_gap_i> = #<_ini[tool_slot_delta]y_gap>]

now

Good, thanks for verifying the servos are programmed appropriately.

Right now, your HLFB pins are HIGH (conducting) when the servos are enabled and OK.  Since you have the inputs connected to your amp-fault-in pins like:

LCNC thinks there is a fault when the servos are saying everything is OK.  Here's the LCNC manual section (motion):

joint.N.amp-fault-in IN BIT should be driven TRUE if an external fault is detected with the amplifier for this joint.

Try changing the HLFB input pins to 'not' like so:
At that point, the joint.N.amp-fault-in pins should be HIGH when the servos are not enabled, and go LOW when they are enabled and OK.

Once you're at that point, you can test by pulling the encoder cable off the motors and see if it causes the amp-fault-in to go high (hopefully).

If you still need a delay we can work on that next.

I think the problem is, not using uppercase letter. This should work:

Y_GAP = -206

spumco wrote:

There is no perceptible rotor cogging when you spin them by hand. 

Nice to know, thank you for taking the time to explain that.

yes exactly

Did you add this to the .ini file, the  line with y_gap ?


[TOOL_SLOT_DELTA]
X = 0
Y = -111
Z = 0
y_gap = -206

now the first three slots work as usual, if I select the fourth one when returning the tool to one of the first three I get this error

Hello everyone,

I’m experiencing some odd behavior when jogging in the G54 coordinate system. When I jog from X0 Y0 to X100 Y0, the Y-axis deflects slightly, as if a small rotation or compensation is being applied. The final reported position is X100 Y0.084. The Z-axis is not affected. A similar issue occurs in the opposite direction: when I jog along the Y-axis, the X-axis also deflects. However, if I issue an MDI command to move to X100, the Y-axis remains unchanged, which is the expected behavior. When I switch to G55 or G56, everything works as intended—there is no coupling or linkage between the X and Y axes. I’ve attached a screenshot showing the issue: first I moved from X0 to X100 using an MDI command, then manually jogged back. You can clearly see the Y-axis deflection during the jog. I have already cleared all work coordinate systems, but the problem persists specifically with G54.

Any help would be greatly appreciated.
Greetings,
Sandro

 

I did setup the MSP software, And I just confirmed the pins again.

I modified the routine for unload and load, o315 and o 316 used. In .ini file the value for 'y_gap' should be 206, not 317 The diff shows the modification  


 

 
 

Are you sure spi works?
Apart from that, make sure the stm32 and the eeprom are in sync, that is, they both come from the same saving of "Save all files"
and that the firmware is compiled and downloaded. It doesn't hurt to do it one more time.
Power cycle the board to make sure both stm32 and lan9252 read the most recent data.
Right-click the mouse on the marked item and remove it. Scan for new boxes to make it reappear.
Also quit Twincat and start it.
All a bit extra cautious to make sure any old data/cache is eliminated.
 

LinuxCNC must have timed out I'll attach again hopefully.