New firmware release 1.17a
-
Duet 085, firmware 1.17a , web 1.14-rc1, 24vdc power, bed is on AC via ssr. A 24vdc fan @ 12vdc is cooling the driver section of the board. Today I downloaded and uploaded the firmware again, just in case there was a problem with the initial upgrade.
A print is running, hit pause, that works fine. Then I hit cancel, after cancel.g has run, the 'outside all triangles' error storm starts filling the screen. Yesterday, found that after using the web page's emergency stop, it never reconnects afterwards. Today, I found that a home all does stop the error once the z axis home has started. My DuetWifi hasn't done this. The file being printed has no affect. The Duet085 didn't do this on earlier firmware. At one time yesterday the web stopped responding and the paneldue stopped talking with the printer, I haven't been able to reproduce that.
First error in the log:
12:40:27 PM M0 H1
Print cancelled
Triangle interpolation: point outside all triangles!
Triangle interpolation: point outside all triangles!
Triangle interpolation: point outside all triangles!Then for every second after that, one or more:
Triangle interpolation: point outside all triangles!
–---------------------
The errors continue until a home all has started the z home part or a power cycle.-- This is right after a home all:
12:43:29 PMM122
=== Diagnostics ===
Used output buffers: 1 of 32 (12 max)
=== Platform ===
Memory usage:
Program static ram used: 45804
Dynamic ram used: 41412
Recycled dynamic ram: 2896
Current stack ram used: 2840
Maximum stack ram used: 6788
Never used ram: 1404
Last reset 00:06:08 ago, cause: software
Last software reset code: 0x0003, available RAM 1736 bytes (slot 4)
Spinning module during software reset: GCodes
Error status: 0
Max PWM loop count 0
Free file entries: 10
SD card 0 detected, interface speed: 21.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 33.6, current 41.2, max 47.8
Current date and time: 2017-01-07 12:43:28
Slowest main loop (seconds): 0.061630; fastest: 0.000108
=== Move ===
MaxReps: 4, StepErrors: 0, MaxWait: 4ms, Underruns: 0, 0
Bed probe heights: -0.173 0.031 -0.215 -0.006 -0.086 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is ready with "M122"
telnet is idle
file is idle
serial is idle
aux is idle
daemon is idle
=== Network ===
Free connections: 15 of 16
Free transactions: 23 of 24
=== Webserver ===
HTTP sessions: 1 of 8
FTP connections: 0, state 0
Telnet connections: 0, state 0
cancel.g:
M104 S0 ; turn off extruder
M140 S0 ; turn off bed
M106 S0 ; turn off part fan
G1 X10 F3000 ; move x to left
G1 Y260 F3000 ; move y to front
G91 ; relative moves
G1 Z10 ; raise z by 10
G90 ; absolute moves
M84 ; disable motorsOriginally had a G28 X instead of the G1 X10 F3000 line. The change had no affect.
Also ran a M122 during the error storm:
12:52:54 PM Triangle interpolation: point outside all triangles!
Triangle interpolation: point outside all triangles!
Triangle interpolation: point outside all triangles!=== Diagnostics ===
Used output buffers: 3 of 32 (18 max)
=== Platform ===
Memory usage:
Program static ram used: 45804
Dynamic ram used: 41412
Recycled dynamic ram: 2896
Current stack ram used: 2840
Maximum stack ram used: 6788
Never used ram: 1404
Last reset 00:15:34 ago, cause: software
Last software reset code: 0x0003, available RAM 1736 bytes (slot 4)
Spinning module during software reset: GCodes
Error status: 0
Max PWM loop count 0
Free file entries: 10
SD card 0 detected, interface speed: 21.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 32.3, current 41.5, max 48.5
Current date and time: 2017-01-07 12:52:54
Slowest main loop (seconds): 0.061462; fastest: 0.000183
=== Move ===
MaxReps: 4, StepErrors: 0, MaxWait: 4ms, Underruns: 0, 0
Bed probe heights: -0.289 -0.070 -0.311 -0.100 -0.703 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 0 is on, I-accum = 0.3
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is ready with "M122"
telnet is idle
file is idle
serial is idle
aux is idle
daemon is idle
=== Network ===
Free connections: 15 of 16
Free transactions: 22 of 24
=== Webserver ===
HTTP sessions: 1 of 8
FTP connections: 0, state 0
Telnet connections: 0, state 0Triangle interpolation: point outside all triangles!
-
I have the same issue as demonio669 Today 18:14. I also tried putting the M226 M25 in my print file and the printer went into a pause states and never ran the Pause macro file. Also i could not get anything to operate till i power cycled. This included sending the M24 command after disconnecting the browser and reconnecting the browser to the printer
-
I have the same issue as demonio669 Today 18:14. I also tried putting the M226 M25 in my print file and the printer went into a pause states and never ran the Pause macro file. Also i could not get anything to operate till i power cycled. This included sending the M24 command after disconnecting the browser and reconnecting the browser to the printer
Yes I also have to press the emergency stop button to control the printer again
-
The M226 issue is fixed in 1.17b, which I am about to release. My thanks to chrishamm for the fix.
-
Had some time. I noticed on my DuetWifi, cancel.g only has G1 Y300 and it works fine and that bed is 400x300. So, on the Duet085, I edited my cancel.g to find the culprit and it's the G1 Y260 F3000. Decreased the y to G1 Y250 F3000, Triangle interpolation: point outside all triangles! error storm occurs. If I lower it to G1 Y240 F3000, the error storm doesn't happen. Go back to G1 Y250 F3000, no problem. But changing it back to G1 Y260 F3000, error returns until I put it back to G1 Y240 F3000. Bed is defined to be 300x270. I even tried deleting and making a new cancel.g, no change. If the file has everything commented but the G1 Y260 F3000 line, it still does the error. The bed does go right where the G1 tells it to go.
-
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.
