Advanced Search

OK. one more thing we need to test, download a Linux Mint ISO, write to USB, boot the PC from that USB in Live mode, choose English as language, log in to forum and try to post.
-
Yes, there are internal logs pointing to different locale being used and the database complaining about it, hence the above request.
Danke fuhr die geduld.

Hey, 

ich habe zwar nicht die gleichen Treiber, aber ich habe einfach 5 V draufgegeben und der Treiber war gesperrt. 
Demnach müsste nur ein digitaler Ausgang deiner Mesa-Karte auf ENA+ gelegt werden und der entsprechende GND des digitalen Ports der ESA auf ENA-. 

Wenn der digitale Port dann HIGH ist, müsste der Treiber gesperrt sein. 

Gruß Mücke 

Wie zu erwatren ist ein Fehler aufgetreten  

Error
Kunena Internal Error: Please contact the site administrator to fix this issue!

 Ist eventuell etwas intern mitgeloggt worden? 

 

Some observations:

Lots of people are using USB to Modbus convertors to control spindle VFDs, and that works OK, (it's noticably notchy doing CSS on my lathe, though)

Jepler (long-time LInuxCNC dev, but now left the project) wrote this back in 2007:
emergent.unpythonic.net/01198594294

USB is definitely adequate for any HMI interaction, otjherwise gamers wouldn't be able to use USB keyboards. (I know that _some_ insist on PS2 for less latency, but most don't)

Have you tried an "fq" config (or "fqi"). That should use the Fanuc commutation for initial starting and then use the quadrature position from that point on.

Probably . I haven't tried it.

Dec 27 it looks like from github. Actually, the bug shouldn't affect you.
A negative refClockSyncCycles value should switch on the PLL and synchronize servo loop time with DC time.
You can always check the lcec.pll-* hal variables. If some of them move, it's on.
refClockSyncCycles is how often the master sends a synchronization signal to the slaves to compensate for clock drift.
I use 1000 because the slaves' DC clock run pretty accurate as it is. Many people use 1 as value.
I have not seen that any number is better than the other, maybe there is, but feel free to use any number you prefer.



 

Now as in just recently or in the patch from last year? or reaaally recently
Also, what does the refClockSyncCycles value do and is there any baseline on what to set it at?

There was a bug with "-1", fixed now but it sounds like you have it.
Use a positive value in refClockSyncCycles and set syncToRefClock="true"
and that should hopefully fix it.

I currently have refClockSyncCycles="-1" which according to the docs you linked above, means its enabled for backwards compatibility. Sadly, I have these mentioned issues where the axis starts clunking randomly (on a random axis) after some time. Its a fresh install from end of january. Does SyncToRefClock still need to be set?

Better yet, enable synchronization with syncToRefClock="true"
github.com/linuxcnc-ethercat/linuxcnc-et...s.md#master-settings

The refClockSyncCycles is how often to synchronize the clocks between the slaves
which is something different altogether, and doesn't help this problem.

Never mind. 

I was trying the entire weekend to make the drives work but still no success. Basically I started from scratch and cloned "linux-cia402" from RodW github page. Then executed "ethercat pdos" and the drives return PDO mapping 1701h and 1B01h. Next, following the manual and the mapping for 1701h and 1B01h, I wrote the .xml and .hal files. In the .xml file, I tried to set the data type for each pin as per the manual but the lcec components does not like s16, u16 and u8, anyway I changed them to s32. LinuxCNC opens and loads the configuration but when I try to home, a following error occurs.

In the terminal I observed a weird output when execute "ethercat pdos" after LinuxCNC has started - there is no names on the right of the PDOs, look at the attached pdos.txt file.

Also the synchronization error  and 1 datagram unmatached warning appeared again.

In the beginning of the .xml file I tried to set the PDO mapping using "sdoconfig" but it does not seem to help either.

Debug enabled, give it a try.

Okay, thank you.

I had already thought that the issue had something to do with packet loss when starting LinuxCNC.
However, this seems to occur during operation, which I have not yet experienced. If this work results in ethercat running more stably, I will simply wait until Sascha announces an official patch, which will likely be available via update.
Until then, I will simply stick with refClockSyncCycles="1">.

I got it working.

No feedback needed.
3 pins are used..

Forward
Backward
Pwm pulse

L298n cheap modul.

I clean up the component and then i make a small video und can share the code.

I use a 8 position toolchsnger from my emco 220 where i unmount the lightbarrier pcb.

How it works:

Start linuxcnc..
Then 1 time make movement over a button of the toolchanger.
Then look which tool is in position.
Then set toolnumber over buttons.

After this all is done over timing.
No motor noise!
No overheating!
No issues!

Rollover is handled.
The biggest problem was to find the correct timings and speeds.

The reason for the issue is that the dc motor has a planetary gear and the wormgear has small play.

You can setup:
How many toolslots you have
Time from slot to slot
Backward time
Backward locking time

Pwm for forward
Pwm for backward
Pwm for locking against the pawl

Advantage:
If you hit emergency off the toolchanger stops and resets

You can add reference signal to tool1
You can drive toolchanger from slot 2 slot over buttons.

You have pins where you csn see if you have rollover and the slots it must travel.

Its complete openloop and can setup over a hal or halpkns