Advanced Search

You should be able to debug spindle operation by using halshow
to look at the spindle pins as you set the spindle speed to different values
Important things to watch are:

hm2_7i76e.0.7i76.0.0.spinout-minlim  
hm2_7i76e.0.7i76.0.0.spinout-maxlim   
hm2_7i76e.0.7i76.0.0.spinout-scalemax 
hm2_7i76e.0.7i76.0.0.spinena-invert  

 hm2_7i76e.0.7i76.0.0.spinout
hm2_7i76e.0.7i76.0.0.spinena


Also make sure then the electrical connections are correct
(so you have 10V from SPIN+ to SPIN-)

I was able to correct the IP address
it doesn't work, I can set cw-cww-enable but no speed.
I am trying to update and it cannot find the linuxcnc repository , gives an error
I am using 2.9.5

Should I reinstall everything again?
I don't understand what is happening

Multiple Ethernet cards.
And Mesa always wired directly to the PC, not through HUB or Switch or VLAN.
Now that is out of the way, i have tested Mesa cards through cheap switches (non manageable) and it worked for me without issues for weeks at a time, but i would never run a production machine through it.
I do not know if EtherCAT works through any of those as i never tested this. But i have seen something used for EtherCAT redundancy several years back at a machine show, for some strange reason i did not pay attention.

Sorry i uploaded them twoce

Greetings ,
You guys are awesome BTW
I am working on a python logic script to control some switches, a button, and a couple encoders connected to the p1 connector of the Mesa 7i96s IO with 5vdc going to power the encoders. They are just simple switches wired one side to P1 input, the other side to ground. I have been working with ChatGPT to develop this script but it can only go so far. It really has trouble with the little details. (id; .get() set()) I don't totally understand it either and need some help. I have included my hal filses and the python script. Any and all help is greatly appreciated.

Hello!
I am attempting to compile the configurator but I'm running into an issue. 
To compile it needs "ethercat_master/tool/common.h"
I went to gitlab.com/etherlab.org/ethercat but that codebase does not contain a "common.h" file in the tool directory.
Any assistance on compiling would be appreciated.
 

unknown wrote:

that should give you enough with what you can do with mesa ethernet
 

That's not my concern. I remember hearing somewhere that the Mesa ethernet link takes over the whole interface, and prevents other traffic from using it too. Wherever I heard that, nothing was said about VLANs, so I assume they were using the physical interface. If the mesa link wants to take over the VLAN that's fine, but if it takes the whole physical interface in spite of VLANs being configured, that would be irritating.

I wasn't able to make the ethercat master use the vlan interface, only the physical.
On the other hand I don't really know what I am doing, so a test is advised.

I can no longer provide support nor able to provide update images do to external issues. Hopefully someone will jump in.

Past caring, you all the admins, have let this individual carry on way too long. I've tried contacting the admins, and starting a topic regarding the issues with the information the person has given. It's the community and the advice and information that is what concerns me. More than completely misplaced. 

As per the title, I'm wondering how a tool head will move when the active coordiante system is rotated via G10 L2 R- and a G2/G3 command is issued. Specifically because the docs say "The axis of the circle or helix must be parallel to the X, Y, or Z axis of the machine coordinate system." 

Case active plane = XY: this would seem to be the easieast to handle, but just to check, are I and J rotated to represent deviations in the rotated coordinate system or no?

Case active plane includes Z: this is trickier, because both options present apparent trouble. If the arc's axis is in the macine plane, say XZ, it seems to be impossible to use G2/3 in such a plane with a rotated coordinate system as the post-processor can't account for it and the tool would take a path different than desired. On the other hand, having the arc be in the X'Z plane (rotated), respects the path desired by the postprocessor but seems to be in contradiction with the docs.

I don't have a LinuxCNC machine installed so I can't do the practical experiment myself (I'm actually about to build a machine and I'm trying to understand the pros/cons of each system). Thanks in advance!

@langdons and unknown
I'm getting tired of this. I just deleted several of your posts that had absolutely nothing to do with the topic.

Yes, the sample file is set for a 10.10.10.10 IP address
if you are using 192.168.1.121, you will get that error
 

Is the networking set up for Mesa?
Is the IP address on the board set same as in the config?

Stick to 2.9.4 for the time being, some issues have arisen, no doubt they will be rectified in a timely manner.

Elaborating on the Lenovo thing, whilst a parallel port in provided, it requires a Lenovo header cable. From what I can gather the cable uses some pin or pins to enable the parallel on what was onced referred to the SuperIO chip. Without this cable the parallel port is neither seem in the bios setup nor the Linux hardware probe. With the cable everything is fine.
Some basically testing on an old parallel port 3rd gen I5 proved it to be a suitable candidate.
But it all comes down to local availability, resellers or what you can find on the street.