Advanced Search

hello,

Some time ago, Sebastian did the config ..

regards
 

Now that you confirm this feature is supported and should work. Which would have been good to know in the first response. I can dig deeper, I assume this is exposed in the hal, correct? Is there a special condition or hal pin for jog while within soft limits? While, there is tons of ductiontation, it is hard to find it when you don't know what you are looking for. If I had to guess, the issue is that it's not a direct EtherCAT issue (has it just a HAL component), but rather a dependency on the configuration from a configuration wizard.

I do agree a machine should never be beyond the limits, but if the logic is just a straight greater than or less than than I think there could be an edge case that needs better logic. Maybe this has already been addressed. I have 23-bit encoders, so that is > 8.3 million per rev. So even with the translation to machine units there is a very very small "error" factor. Meaning the "actual" location will fluctuate (bad word choice) with no movement by this very small amount. This can make the axis and/or joint appear its beyond a soft-limit. For instance, when I zero the DRO will remain "zero" but the "-" will flash on and off. Again, maybe all this has been addressed.

Additionally, I have found incorrect and inaccurate details regarding the setup of absolute encoders and how LCNC handles them in both document and forum searches. I am more than willing to contribute back, but "guidance" would be more helpful.

Lastly, tommylight  Thanks for all your efforts as a moderator; it's a thankless task.

On my opinion, better not to use USB communication. I had USB joystic connected to CNC, if USB lost communication - need to restart linuxcnc to access it one more time. USB - it's not for device control - only for file exchange - on my opinion.

Linux cnc supports EtherCAT interface. Try to make your device with communication protocol as EtherCAT slave. It will be more professional device in this case.

I have a DIY RouterMill that I've been fighting with for many years. I recently ditched MACH3 and paraports for the MESA 6i25 <=> 7i76u combo.
After flashing the 6i25 with the 5i25/7i76u x 2 bitfile and updating LCNC to 2.94 and configuring with PNCConf, all of the steppers worked as expected and were tuned for optimum movements for my machine. Turning my attention to the INPUTS, based on what I understand from the docs, the INPUTS are sinking so I configured the machine with all INPUTS as follows:

VF(24v) -> switch(NC) -> 7i76.0.0.input_nn

After starting LCNC, I notice that the ESTOP was triggered but, the button was not closed. Checking the INPUT pins with halshow, I could see that the board was showing all INPUTS as TRUE, therefore I changes all of the INPUTS to input-nn-not and restarted LCNC. Now all of the INPUTS seemed to respond correctly. When I attempted a HOME_ALL, the Z moved to positive, so I reconfigured it to home negative with PNCConf. That worked and after more reading and adjusting of some parameters, I got the Z homing correctly backing off the trigger position by .050 in.  Then I directed my attention to X.  However, I had to adjust a few more parameters for the X axis then restarted LCNC. *)#$!! All of the inputs had switched and were now reporting as TRUE. Frustrated I changed all INPUTS back to input-00 and restarted LCNC. With this session I was able to get both the Z and X axes to home correctly, however, Y was now the problem child as it would not back off the trigger position. After several attempts I finally decided to swap DIR-/DIR+ at the microstepper so the Y config was exactly as the X config. (My Y axis is at the back of my machine so I had reversed the motor in the config for correct movement). After making the change and while running PNCConf I confirmed that the Y axis was now responding correctly then proceeded to resume verifying  the HOME ALL function, The attempt failed, so I tweaked the HOME parameters but, when I restarted LCNC all of the INPUTS had again switched their state (*)#$!!,*)#$!!). More bizarre was that now no matter how I set the PROBE input (input-nn or input-nn-not) the halshow remained the same.  After several additional restarts, the input pins again flipped the input state.

At this point I'm half inclined to suspect the 7i76 board as it has one INPUT, input-04, that is always stuck in the same status in halshow much as the PROBE input is now responding.

If anyone has any ideas that I can try, I would greatly appreciated the support.

Regards,
Stephen

I use Gmail just like Todd, and there are no emails in any folder.