Advanced Search

Sounds like the drive has a significant offset or there is some electrical issue
What RPM do you get from the drive at 0V?

I is not for tuning overshoot but to have a slow but unlimited feedback

You can try more I term ( until it oscillates then back off to say 25% ) but I think the
real problem is the offset.

(the P term by itself cannot bring the error to 0 because the P term needs
and error to have any effect)

All this to say, it sounds like there is an electrical issue or perhaps drive
parameter setup issue that needs to be addressed rather than patched
over in LinuxCNC.

 

Also are the drives enabled?

Typically servo drives would have an enable input that must be connected to operate
(with default setup parameters)

Note that if LinuxCNC cannot communicate with the 7I76EU, LinuxCNC will not start.

I've been trying to understand why the system isn't pulling the revs down to 300, but seems ok above, so played with the ini file OUTPUT_SCALE
ini           5000      4500    3600
s.rpm                 Actual
300          450         480      490
500          600         630      700    
1000      1000       1050    1200
2000      1800       1900    2300
3000      2700       2800    3300
To me the control isn't controlling. I think it looks like P needs to be bigger, but if I raise it enough to have an effect, I get significant oscillations.
My understanding was I should raise P until it just oscillates, and then back off a little to be safe,  and lastly tune for overshoot with I. But with this method is not working for me. Is there another method please?

dunnitagain wrote:

Great ! i have to figure out how to load the error files to a USB Stick .
 

It's not ideal, but we can work with photos of the error log on the screen. 

Is there any documentation available on setting up absolute encoders with Linux CNC?

I had to set my machine to a certain state, when a new gcode file is loaded, also reset saved last motion.program.line. I did  not find any example, suiting the requirements, so did it my own way. This pythoncode is creating a number from the current loaded filename. Unique enough for me.

e.g. 'rectangle_inside_helix_stepdown_no_stepover.ngc' returns  3724037, or 'HalfBallConc.ngc' returns 142356. A 'pin in s32' can handle those numbers

easy to make a comparaison oldfile/newfile and take action.

 

One option is to add a simple RS-422 driver/receiver (like a SP491) connected to the parallel expansion port

Also if you have a free stepgen and a free encoder input that gives you a RS-422 interface.

Most probably 10.04

Try wiring both - together and to the - on the Mesa side, leave drives as is.

I wired all the the motors, but i can't move with linuxcnc and the mesa board , i've done the basic configuration and followed the this post  because the configurator couldn't find the mesa but after following the instruction the mesa is recognised. My issue now is that i can't command the motors from mesa and motion control of leadshine can't find the driver(i've contacted the even  the techsupport of leadshine , and no solution finded). For the wiring i followed this  and the official pdf. The wiring should be good, i don't think i've done something wrong . A the moment i've some doubts if linuxcnc can communicate with the mesa, but if i unplug the ethernet cable in linuxcnc it's reported an error so i think they are talking. I share the photo's of my wiring. 
Has anyone experienced a similar problem? Is there a way to further test the Mesa board’s output, or any diagnostics I can run in LinuxCNC? Any advice would be greatly appreciated!

Perhaps configuring LinuxCNC to invert the fault input will work?

For some reason, powering the enable input on some drives disables the drive (Ask how I know).

Which version of Ubuntu?

Have you set up this drive ?
Performs well ?

Hello Rod,
Tank you so much for your answer.
yes of course, i know .... i am 2 versions behind.
If you has fixed in the new version 2.10 ... its possible to get the source code of the driver of the XHC-WHB04B-6 ?
I think this is for me faster like a complete new installation and new configuration of the Machine.
Thank you so much.
Best regards
Reinhard

Its way more easy. You can connect two hardware inputs to the probe-input without having to choose the specific one. As long as you do not disconnect for example the 3d probe and having a active probe signal by that.

In this case you can have a workaround and setting the input of the 3d probe to a ignored one while not having a specific tool in the machine. So for example 3d Probe is tool 1 and tool 1 is not in the machine -> disable the hw input of the 3d probe.