Advanced Search

Sorry, I tried uploading pictures of my BOB several times, but it wouldn't do it. I think I got it to work finally.

NWE, even though I have the BOB right next to the contactor and 12v/24v power supplies, I have never had any issues from those. I have consistently been able to run programs without issue with everything except the VFD on. The contactor is part of my Estop circuit, and it only gets turned on before I run a program or off if I hit the Estop. I have only ever experienced issues when the VFD is on.

I experimented yesterday and learned some. I tried connecting it to earth ground, but that did nothing. I tried disconnecting everything from the BOB except for the 24v coming in and the parallel port and USB from the PC (I switched the VFD to manual control). LinuxCNC ran the program with out any trips even though the VFD was running, so the BOB itself can't be the issue. I tried reconnecting one of the stepper driver pulse/direction signal wires (the steppers were completely off) and ran the program again, and it did trip, even though that wire is shielded and grounded.

I will disconnect the second shielding grounding at the motor. I will also try adding ferrites on the VFD wires first. I think we have a couple lying around that we also pulled from other things.

i am here just for subscribe and learn something more about PLL ... 

take a look at default resolution SDO .. it has to be something like 20 or 16 ... it is user resolution per revolution ... maybe it has some weird setup from factory ... you have maybe swapped bytes or something or wrong data type .... 

you dont share anything ... maybe share more details for focused reply 

Never seen a several km long axis so I am out of clues, sorry.

I can only take credit for rediscovering the PLL code and write some lines of documentation.
Sasha Ittner made the PLL code back in 2018 and it hasn't changed since then. 

Will be interesting to see what you come up with.

My problem. Is in PDO mapping, i was able to configure how to switch the IO module to OP state by using sdoconfig in XML to set some SDO to be able to switch to OP state, now my problem is with PDO mapping section, the manual says PDO 6000 is for inputs and PDO 7000 for outputs, when i ran sudo ethercat -p 5 pdos, i couldn’t find these PDOS

Hello, i have R3EC leadshine io + DI + DO
Are you having same io system , if so could you please help me in writing the xml, i am stuck in the PDO mapping section

Really nice work thank you.

I’ve modified the interface so that the scanned surface can be visualized with a button press. The next step is to make the probing settings persistent across LinuxCNC sessions. These settings are stored in the .var file, but I’m not sure how to load them at startup and update the Qt widgets accordingly.

 

jjdege wrote:

Hi,
try changing the value in the .hal file

setp cia402.0.pos-scale 1000

 
[code]Hi. Pardon for offtop. Please could you try to explain what will do linunxCNC when you using this scale, and reach the calculating maximum of +2^31, and momentary jump to -2^31. On my case system stops and there an error of following..

[/code]

Hi
I doing retrofit on machine, used etheecat delta.
i used in hal file scale parameter pos-scale to adjust lenght of movenent

today i catch an error, when linuxcnc receive value during moving equals +2^31 and became -2^31, system catch that prevous value pos of axis calculated in mm was 380mm, and after count +2^31 overflow became -67mm. So there an error.

I have no ideas, and stucked) How to solve this trouble?
thanks in advance!

Most probably they will not work, inductive proximity sensors react to metal by inducing a magnetic field, but do give it a try, they might react, and might be polarity sensitive....

gtk-builder-error-quark: gvcp-panel.ui:72:38 Invalid property: HAL_Table.n_rows (11)
Warning: Forward kinematics must handle duplicate coordinate letters:yy
Embeded tab command "halcmd loadusr -Wn gladevcp gladevcp -c gladevcp -H gvcp_call_list.hal -x 58720684 gvcp-panel.ui" exited with error: 1
Shutting down and cleaning up LinuxCNC...

Different OS?

JT

Hello and Merry Christmas to you all,

I have written a ethercat driver for the EL2564 (led driver) - since there isnt't one yet - and tested it so far. Everything can be found in the attached ZIP archive. A video shows how it works

Have fun with it and enjoy tinkering in your workshop,
Pierre 


 

So, there is a much bigger issue with lcec supporting LWR and Yaskawa drives requiring LRD/LRW.

I followed some of your links and while there is some success, there are also very pessimistic opinions
on rewriting of lcec_main. Maybe it is possible to take some of the success and shoehorn it into something?

For Yaskawa Sigma7 the issue with lcec (linuxcnc-ethercat) software component is not only EOE being enabled in the drive.

It also has something to do with modes LRD/LWR and LRW. In the sigma7, the PDOs in the syncMasters are not read-write, i.e., LRW mode is not supported by sigma7. To work with sigma7, you need to enable 2 domains in the lcec program. I am not sure how to do that yet.

This issue is documented in these forum threads:
forum.linuxcnc.org/ethercat/50245-yasikawa-sigma7-lcec-driver
forum.linuxcnc.org/ethercat/48110-etherc...-responding?start=40

I have tried using this program from github.com/nylon7 and fdarling (on the yaskawa thread in the linuxcnc forum) and have seen some success in enabling the sigma7 motor and moving it and reading the absolute position register over ethercat.

github.com/nylon7/Igh-Ethercat-master/bl...ples/user/main_yas.c

For doing this, I am using the IGH Ethercat master 1.6-stable with EOE disabled as documented by Hakan.

I think we need to make some changes in lcec to enable the use of two domains.

-automata