motley
Posts: 5
Joined: Sat Apr 30, 2016 4:49 am

Connection problem with Duet 0.8.5

I have a Prusa Mendel type with a Duet 0.8.5 controller, using Pronterface I can run each axis without problem.

The printer is connected to a Lenovo T510 running 64 bit Win7 Ult.

Initially I could't get Simplify3D to connect, but a couple of posts on this forum led me to uncheck the option 'Wait for startup command' in the menu Tools - Firmware Configuration - Communications. Interestingly this option is not saved between sessions. With this option unchecked communications with the printer were established.

However trying to test the comms by using the jog controls (Tools - Machine Control Panel - Jog Controls) results in one movement only, sometimes not even that. I can see the Gcode being generated but the printer does not respond. As I said at the top of this post using Pronterface the machine responds as expected.

I chose to try Simplfy3d having seen the demo video and was impressed by the fine tuning available and setup choices. However it's all to not avail if I can't connect reliably.

All help gratefully received,

Thanks,

Chris
andrewk72
Posts: 161
Joined: Fri Apr 29, 2016 5:43 am

Re: Connection problem with Duet 0.8.5

That setting won't be saved if one of your processes has the firmware overrides enabled (since that tells it to override your firmware settings any time you use that process). They have a video that explains it quite well: https://www.youtube.com/watch?v=NYPUAqT4UyI
motley
Posts: 5
Joined: Sat Apr 30, 2016 4:49 am

Re: Connection problem with Duet 0.8.5

Andrew,

Thanks for the info and video link - I have had a play around and now have communications - not sure I fully understand it all yet but at least I have movement.

It's an old machine which I never quite got working before time pressures forced me to delay the build.

First the thermistor calibrations, then the movements are in reverse as is the limit switch logic, still a little progress today :-)

Again thanks for your help...

Chris

Return to “Troubleshooting and Bug Reports”