Direction signals not working properly
Posté : lun. nov. 05, 2007 12:13 am
I've tried using Jedicut with several of the XP DLLs that come with the download and had little joy
With the MaxComXP DLL the steppers all move fine but the direction signals (3,5,7,9) are not changing on the parallel port so they only move in one direction.
With the VisualCNCXP DLL I can get X1, X2, Y1 all moving correctly (in both directions) but the direction signal (Pin 9 of the DB25) doesn't toggle to indicate direction.
I also find on the VisualCNC XP DLL that I can not vary the step-rate of the motors and they step exceedingly slowly (external timer is de-selected and I *can* vary the step speed on the MaxComXP DLL).
Any ideas?
Running Windows XP and I've tried two machines just to verify that there's not a hardware fault. This machine also runs the Linux-based EMC CNC software with no problems at all so I don't think it's hardware.
One clue -- both machines on which I installed JediCut came up with an error that said soemthing like "unable to connect with IO.sys but it is running" when first started. Is this normal? The error message has not reappeared.
With the MaxComXP DLL the steppers all move fine but the direction signals (3,5,7,9) are not changing on the parallel port so they only move in one direction.
With the VisualCNCXP DLL I can get X1, X2, Y1 all moving correctly (in both directions) but the direction signal (Pin 9 of the DB25) doesn't toggle to indicate direction.
I also find on the VisualCNC XP DLL that I can not vary the step-rate of the motors and they step exceedingly slowly (external timer is de-selected and I *can* vary the step speed on the MaxComXP DLL).
Any ideas?
Running Windows XP and I've tried two machines just to verify that there's not a hardware fault. This machine also runs the Linux-based EMC CNC software with no problems at all so I don't think it's hardware.
One clue -- both machines on which I installed JediCut came up with an error that said soemthing like "unable to connect with IO.sys but it is running" when first started. Is this normal? The error message has not reappeared.