2.8 pre locks up and wont load

Hello,

I recently upgraded to the latest master 2.8 from a previous 2.8(approx a year old, ver 277, i think) . Lcnc tries to load and locks up withe following error( see pi error attachment for complete log)

HAL: ERROR: pin_new(hm2_7i90.0.led.CR2976) called with already-initialized memory
HAL: ERROR: pin_new(hm2_7i90.0.led.CR2977) called with already-initialized memory
HAL: ERROR: pin_new(hm2_7i90.0.led.CR2978) called with already-initialized memory
HAL: ERROR: pin_new(hm2_7i90.0.led.CR2986) called with already-initialized memory
rtapi_app: caught signal 11 - dumping core

I had this all working actually moving my Hardinge with the rspi .Now Lcnc hang up on with the above error, suggestions??Thanks

Ok, things that make ya go danm.....In an attempt to make this issue go away, I uninstalled the newer 2.8 and put the latest 2.7, which would hang up loading the driver, I suspect I put the rtai version on instead of the sim.
Anyway..... I reloaded 2.8 this evening and got the same error with the rspi driver, but now the hm2-rspi driver works.Go figure, so...
It is a lathe config and if I try the newer joint/axis asignment like so

[AXIS_Z]
MIN_LIMIT = -10.
MAX_LIMIT = .25
MAX_VELOCITY = 3.3
MAX_ACCELERATION = 10.


## Z axis
[JOINT_1]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 3.3
MAX_ACCELERATION = 10.
ect
I get this
check_config: ERROR
(Using identity kinematics: trivkins)
[JOINT_1]MIN_LIMIT > [AXIS_Y]MIN_LIMIT (-10. > -1e99)
[JOINT_1]MAX_LIMIT < [AXIS_Y]MAX_LIMIT (.25 < 1e99)

check_config validation failed

The config will load with this:
[KINS]
KINEMATICS = trivkins
JOINTS = 3



[TRAJ]

AXES = 3
COORDINATES = X Z
HOME = 0 0 0 0
LINEAR_UNITS = inch
ANGULAR_UNITS = degree
CYCLE_TIME = 0.010
DEFAULT_VELOCITY = 3.3
MAX_VELOCITY = 3.3
DEFAULT_ACCELERATION = 14.0
MAX_ACCELERATION = 14.0
MAX_LINEAR_VELOCITY = 3.3

[AXIS_X]
MIN_LIMIT = -6.0
MAX_LIMIT = .08
MAX_VELOCITY = 3.3
MAX_ACCELERATION = 10.

##X axis
[JOINT_0]
TYPE = LINEAR
HOME = 0.000
MAX_VELOCITY = 3.3
MAX_ACCELERATION = 10.
BACKLASH = 0.000
INPUT_SCALE = -60000
OUTPUT_SCALE = 1.
OUTPUT_OFFSET = 0
MIN_LIMIT = -6.0
MAX_LIMIT = .08
FERROR = .015
MIN_FERROR = .004
HOME_OFFSET = 0
HOME_SEARCH_VEL = 1.
HOME_LATCH_VEL = -.5
HOME_USE_INDEX = YES
HOME_IGNORE_LIMITS = no
MAX_OUTPUT = 1.

# PID tuning params
DEADBAND = 0
P = 60.
I = 3.
D = 2.
FF0 = 0
FF1 = .020
FF2 = .02
BIAS = 0


[AXIS_Z]
MIN_LIMIT = -10.
MAX_LIMIT = .25
MAX_VELOCITY = 3.3
MAX_ACCELERATION = 10.


## Z axis
[JOINT_2]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 3.3
MAX_ACCELERATION = 10.
BACKLASH = 0.000
INPUT_SCALE = -60000
OUTPUT_SCALE = 1.000
OUTPUT_OFFSET = 0.0
MIN_LIMIT = -10.
MAX_LIMIT = .25
FERROR = .02
MIN_FERROR = .006
HOME_OFFSET = 0
HOME_SEARCH_VEL = -1.
HOME_LATCH_VEL = .5
HOME_USE_INDEX = YES
HOME_IGNORE_LIMITS = no
MAX_OUTPUT = 1.0
# PID tuning params
DEADBAND = 0
P = 60.
I = .5
D = .8

FF0 = 0
FF1 = .011
FF2 = .0002
BIAS = 0

##spindle
[SPINDLE_1]
MAX_VELOCITY = 50.
MAX_ACCELERATION = 20.0
BACKLASH = 0.000
INPUT_SCALE = 8192
##8192
OUTPUT_SCALE = 1.
OUTPUT_OFFSET = 0.0

MAX_OUTPUT = 1.0
# PID tuning params
DEADBAND = 0.000015
P = 0
I = 0
D = 0
FF0 = 0.02
FF1 = 0
FF2 = 0
BIAS = 0

##mpg
[JOINT_3]
INPUT_SCALE = 100
MAX_VELOCITY = 3.3
MAX_ACCELERATION = 5.
[EMCIO]

I suspect Im missing something. A couple weeks ago I had an issue with z homing, tell it to home and it sat still and zero's it self, never searches for the limit switch.Thanks

Got it. The syntax in the ini file has to be exact. That was also the source of the homing problem. The sim may load the old style axis/joint definitions, but it seems to get the axis's to home they have to be in assigned order , meaning if you have a joint for Y , you can't home Z until Y is homed.

JR1050 wrote:

Got it. The syntax in the ini file has to be exact. That was also the source of the homing problem. The sim may load the old style axis/joint definitions, but it seems to get the axis's to home they have to be in assigned order , meaning if you have a joint for Y , you can't home Z until Y is homed.

Thats not correct. The HOME_SEQUENCE in the .ini file determines the order of homing. If you have a joint axis such as a gantry, the sets of joints making up an axes needs to be an identical negative number. The 2.8 homing configuration docs is quite precise about how it all works.