Remora - ethernet NVEM / EC300 / EC500 cnc board

More
3 years 2 months ago #278376 by Eugene64
"and use

upload_config.py
usage: upload.py <config.txt>
accordingly to upload config.txt
from
github.com/scottalford75/Remora-NVEM/tre...es/remora-nvem-basic
to test.

Make sure drivers are also in correct configuration you require.

Below is default [TRAJ] from remora firmware in
github.com/scottalford75/Remora-NVEM/blo...asic/remora-nvem.ini

[TRAJ]
COORDINATES = X Y Z
LINEAR_UNITS = mm
ANGULAR_UNITS = degree
CYCLE_TIME = 0.010
DEFAULT_LINEAR_VELOCITY = 100.00
MAX_LINEAR_VELOCITY = 200.00
NO_FORCE_HOMING = 1

I hope this make sense a little :)" - I compared the configuration that I have installed with the one that you recommended to install. The difference is only in one line. I have registered "loadrt remora-eth" in your version of "loadrt remora-nv". What should I do next ? Thank you.

Please Log in or Create an account to join the conversation.

More
3 years 2 months ago #278384 by cakeslob
Both components look almost identical. It probably wont make a difference if you change from eth to nv.

It sounds like you are using regular stepper motors with a closed loop in the driver. Regardless, try the thing I said earlier.
www.forum.linuxcnc.org/18-computer/44828...rd?start=1030#277956

Please Log in or Create an account to join the conversation.

More
3 years 2 months ago #278454 by MotoMishka
Hi Scott,

Thank you for your reply. Do you think i fried the board with that jumper? I ordered a pico probe, will try with that once it gets here.

Please Log in or Create an account to join the conversation.

More
3 years 2 months ago #278585 by Eugene64
"It sounds like you are using regular stepper motors with a closed loop in the driver. " - I am controlling a stepper motor with an N-coder connected to a 2HSS86 controller, and I'm absolutely right about it. Is it possible to change the motor type from servo to stepper in the configuration file? Please advise me where I can read more about finely tuning the parameters (P_GAIN, FF1_GAIN, DEADBAND) that I'm adding based on your recommendation. Thank you!

Please Log in or Create an account to join the conversation.

More
3 years 2 months ago - 3 years 2 months ago #278595 by Eugene64
Last edit: 3 years 2 months ago by Eugene64.

Please Log in or Create an account to join the conversation.

More
3 years 2 months ago #278616 by cakeslob
It looks like an improvement thought? It doesnt seem to be over shooting position by as much.

To be honest, I also do not know a lot about the parameters. I cant see the numbers on screen very well, perhaps start with lowering the deadband to something like .01. It looks as though you are getting closer though.

Code:
Pgain - Proportional gain. Results in a contribution to the output that is the error multiplied by Pgain. FF1 - First order feed-forward term. Produces a contribution to the output that is FF1 multiplied by the derivative of the commanded value. For position loops, the contribution is proportional to speed, and can be used to compensate for friction or motor CEMF. For velocity loops, it is proportional to acceleration and can compensate for inertia. In both cases, it can result in better tuning if used properly. deadband - Defines a range of "acceptable" error. If the absolute value of error is less than deadband, it will be treated as if the error is zero. When using feedback devices such as encoders that are inherently quantized, the deadband should be set slightly more than one-half count, to prevent the control loop from hunting back and forth if the command is between two adjacent encoder values. When the absolute value of the error is greater than the deadband, the deadband value is subtracted from the error before performing the loop calculations, to prevent a step in the transfer function at the edge of the deadband. (See BUGS.)

forum.linuxcnc.org/10-advanced-configura...ng-pid-and-ffn#14487

Please Log in or Create an account to join the conversation.

Time to create page: 0.448 seconds
Powered by Kunena Forum