From: Sebastian K. <se...@hi...> - 2009-05-31 02:53:42
|
Terry wrote: > I tried out the hm2 today > I get an error from this group of lines in my .io file > > > # Connect limit/home switch outputs to motion controller. > newsig Xminlim bit > newsig Xmaxlim bit > newsig Xhome bit > linksp Xminlim <= hm2_5i20.0.gpio.024.in-not > linksp Xminlim => axis.0.neg-lim-sw-in > linksp Xmaxlim <= hm2_5i20.0.gpio.025.in-not > linksp Xmaxlim => axis.0.pos-lim-sw-in > linksp Xhome <= hm2_5i20.0.gpio.026.in-not > linksp Xhome => axis.0.home-sw-in > > > it was an hal error starting with: > > linksp Xminlim <= hm2_5i20.0.gpio.024.in-not > > Im sure all are bad but this one was first What was the error message? > if I comment these out then I can get EMC to fire up > but with a joint 1 error,I believe the A and B encoder > on that axis are switched from the mi520.This error > does not concern me as it is easy to fix in the wiring world > but the machine nneds to keep running so I need to fix hm2 except for that > joint error then I will rewire and move on If the encoder A and B lines in the hm2 firmware are reversed vs the older m5i20/hostmot firmware, then simply reversing the sign of the encoder scale in the hm2 .ini should take care of it. Or, as you say, swap the A and B wires, but you'd have to remember to swap them back if you want to run the older driver again. -- Sebastian Kuzminsky |