Advanced Search

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....

Hi Andy,
Are the macros reread from the drive each time they run, or loaded once at start up? 
The reason I ask, is I need to change the G76 Q value to 4.5° to cut my Schaublin collet draw tube buttress thread, and was wondering if I can just edit it with LinuxCNC active, or whether I should shut down, edit, and then restart?

Have you considered making flank angle a data entry box on the Macro page?
Cheers,
Mark

The velocity units for linear axis are in inches per second, not revolutions per second
If the linear velocity is not correct, its likely the the step scale does not match the hardware
(hardware meaning the ball screw pitch, step drive microstep ratio, any intermediate gear/belt reductions etc.)
 
The velocity units for rotary axis are in degrees per second.

Note that latency will have no real affect on scaling unless its
so bad that you get stalling (which would be obvious)

I am finding that

1. the stepper motors for the two spindles work as expected, however
2. the stepper motors for the axes (B, U, V, X, &, & Z) run at a VERY slow speed. 

The latency test on my Raspberry Pi 5 gave:

• Servo Thread
  • Max Interval = 1,013,089nS
  • Max Jitter = 13,089nS
• Base Thread
  • Max Interval = 46,407nS
  • Max Jitter = 24,074nS

I ran the Step Timing Calculator to set the BASE_PERIOD based on using StepperOnline DM542T drivers.

• Step Length = 2.5µS
• Step Space = 2.5µS
• Direction Setup = 5µS
• Direction Hold = 5µS

The recommended BASE_PERIOD = 26.57µS.

When I run LinuxCNC based on this configuration, the value for the parameter, hm2_yi92.0.stepgen.02.maxvel = 1.

Regardless, the stepper motor does NOT run at 1 rev / sec.

---

Attached are the HAL, INI, and include files for

• Spindle0 (Spindle1 is the same)
• Axis X (axes Y, Z, B, U, & V are the same)

The X Axis is set as Joint 0, Channel 02.

---

Help would be GREATLY appreciated!

Thank you and kind regards,
Rich

What does my script do?

(sudo is a bit funny with some command lines)

I realize my questions probably don't make much sense so attached are some pics of how I think I should wire it, bypassing the old "phc interface."

I don't want to use the "phc interface" because I would have to make some assumptions about how it was wired.
For example, can I assume the 12v on the on the "phc interface" break out is actually 24v since the hypertherm hsd130 doesn't have 12v?
Do the wire colors correlate to the wire colors in the manual?

If I take the time to verify this, why not just bypass the "phc interface" and go directly to the 37 pin connector that I have documentation for.

Hello folks...

have anybody working configuration with custom data telegrams of SM pdos which include internal SoE probing objects? I think internal probing in generally over the SoE parameters and S-0-0169, S-0-0170 IDNs ...

@chimeno, @db1981 has some working stuff but I can not see any custom modification of the SMs ifself...

Thanks and regards