Advanced Search

Hi again,

For "posterity" on google i thought i'd show what i did on my CTB-servodrives. I managed to figure out that if i turned up for the gain(register Cn.29) from the factory setting of 100 to 350 i got quite a lot better results. Now a "step" looks something like this:
 
Greatly reduced the follow error and made it hit the required position a lot faster/better. I tried higher values, but then it will overshoot. This enabled me to turn "ferror" down to 10 and "min_ferror" down to 1 in the settings without getting "follow error" when jogging....this is better, but not sure if it is good/low enough?

However, i still have a question: There is a delay between "pos-cmd" and "sta-ActualPosition", obvious this can never be 0, but it seems like there is something like 50ms between the two according to the graph...this seems "long" to me...is that normal? I'm guessing that EtherCAT has something to do with this, even though i think it should be an order of magnitude lower if it stems from EtherCat. Anyways, i'm unsure if this will affect the performance of the machine significantly...?

Question: What is this delay on your machine? I'm trying to either comfort myself and accept that this is a normal delay, or determin if i have to keep digging in the drives registers to try to make the drive follow LinuxCNC in a tighter way...somehow...

/Thomas

If your getting over current alarm, most probably the motor wires are miss wired.
Stepper motor wiring is very strict, no mixing of coils, that is something most drives will not survive.
To check wiring, connect any two motor wires together (disconnected from the drive) and turn the motor by hand, if you feel resistance = that is one winding and those two wires MUST go to A+ and A- <<<OR>>> B+ and B-, never ever between any A and any B.

I suggest having a huge banner on every web page on planet earth to remind people that the server they are getting pages from runs Linux, open source software.
The whole world runs on Linux, everything from microwave to NASA "Mission Critical" stuff, to stuff that keeps humans alive in hospitals.
All still Open Source or was Open Source at a given point in time.
-
Talking bad about developers is really uncalled for:
- they are humans, and as such they might get p.o. seeing their software used in huge projects that are making someone somewhere insanely rich, but they are still in their parents basement pushing 40-50 years old with no wife and kids....
-or someone else jumping into their project and trying to change how he/she did things while intentionally trying to make them look dumb/stupid/incapable
And no matter how bad the first example was, this second one is much worse.
It is Open Source, if you do not like how it is, fork it and do things your way, do not demean the original developer/s
-
To ALL DEVELOPERS everywhere:
THANK YOU.

But can you elaborate how you "removed" the Y axis from within linuxcnc / pncconf?

Well - (to put it politely) blow me down . It had to be something simple of course. I will check it out shortly. Many thanks.

I am not familiar with those exact motors. That said, I just want to make sure that none of the motors will move at all?
Do they make any kind of noise when a move is commanded? Like when a stepper is stalled? Do they get hot?
If none move at all and they all trip with the exact same problem check your drives amp setting.
It may also be possible that the motors need to be wired in bipolar series for those drives to work
with them.

For X-axis and Y-axis it's Nanotec 4H5618 C0408
www.nanotec.com/fileadmin/files/Datenbla...toren/4H5618_L_C.pdf (it's in german)

For Z-axis it's ISEL MS110 (473030)
www.isel.com/hu/mwdownloads/download/link/id/4186/

What size motors are you driving with them?

In AXIS use the VIEW tab and select Inch or Metric display, or use the "!" key.

Sure, maybe we could continue here:

forum.linuxcnc.org/10-advanced-configura...stead-of-rtcp#295155
 

I found it. Unfortunately switching it to 5V didn't change anything.
However I realised that the red LED of the drivers are blinking one time every three seconds, in the manual it says "Over-current protection activated when peak current exceeds the limit."

I've already managed to find out why I need to change numSymbols=200 to numSymbols=300. But it has the right position, if you put it at the beginning it crashes the system. Thank you, I'll leave this post in case anyone needs help with this. Thank you to everyone in this forum

#Carregar classicladder Parte 1-3
loadrt classicladder_rt numBits=100 numPhysInputs=99 numPhysOutputs=98 numS32in=99 numS32out=99 numFloatIn=99 numFloatOut=99 numWords=30 numSymbols=300

 

See top of the above picture of the drive. It says PWR / ALM from what I could see of your pictures you have them.
From the factory they are set to 24 volt. It is possible that switch is underneath of the cover.

I haven't read anything so stupid and inane in a long time

Hello everyone. I'm organizing my programming in Linuxcnc's classicladder. However, I'm not able to name a symbol name for variable %B3 onwards. It doesn't appear in the list when I press the Symbols button in the Section Display of custom.clp window. I've already tried manually editing the custom.clp file in the Geany program, but it didn't work. Note, in the hal file numBits=100 has already been configured, but I'm still not having success. Attached is what has already been done. Does anyone have any suggestions on how to solve this, so I can name the symbol %B2, %B3., %B4 ... onwards?

#Carregar classicladder Parte 1-3
loadrt classicladder_rt numBits=100 numPhysInputs=99 numPhysOutputs=98 numS32in=99 numS32out=99 numFloatIn=99 numFloatOut=99 numWords=30