New firmware release 1.17a
-
What happens if you send G1 Y260 manually?
That message means that the firmware thinks you are trying to move the head to a point a long way outside your 5 bed probe points. It most often occurs on homing moves, because the G1 S1 homing moves necessarily have an endpoint that may be well outside the bed.
You might want to try putting a G90 command before that G1 command, just in case it has somehow got into relative coordinates mode.
-
When that G1 Y260 F3000 move occurs, the printer is already at X0 Y0 due to the G1 X0 Y0 F5000 in pause.g. After the moves in cancel.g are acted on, the dwc & paneldue shows X10 Y260. None of the axes positions are outside the defined printer area of 300x270x200, before, during and after.
The G91 has a G90 in the two macros and they only surround the z moves.
The print files that slic3r makes, have a M83 & G90 at the beginning.
-
The M226 issue is fixed in 1.17b, which I am about to release. My thanks to chrishamm for the fix.
I try V. 1.17b and the problem is fixed! thank you David and chrishamm !!!
-
The problem with webcam images is that the target URI has to be different every time a new photo is requested. I saw the other day that JQuery does it a bit different and that they use &= <random>instead of &dummy=<random>. Are you able to open http://localip/webcapture.jpg?command=snap&channel=0&=346345234 or does it give you an empty image as well?
For MJPEG sources I'm planning to allowing a static image URL by setting the update interval to 0. This will be implemented in DWC 1.14a.</random></random>
Hi and thanks for responding so quickly. Anything that appends another "&" cause no image to be displayed. If another character is used such as a ";", the camera ignores it and displays the image.
Are you able to open http://localip/webcapture.jpg?command=snap&channel=0&_=346345234 or does it give you an empty image as well?
No image is displayed.
-
When that G1 Y260 F3000 move occurs, the printer is already at X0 Y0 due to the G1 X0 Y0 F5000 in pause.g. After the moves in cancel.g are acted on, the dwc & paneldue shows X10 Y260. None of the axes positions are outside the defined printer area of 300x270x200, before, during and after.
The G91 has a G90 in the two macros and they only surround the z moves.
The print files that slic3r makes, have a M83 & G90 at the beginning.
Copied the cancel.g file over to the corexy with the DuetWifi. It worked fine, then changed the Y260 to Y300 for the max y on that printer, and it still worked fine.
Updated Duet085 to 1.17b, problem still there. There must be something odd going on with my Duet085. It doesn't always show the M117 on the PanelDue and every so often on power up the ethernet is unresponsive. Since the problem stops by using Y240, I'm not going to worry about it.
