Small victory in the war against the Cincinnati cinturn 12u

I removed car-ready input xx
I added the motion in digital line I am now getting the following error. 
in Axis

Error: Index out of range, 5 not in [0..4] increase num_dio/EMCOT_MAX DIO=64)

turret motion is happening now, I am still getting failure to lock, due to what looks like a abort. I am attaching all of my current config files in in the zipped folder are the halscope captures of what's happening.

I've been googling on this for a bit now, and so far there nothing that should be causing emcio enumarated input failure, that I understand. 

 

So, it is counting the sense pins 0-3 as extra joints ? and the joints needs to be increased ?

Just so I understand exactly WHAT I am changing for the future

well, for sure, that's not the issue. I am not sure entirely why but the conv-float-32u seems to be adding joints everytime you move the turret.

as soon as I added the num_dio=8 after my first turret move, same error, this time 16

ERROR: index out of range, 15 not in [0..10[ (increase num_dio/EMCOT_MAX=64

and still ignoring my dwell command in the gcode to stop the motor and wait before locking the turret. Why does this work in the vismach sim but fail on my machine, which afaict is configured exactly the same way ???


 M66 P0 L3 Q60 ; wait for carousel finished
   
    M65 P0; stop carousel

should I change my current m64 g4 p5 to   

 M66 P1 L3 Q5 instead ?I keep getting locking failure because the motor keeps overshooting turret position. 

I've tried just a plain g4 pxx command, it ignores that as well

all of this is odd, these changes work in vismach sim, so either the sim is excessively fault tolerant, and that makes it useless for prototyping or I've stumbled onto some sort of failure mode that's not obvious

i did increase the num_dio to 64, just for shits and giggles, still getting errors, given the random numbers, it's probably some connection to float I'm to inexperienced to see.

IF Gcode it executed top to bottom left to right, the g4 pxxx is in the proper place, HOWEVER, the interpreter continues to ignore it. I did have a few M commands munged together.

Here is the clean up version of my ngc file, I am hoping that adding this line should create the pause. I have no IDEA why in vismach sim the g4 pxx commands work, but on my real hardware, they are ignored, every place I put them to slow the motion down.

M66 P0 L2 Q2 <

---

this line here should pause the machine for at least 2 seconds, m66 dio wait on input, p0 being the digital output we are watching, l2 going low from carousel and q2 is the hold time. after the wait time, the program should go back to executing.

If you see an error here, please highlight it in your reply.


o<toolchange> sub



; only unload the tool if there is a tool in the spindle
; This assumes that the carousel is already aligned correctly.
; It is important to unload the tool before shutting down the machine.



G53 G0 X16.00

O100 IF [#<selected_tool> GT 0]

M65 P1 ; unlock carousel
M66 P1 L4 Q1 ; wait for locked=false

O106 if [#5399 LT 0]
(abort, failed to unlock carousel)
O106 endif

M68 E0 Q#<selected_pocket> ;set the carousel to move to the right pocket

M64 P0 ; start carousel

M66 P0 L3 Q60 ; wait for carousel finished

M65 P0; stop carousel
M66 P0 L2 Q2 <

---

this line here should pause the machine for at least 2 seconds, m66 dio wait on input, p0 being the digital output we are watching, l2 going low from carousel and q2 is the hold time. after the wait time, the program should go back to executing.



M64 P1 ; lock carousel


M66 P1 L3 Q1 ; wait for locked=true
O108 if [#5399 LT 0]
(abort, failed to lock carousel)
O108 endif





O100 ENDIF





o<toolchange> endsub [1]


M2