Advanced Search

Maybe post your hal and ini files.

I guess that's the bit I am missing.
In the hal file, there are no "input-a" anything for the X,Y and Z encoders so I don't get how lcnc knows what anything is connected to.

Sorry.

The raw encoder pins have names like:

hm2_7i92.0.encoder.03.input-a
hm2_7i92.0.encoder.03.input-b
hm2_7i92.0.encoder.03.input-index

Thank you for helping. it is working. having some troubles with the WIFI see new work can't connect. What file are recommended for the byte to bot set up with the Parallel Port Raspberry Pi Hat and 5 axis breakout board.

Hi Tim,
your measurements are correct,
the code is wrong

I have fixed the shiftreg plugin,
but the 6.4Mhz of the w5500 are correct,
more is not possible with the ice40up5k on 30Mhz clock.

Thanks !

Joco wrote:

And that behaviour continues under scurve planner?  That was what I was referring to. Not what standard planner does.

@Joco - my apologies, I completely misunderstood your original warning.  I thought you were concerned that the current TP maybe didn't lock out FH and motion-inhibit as advertised, and perhaps that situation was carried in to Grotius' s-curve TP.

I have not tested the s-curve TP's behavior.

Sorry to all for the unnecessary tangent.

I've failed to work out how to use a spare encoder input on the 7i77 as a Limit switch input.
I've started out by telling PNCConf that the switches are connected to the I/O Field inputs so I can see the syntax, for instance 
net min-x     <=  hm2_7i92.0.7i77.0.0.input-00     for the X limit minus.
Was planning then to edit this line to match an encoder.

But when I study the hal file posted here, I cannot see how the encoder input pins are called. I was expecting there to be similar 7i92..7i77 references in the Joint 0 section for instance and there are for the analogue outputs, but not against the encoders.
Can you help please.
Thanks

Well done!
I will update/patch and try some more codes on my testmachines this evening (living in Germany btw.). I will report back then.

@Julian,

The file seems to run now under -> ./start_axis_9
I removed some segment length checks like : < 1e-12
This is a very tiny value, but it was enough to halt the planner so now and then.
Code is updated.
 

Hello
i have a similar problem. What was the solution ? where connection PUL+ PUL- DIR+ DIR- on the servo drive ?