|
|
Topic: Yasnac MX2 Drip Feeding
|
By: Guest | Posted on: Mar 2 2011 at 10:06:34 PM | Im using the trial version of easy DNC to get my boss to buy the program. Using the recommended configurations (dncsetup.com/yasnac.html) for rs232 cable and parameters, using a rs232 wiring adapter plug. Configured the plug to the diagram and changing the parameters I get a TH parity error.
Any help is greatly appreciated. | |
By: Guest, | Posted on: Mar 2 2011 at 10:57:34 PM | It's usually beat to diagnose problems sending data from the CNC to the computer. Does everything come through correctly?
If you get lots of correct data on easydnc display but many characters are garbage, maybe max 40 to 50% of the characters are garbage then you have the parity in easydnc set incorrectly.
then send from computer to CNC memory ie not drip feeding. Do you still get the parity error?
I don't know If TH parity is the even/odd/none parity options that you see in easydnc settings or whether it's the CNC file end-of-block parity which can often be disabled inside the CNC parameters.
| |
By: Guest, | Posted on: Mar 3 2011 at 02:16:49 PM | Thanks for replying.
Just plugging my plug into cnc, with the specs of the link i provided I get a TH error. Doing nothing and hitting the go button on controller, or sending/receiving I get the error and even from the computer I get the error trying to send in to cnc.
I can not send out from computer, because once I go to EDIT, IN the cnc pops the TH error. Im thinking that the Error is being popped due to wrong plug, but thats the thing. Im using the suggested pattern from the link that I posted.
Ill be working on it today, so ill update any progress if there is any!
THANKS | |
By: Guest, | Posted on: Mar 3 2011 at 11:27:32 PM | Most CNC machines have more than one communications port. Maybe just one you can see on the outside of the machine but inside the machine may be another that you can't access. It's there for other options such as tape drives or other devices that can be connected.
If the CNC is setup using the wrong port then you could get the error because it can't see the cable. | |
Reply - add a comment to this topic.
You may enter letters, numbers and standard punctuation only. HTML and other scripts/tags will be rejected.
|
|
|