3
« on: November 15, 2010, 06:32:24 AM »
Same issue with mine for 3 yrs. I think MAXNC got padlocked by the warehouse leasing company a few weeks ago (another post on a different site) and there has been no response since. No tax filing either since 2008. I don't want anybody's company to fail but if true then the public should be aware.
Anyway, I've replaced the controller and tweaked the debounce (Chris seemed to think this might be the answer) plus put a filter on the power supply.
Same problem, no better. Also same problem when using the embedded computer as the connected computer so the error has to be in the controller/servo interface. The ways are clear so the gantry isn't binding. It DOES seem to be missing instructions
and what I'm trying to find more information about something that came from another post that talked about the PIN setup for PIN #10, it said:
PIN#10 NOTE: MOVE ENABLE IS USED TO STOP THE COMPUTER STREAM OF CODES UNTIL THE SERVO
MOTORS CATCH UP. ON TIME-OUT IT WILL PRODUCE A SERVO ERROR.
If I could find out how to lengthen that Time out interval, I hope that might fix it. I may try going back the the
debounce and setting it much longer or much shorter to see if that has any effect.
The second area that I'm looking into came from the spotty manual from MAXNC and suggested that memory managers like
HIGHMEM.sys or a ??386 memory manager might be the problem. Will try to disable memory management to see if that's somehow
interrupting the commands over the MODBUS.
Will also look at the wiring guide for MACH3 to see if the setup has any functions to monitor the serial communication.
Will keep you posted if successful.