chmt36va machine.xml concerns

[Nathaniel Horne]

Hey everybody! I'm just trying to figure out why we're running into some errors that we are having with our Charm High chmt36va. We've been trying to get our machine picking and placing for about 6 months now, but there seem to be more errors and bugs than anything else.

We had been using our own machine.xml file (listed below as previousmachine.xml), but we wanted to see if we could sidestep the MOUNTAIN of errors we were experiencing by loading a machine.xml file from someone who already had a functional chmt36va.

We followed a few links to get to Jan's machine.xml file (attached below as jansmachine.xml). However, when we uploaded that to our .openpnp2/ folder, we couldn't even turn the machine on. Screenshots listed down below.

I guess we're at a loss as to what we're doing wrong and where we should even go from here.

Where we got Jan's machine.xml file: https://github.com/janm012012/Smoothieware-CHMT

[Jan]

Hi Nathaniel!
Please consider asking OpenPnP related questions in the OpenPnP group.
There are others running this machines successful for years that are
very happy to help you.
Your error message suggests, that the COM port on your computer is
different (or the serial link is broken). Please visit Machine Setup ->
Drivers -> GCodeAsyncDriver -> Configuration and find the Serial Port
setup at the end.

Jan

> --
> You received this message because you are subscribed to the Google
> Groups "Desktop Pick and Place" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to desktop-pick-and-...@googlegroups.com
> <mailto:desktop-pick-and-...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/desktop-pick-and-place/5a3b5023-3cab-4c9b-bb1a-53fd3f48f4fbn%40googlegroups.com <https://groups.google.com/d/msgid/desktop-pick-and-place/5a3b5023-3cab-4c9b-bb1a-53fd3f48f4fbn%40googlegroups.com?utm_medium=email&utm_source=footer>.

[Nathaniel Horne]

Hello Jan! 

Thank you for responding so soon. Apologies I haven't been able to respond up until this point. Switching to a different com port did the trick. We'll keep you posted if anything else comes up.

Nathaniel