Advanced Search

Hey, you can try this one out, its still got some buts but it does the thing you want
github.com/cakeslob/regularmac_800/tree/search_gcode

From that Omron thread, it looks like Arvidb got it working, so can you try with the ecat-conf.xml?It's the same xml that Arvidb used, but I have changed to what I think it the right model, based on the product code 6 you use.

You need to remove this from your hal


You are already loading probe_screen.py with the EMBED_TAB_COMMAND in the INI.

To troubleshoot the pin problem, comment all lines with 'probe.' pins so the config starts up and use the 'Show Hal Configuration' tool to check if the pins are there.

Sooo, back at my ethercat fun and I think I've made progress, but I'm stuck.

I've gone right to the basics and am just using halshow to poke the drives.
I made a super basic xml file following some other examples on here.

So, following this:
EtherCAT: How to use the dedicated OmrG5 lcec driver? - LinuxCNC $ ethercat slaves shows me my 3 drives just fine
$ ethercat upload -p 0 -t int32 0x6064 0x0 shows me position just fine
$ ethercat safeop doesn't work and returns error 90 because the default sync0Cycle is wrong. This seems expected.

My xml is:

<masters>
<master idx="0" appTimePeriod="1000000" refClockSyncCycles="1">
<slave idx="0" type="generic" vid="#00000083" pid="#00000006">
<dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="0"/>
<watchdog divider="2498" intervals="1000"/>
</slave>
</master>
</masters>(using the generic driver here cause the omron one was saying no drive found)


then we do this in halshow:
loadrt threads name1=master period1=1000000
loadusr -W lcec_conf linuxcnc/configs/ecat-test.xml
loadrt lcec
addf lcec.read-all master
addf lcec.write-all master
start

All works, except after we get to start, the drives show error 83, and if you look at the pins, its actually cycling through preop, safeop, inti, op, error every so many ms.

So what have I done wrong here, or what do I need to add? The are many gaps in the information and steps people provide so I expect there's just something missing I don't know about.

Thanks!

Thanks a lot for your help!

Now that I hooked up an oscilloscope, the problem disappeared completely again - can't reproduce it anymore, at all.

That made generating pulses easier of course, I simply jogged the thing along. The levels of the step+/- pins on the motor side are around 4.8 volts, and -4.8 on a pulse.

I also noticed that the level between STEP- and the cable shield (GND) is around 40 volts AC (50 Hz). I can't say I understand why that would be so. Is that normal/intended?

It appears that the pins in question (probe.toolchange-change, etc) would be created by probe_screen.py.

In the INI file,

And from custom_postgui.hal

Try this.
in your config folder add folders qtvcp/screens/qtdragon_hd

in the qtdragon_hd folder add this file, name it qtdragon_hd_handler.py

for installing qtpyvcp and probe basic use the apt install, it stay updated and will update as updates are available when you run sudo apt update for the system.

the linuxcnc installation seems to be a moving target, i use my own instructions in the stable_quick_start_apt for installing debian and linuxcnc and it seems to be the most reliable. but you technically should be able to do it the way you outlined above. please report back if you get errors.

Hello all,I’m in progress to get information about how to retrofit an old Gildemeister.To make a plan with what to buy and set the proper path. In the begging was pretty clear, new servo, new Vfd, go with ethercat and modbus for spindle. But when o checked today the spindle is a very large dc motor. The amplifier is old but in working condition. A new amplifier have a huge price for this motor. Do you have some suggestion for me?

Hi Tom, with the new cable all four work. I looked for motors but they ask 200 euros, in your opinion are these drives valid or are new Chinese ones better?
I calculate the cost of the motors because the drives didn't cost me anything.

Perhaps an output is marginal because of previous damage

I would verify full 5V swing on all step/dir pins.

Here is a simple script to toggle all stepgen step and direction pins slowly:

 


Download then

chmod +x stepgens.txt

and

./stepgens.txt to run

Note that this needs a relatively recent mesaflash

github.com/LinuxCNC/mesaflash

I'm running version 2.9.3

When I open this link: developer.arm.com/downloads/-/gnu-rm, it says: This page is deprecated. See Arm GNU Toolchain for updated content and latest releases. Arm GNU Toolchain.
If I follow Arm GNU Toolchain, many download options appear. Which one should I download?
The truth is, I have little experience doing this type of installation from scratch, and it seems like what you've written on your Github is for experts. I don't know if there's a way to do all these processes automatically with bash.

Which version of linuxcnc are you using?

i cant tell as am not machining anything, just moving the machine.
with other files this doesnt happen, but the position errors still happens
a lot of times i have drivers out off op state, then back on, i can run the same hardware on standard linuxcnc without any problem

edit:
emcMotionInit: emcTrajInit failed
this message shows in terminal when i start the scurve ethercat config, is this a problem?.