Mesa 7I96s - 5 AXIS

Hi guys!

 I managed to stop my LinuxCNC from giving errors by isolating a core of my CPU. Since then, the milling operations have not stopped and everything is going well.Now I need to add a 2-axis rotary table.

I copied my working configuration from my Mesa 7i96s, and added two A/B axes, both in the INI and in the HAL.I thought it would be as simple as that, but I'm getting an error.I'm not sure if the axes should be called A/B in the configuration.I'm attaching the files to see if you can help me.

Thank you. 

hm2_eth: ERROR: Could not retrieve hardware address (MAC) of 192.168.1.121: Resource temporarily unavailable

Means that there is no communication with the 7I96S

Yes, I saw it.

But with 3 axes it works. That's why I'm asking.

wiring issue causing a short?

I have checked the wiring of the drivers and the controller board. Everything seems to be fine.

With the 5 drivers turned on and the 3-axis configuration, it works fine. When I open the 5-axis configuration I have created, it gives an error.

Could it be due to a parameter in the HAL or INI?

Is the card IP address different in the 5 Axis configuration?

Not, it's the same

So it's a mystery, Your hal/ini files work for me.
(after changing to 10.10.10.10 IP address because that's how my test PC is setup)

Do you always get this error:

hm2_eth: ERROR: Could not retrieve hardware address (MAC) of 192.168.1.121: Resource temporarily unavailable

That happens before any joint/axis ini settings are processed and is only related to low level communications.

You can sometimes get this error after power cycling if the network link is not established yet, so could happen in testing
but is not in anyway related to the number of axis.

 

Yes, I always get the same error. I've been trying things all day, changing the connections between the drivers that I'm sure work fine. Everything seems to be working correctly in terms of the electronics. I've tried all possible combinations with the drivers and the connections on the 7I96S.

Could there be a ‘conflict’ because there is another configuration that has worked with the same IP? Could there be some kind of ‘cache’?

If I remove the two added axes from the HAL, then I don't have any problems.