Hello Guest it is July 03, 2022, 08:43:00 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - siderits

Pages: 1
1
General Mach Discussion / Re: Maxnc
« on: November 16, 2010, 09:12:22 AM »
Another board said that the leasing company padlocked the warehouse and they don't seem to have filed taxes since 08'.
C and M own the shares.  I'm in the same boat, by the way, have been working on getting the thing to work for 3 years. 
Now its a hobby.  I'll admit to learning a lot during the journey.

2
Probably not himem.sys memory management because same thing happens on the Embedded computer that's not connected to the Windows system.

I'll try it anyway.  When booting the computer hit F12 until you get the DOS screen and then you can disable memory management.  Or edit the config.sys in the root (as per googled instructions).

Do this at your own risk, I'm trying it so maybe you should wait and see if I mess up first.

3
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.

Pages: 1