Advanced Search

I should note that the the pinirq script runs as expected on the LinuxCNC/Debian 12 image

Thank you Tommy and Djdelorie, i appreciate your help so far, i had a few minutes and disconnected probe and assign individual pins and did not work but i did not have much time and I will be away form the shop probably till Tuesday (which sucks because i want to convert this machine so bad) but i like the idea of only using 2 pins this way ill end up opening one output. and ill get back here to report how ever i did not find the option of assigning multiple stepgens to one pin so i assume it will have to be done in .hal and .ini??!! ill include those once i try (if i get a chance ill sneak in the shop on Sunday (fiancé permitting lol)

thank you again for the help

Files attached.

 

   

 

Coming up with another problem:
When using toolchange with combobox toolselection and pushbutton, Toolchange gets completed.
Trying to jog with jog pushbutton afterwards, this error appears for any axis

Joint jog requested for undefined joint number=-1 (min=0,max=3)


Doing toolchchange Tn M6, jog works without problem
When a MDI command movement of any axis is done, afterwards jog is possible without error

Don't see anything wrong there.
To try to diagnose this, we would need to see
ini file
hal file
ethercat-conf.xml file
and last say 40 lines of ouput from the command "sudo dmesg"

Here you go, see attached. 

Change appTimePeriod as well. Lcec usually gives an error for mismatch with servoperiod, error somewhere after linuxcnc start command.
Are there any other errors in the window where you start linuxcnc?
Can you post the ouput from the "lcec_config" command?
I really only have two more ideas, try with sm sync and free run.
For sm sync change to assignActivate=100, and for free run test comment out the whole dcConf line/item.
If that doesn't makes things better I think you should hook it up to Twincat and get it going there.
 

I'll copy the debug output to a file and attach it...

Thank you for your reply. I have asked rtelligent for the correct manuals but don't hold out much hope for a response.

I completely agree that the two versions are so similar that they should "just work", but the ECRs disagree, hah. I'll try deleting the 6077 reference and cross my fingers.

I would post the code in question but don't know how to get it from the Linux mini PC out to a Windows PC so I can post it. I can post literally screenshots (via camera), if it's helpful.

The developer had me start LinuxCNC from a command window with the following command. I did, and will try posting the results here, but the forum is blocking me, saying that it has "too many links" (there aren't any):
/usr/bin/linuxcnc '/home/edmuser/linuxcnc/configs/BaxEDM-2axis-WireEDM/2axis-WireEDM.ini'
 

We discussed 60fe some time ago forum.linuxcnc.org/ethercat/50492-etherc...ligent-ecr60-outputs digital outputs.
What are the errors you get? Linuxcnc output and Ethercat output from "sudo dmesg"
Initial thought is that this drive should work with default settings, like the ECT60 does.

Here's a script for 6.17-rc1-rt1 that works for me on Mint 22.1
There may well be different dependencies on your system

 

unzip, chmod +x  then sudo

And yes, Debian does seem to have a talent for making awful RT kernels
 

6077 is actual torque which probably can't be read without encoders so delete it. Not sure about 60fe, I never used it.
I would get the docs from rtelligent for both drives. there isn't really much difference between the ECT and ECR aside from some I/O and encoders.
Sometimes you need to reset to factory defaults as covered in the docs.

I worked it out, by playing around with adding an M5 to the end of Chamfer. It rereads it each time, so I didn't need to restart LCNC.

Ooops, I got that wrong go for kernel 6.16

PCW wrote:

It's more of a kernel/driver issue than hardware/Linux Distribution issue.
 

I think the world has got more complex and there are standards like energy efficient Ethernet (EEE) that the kernel has to support today in this world of power conservation. they all add up.rtt min/avg/max/mdev = 0.100/0.114/26.854/0.321 ms, pipe 2 As you say it is sometimes slow. This can be affected by the initial ping when its connecting but it can be EEE kicking in. Check the doc for how to disable that. (I am not convinced that it is still disabled by default.

One of the issues here is that there is no RT ethernet drivers. Ethercat gets around this by writing their own drivers but for the most part now depends on the generic ethercat driver which is not real time which they say is mostly good enough (except for some realtek). 

The only other trick which has worked with 2 core PC's in the past is to compile the kernel yourself because Debian seems to make some odd choices in their kernel version. If you go down this path, I would download the 6.1.17 kernel source and the matching 6.1.17 RT patch. I would do this to build a Deb on another PC with more cores or it will take you many hours/ even days. Perhaps PCW can provide some guidance on the necessary steps. Unfortunately, I have lost my scripts....