Advanced Search

i think you are little bit wrong because of mapping... mapping is used to setup communication canal to shape which you need...

you can use legacy or mdp but there will be different temps for your program.. if you will use MDP, my profibus component will not work probably... I had to check them...  but for setup purposes of communication start it is OK

but all of them will need SDOs which tells the slave how to communicate with its master ...

It sounds like you're experiencing intermittent motor position errors, which can often happen with stepper motor setups due to following errors or configuration tuning.

Preview of ethercat test:

www.youtube.com/shorts/sKFA5jFS64c
 

@Smc.collins,

That's more or less what's going on.

Maybe you could run multiple trajectory planners in lcnc. But still you have just one
shared memory region, and one interpreter.

Today the realtime example is tested on real hardware using ethercat bus.
This is source code looks like RTAPI & HAL,  but is coded entirely from scratch.
Purposing it can load multiple instances of rtapi & hal.

// Ethercat EK1100 & EL2124
ethercat code

// Qt gui
qt_code

// Rtapi & hal lookalike code to run the application.
function loader

This test was going very well.
The qt app has buttons to set the ethercat digital io's.
The function loader also  connect's the hal pins over different shared memory regions.

Thanks a lot. I'll have a try as soon as possible.
If I understand your question right: I do use the MDP mapping (not the legacy) since I thought that then I do not need any SDO configuration in the ethercat conf, all the startup stuff is then stored at the EL6731 itself -- but I just followed some advice in this Forum, clearly I do not know what's really happening.

BR Franz

Hi,

I frequently run into issues like this where I receive the message seen in the screenshot and I am not sure where the problem is. The message points to an issue with Joint 2 (Z-Axis) on a line without Z-Axis command. 

My Machine Axis is defined as X=0 at the upper most point XY=0 at the lower left. I referenced the work piece XYZ=0 at the left bottom (XY) on top of my material.

This is the second Tool used on this work piece (first was planing, now it's pocket milling).

And thanks for the pointer to the probe update.

Thanks, I will have a look at those lines tonight.
Also, Tommylight's reply appears to raise concerns re the parallel port. Is the below possibly relevant?

• Make sure LinuxCNC does not prevent the Linux parport_pc driver from loading. Older versions of LinuxCNC would blacklist parport_pc in /etc/modprobe.d/linuxcnc.conf (or /etc/modprobe.d/emc2.conf for even older versions of LinuxCNC). Comment out any lines in either of those files that looks like this:
  install parport_pc /bin/true
• Make sure your Hal configuration does not have loadrt probe_parport in any .hal file.
  
  And possibly this is also a problem now? 
  "Joints_axes updates
  When you update LinuxCNC, the update_ini script will automatically convert your user configurations. If the script detects that your configuration needs to be updated, it will offer to edit your user files and create an updated configuration. "
  
  If there are multiple more problems, maybe I should have/still could try to update my old computer Linuxcnc (not sure of version offhand but c.2007) before copy over the linuxcnc folder?

Edit: I did originally consider updating linuxcnc first but believe my version of Debian is too old for that, so probably not a route I can go down.

Seems to be a problem with python2/gtk2 vs python3/gtk3. With version 2.9 Linuxcnc no longer supports python2/gtk2 so  'stdglue.py' , 'probe_screen.py'/'probe_screen.glade' and possibly 'spindle_button.glade' would need to be updated.


[Edit]

This might be of interest:
github.com/verser-git/probe_screen_v2.9

This is the solution... Thanks....

If you are using master branch - I added jog increment pins:

qtdragon.jog-linear-increment
qtdragon.jog-angular-increment

Tonight I focused on getting my handwheel working. RIO is just a fantastic software!

I was also able to get a video of the problem of my Y axis.

I noticed a few things: The units in the display of LinuxCNC are sometimes jumping around a little bit. I think that was discussed somewhere earlier her. Will dig that out. Maybe that's the reason why I measured Step pulses and the motors shake even when I did not move an axis.

A few words to my machine. X and Z are are Nema 23 Motors (23HS30-2804S) with www.omc-stepperonline.com/digital-steppe...stepper-motor-dm332t DM332T driver. Z Axis has the highest resolution 5mm pitch ball screw and 3200 microsteps/round. Brings it to a scale in LinuxCNC of 800. As shown in the video I have no issues going up to 3600mm/min.

The Y Axis have 2x  www.microkinetics.com/index.php?page=stepper_motors/34m450 34M450 Microkinetics Motors with www.microkinetics.com/pdfmanuals/DM8010.pdf DM8010 Driver.5mm pitch ball screw and 2000 microsteps/round. Scale 640 in Linuxcnc. I limited the axis to 1950mm/min, but it's still stalling.

All axis are connected over the same Breakout board with no level shifter.

I doubt that the problem has something to do with RIO, but I am not sure. Still a myth what the problem is.

Yes I had forgotten, its the RPI3 that uses USB --> Ethernet
I should know since I have run a Mesa Ethernet card from a RPI4.

 (I think some RPI4 --> Ethernet motion card users needed to increase
the servo thread period to 2 ms to get it to run reliably)

Cant do this anymore bye all wrote:

I was always under the impression that up to version 3 the ethernet was on the USB bus and 4 and after were on the PCIe bus.

Me too !

Disable "secure boot" in PC's BIOS.