Yes, there will be synchronized movement as its all controlled by Linuxcnc on the single servo thread

halui.mode.teleop bit inpin for requesting coordinated jog mode 

tommylight wrote:

That would be redundant as LinuxCNC is the motion controller.
In short:
-buy a Mesa 7i96S and a THCAD

I was wondering if I should buy direclty the 7i95T as it has all needed i/o and encoder feedbacks for up to 6 axis.
What you suggest ?

I plan to set up a separate head in the future for plasma and who knows maybe even a spindle for drilling.

looking forward to your TP2. I would consider a few jerks in feed override an acceptable loss for using override as long as the max degredation of velocity is trapezoidal. Even a slight violation of max acceleration of an axis during the feed override is an acceptable degradation in my opinion.

If you are looking for a discussion on switchkins, I can help. When I first wrote switchkins, I could not think of an easy method to force a interpreter sync and yield type of queue buster which stops readahead. So looking at Fanuc and Hass, I added G12.1 and carried it through the complete chain of interpreter and motion. However dgarret came up with a much easier way to affect the queuebuster using M66 and remap which avoided touching so many files in the source tree for the switchkins feature.

For using axis limits during planning, the tool length which will become a parameter for the kinematics (including kinematics on the user side), could be carried through HAL or as a status variable from the #variables (#5401 to #5409).
I am looking forward to your release.
-automata

I wonder if there are two interfaces. For example, the X and Y axes are controlled by the Ethercat and the Z axis is controlled by a Mesa card, will there be synchronized movements?

scsmith1451 wrote:

I uninstalled Glade and then reinstalled it. The issue still persists.

I can't help you, but have a suggestion.
The "object has no attribute" is python's error and means "python can not finds", probably due bad path.
For me often helps to install python package in both ways, deb package and pip package.

Yes. When I try to upgrade,I one part of the error message reads:  raspi-firmware: missing /boot/firmware, did you forget to mount it?.
I cannot post full message because the system clock is wrong so internet is not working.........

I'm using the physical keyboard keys to control jogging.

Checking halui.mode.is-manual = FALSE. I attempted to set it to TRUE but halshow reported that the parameter is not writable.

Is there a way to force this pin to be high?

Regards,

Sometimes a custom component simplifies your hal file. Here is my solution for a similar problem where there are two belts each with 4 positions. But because it's not possible for both belts to use the same position, it comes down to the same problem you have. For the ratios, I just ran the spindle on each belt combination and read the actual rpm with a cheap laser tacho and did some maths. But I did not have levers, and made a panel for qtdragon which Chris "borrowed" for the qtdragon docs.

github.com/rodw-au/vmnmillqt/blob/main/scalebelts.comp

Sean Drummond did a really nice diagram of a 7i96s which you can grab over at plasmaspider  plasmaspider.com/viewtopic.php?p=231679#p231679  

If you want a diagram you can't go better. I usually just create a table of all the pins and where that go. Its better to do it in a word document rather than a spreadsheet so you can add more freeform text/

Update: I uninstalled Glade and then reinstalled it. The issue still persists.

The errors thrown during launch not reads:

tool_mmap_user(): tool mmap not available
poll(): continuing without tool mmap data
gtk-builder-error-quark: crosshair_panel.glade:12:34 Invalid property: HAL_Table.n-rows (11)
**** GLADE VCP ERROR: With xml file: crosshair_panel.glade : 'gi.repository.Gtk' object has no attribute 'glade'

when launched from the panel from the command line:

$ gladevcp crosshair_panel.glade

Maybe I need to reinstall linuxcnc?

Regards,

Thanks, I'll give it a try.

The ethercat thread and linuxcnc thread should be the same, On startup, the 2 thread synchronise. If you use the ethercat drivers on the linuxcnc-ethercat github page, this has been improved with changes to linuxcnc and the ethercat master to improve this sync. You probably need master to get these changes.

rubes wrote:

that is what everyone gas been telling me (the part about home_ignore_limits). that other line i dont understand because i am not a HAL programmer. but there is probly several ways to accomplish this. if your one line per axis accomplishes the same thing, it is certainly more elegant and efficient.
 

Personally, I like writing statements on separate lines. I find its easier to understand and maintain