LinuxCNC just stops............Help me Mr. Wizard.

More
15 Jun 2019 17:01 #136998 by Roguish
thanks John,
but I don't get it. something is fishy.

from the docs:

MAX_LINEAR_VELOCITY = 5.0 - The maximum velocity for any axis or coordinated move, in machine units per second. The value shown equals 300 units per minute.

MAX_LINEAR_ACCELERATION = 20.0 - The maximum acceleration for any axis or coordinated axis move, in machine units per second per second.


from my config.ini:

[TRAJ]
COORDINATES = X Y Z
LINEAR_UNITS = inch
ANGULAR_UNITS = degree
CYCLE_TIME = 0.013
DEFAULT_LINEAR_VELOCITY = 0.20
DEFAULT_LINEAR_ACCELERATION = 111.0
MAX_LINEAR_VELOCITY = .666
MAX_LINEAR_ACCELERATION = 222.0
MAX_ANGULAR_VELOCITY = 1.
POSITION_FILE = simple_last_position.txt
NO_FORCE_HOMING = 1

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

More
15 Jun 2019 17:12 #136999 by BigJohnT
I agree that something is very fishy, but I'm not seeing it. I'd start with the very basic config that would run and start adding back a bit at a time and see what triggers that weird number.

JT

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

More
15 Jun 2019 18:17 - 15 Jun 2019 18:30 #137002 by dgarrett
The 2.8 branch has long used abbreviated names for these
two items:
[TRAJ]
DEFAULT_LINEAR_ACCEL
MAX_LINEAR_ACCEL

but the sim configs and the update_ini script use non-abbreviated
names:
[TRAJ]
DEFAULT_LINEAR_ACCELERATION
MAX_LINEAR_ACCELERATION

A pending correction will make code (initraj.cc), the update_ini script
and the sim configs agree and use the NON-abbreviated names.

Until this is corrected, you would need to use the
abbreviated names form.

Note: the default used when the above TRAJ items are not
specified is 1e99 resulting in the big numbers (but i doubt
if this is your problem if you have reasonable accel limits
for each axis coordinate).

Test Branch:
github.com/LinuxCNC/linuxcnc/commits/dgarr/2.8_fix_traj_names

Commit: github.com/LinuxCNC/linuxcnc/commit/c7fc...4cb6d66efc945bada060
Last edit: 15 Jun 2019 18:30 by dgarrett.

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

More
15 Jun 2019 19:17 - 15 Jun 2019 19:22 #137004 by Roguish
John,
found it I think.
Doc are out of synch with code. see the code below. the term 'ACCEL'
the Docs show 'ACCELERATION'

JUST PROVED IT. I changed my .ini from the full 'DEFAULT_LINEAR_ACCELERATION' to 'DEFAULT_LINEAR_ACCEL'
and it now works...............


this is in initraj.cc
acc = 1e99; // let the axis values apply
trajInifile->Find(&acc, "DEFAULT_LINEAR_ACCEL", "TRAJ");
if (0 != emcTrajSetAcceleration(acc)) {
if (emc_debug & EMC_DEBUG_CONFIG) {
rcs_print("bad return value from emcTrajSetAcceleration\n");
}
return -1;
}
old_inihal_data.traj_default_acceleration = acc;

acc = 1e99; // let the axis values apply
trajInifile->Find(&acc, "MAX_LINEAR_ACCEL", "TRAJ");
if (0 != emcTrajSetMaxAcceleration(acc)) {
if (emc_debug & EMC_DEBUG_CONFIG) {
rcs_print("bad return value from emcTrajSetMaxAcceleration\n");
}
return -1;
}
old_inihal_data.traj_max_acceleration = acc;
Last edit: 15 Jun 2019 19:22 by Roguish.

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

More
15 Jun 2019 19:32 #137006 by Roguish
Dewey,
thanks. just found that myself.
and yes, I do have reasonable accels in my .ini for each joint/axis.

so, any thoughts on what my issue may be?

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

Time to create page: 0.090 seconds
Powered by Kunena Forum