Advanced Search

Yes everything in the bios is off. The only thing that has changed in the pc since it was running the older version of PlasmaC without issue has been the hard drive. I can only think that either it has an issue or the controller has an issue, maybe that’s why the original drive failed.
I will try a different motherboard and HDD over the weekend

Thanks for the help

Thanks, I will take the practical approach and leave it alone.

I did catch that a bit afterwards, lol. thank you for keeping an eye out though. I tried to un-E-Stop, power button on and home all axis. No motor movement, drives are still in preop state. Have attached the resulting output.

Steve Cap
 

No need to change, they are fine. For joint 0 and motor "D1"
But I saw in the screenshot, you mix D1 and D2, can't do that. "D1" comes from ethercat-conf.xml, the first drive. You will find "D1" there.
Change D2 to D1.
 

No, the system will be linuxcnc, the head does not yet  have a BC-AMP but there is provision to mount an amplifier to existing tapped holes. So at this stage I don't measure anything!
 
Your unit should fit and it would be up to me to adapt  linuxcnc to read your system and interpret the results for height control.
I have previously beta tested some hardware for Mesa and developed an ohmic sensing component for linuxcnc, which is now part of linuxcnc that enables the hardware I tested.
linuxcnc.org/docs/stable/html/man/man9/ohmic.9.html


 

OK, I am making some headway and beginning to understand how things are being read in. The GUI loads up now, but before  I try to jog anything do I need to modify these sections too? 

What's the cause among all text, but it is this line in the middle. More variables to rename.
You have it marked already in the left window. lcec.0.D1.srv-cia-controlword
But you renamed the wrong variable. Rename lcec.0.0.cia-controlword.
 

Ok, we made it a bit further. but now the entry I've added that should be correct does not seem to take, also there is an error regarding SDO upload?

Steve Cap

2. no, not that i can think off.

I thought I would reply here as I too bought a Byte2Bot parallel hat. I eventually did get it working, but in hindsight I believe I made a mistake purchasing this. While it does work for its intended purpose once you figure out the setup, it is limited to 12 outputs and 5 inputs. What I should have done is purchase a level shifting GPIO breakout hat, which give 26 pins of I/O and each pin can be either input or output. As my particular machine is set up, I have used all of the 5 inputs on the byte2bot board, but could use some more. I believe a level shifting breakout board would have been more useful for me.

I installed Linux Mint Debian (faye) and LinuxCNC. It all works fine, but LinuxCNC is rev 2.9.0 something.
1. How do I upgrade to the most recent version?
2. Does this really matter?

Thanks,
Steve

In gmoccapy I have the initial rpm set to 350, the override coefficient 1.2 and the max rpm to 600. In manual mode I start the spindle and the rpm starts at 350 as 100% I am not able to raise it to the maximum level which is 600.
The second issue in MDI mode I call the command for example M3 S175 and I have such rpm on the display and the slider at 100%.  After switching to manual mode , starting the spindle with the button the rpm starts from the level of the last called command M3 S....

Für open loop kannst du den stepgen als position feedback verwenden. ZB:

That (>16 ms latency) seems like a power management issue or perhaps a hardware failure.
Are all power management, C States >C1 , Turbo modes etc disabled in the BIOS?

I added the pcie_aspm=off and also igb.EEE=0
while running latency-histogram the rt error occurred and the latency shot up massively, see attached.
i then added isolcpus=2,3. I have since done some cutting and not had the error since. Time will tell if that resolved it or not, but the massive increase in latency that came out of nowhere makes me think there is something else happening