New firmware 1.09k-dc42

For me PanelDue stopped working with 1.09k. With 1.09j everything was fine. I have to use checksum (M575 P1 B57600 S1) in my setup as otherwise PanelDue stopped my prints randomly. Could that be the reason? I am using PaneDue V 1.11. Will tryx without checksum enabled, but printer is busy right now...

The UART on the atsam3x8e mcu has unfortunately only a 1 character receive buffer. As a result, it is quite easy to get dropped characters in the transmission stream from the PanelDue to the Duet. This means for example that the M105 or M408 command sent by PanelDue might be interpreted as M0. I implemented the M575 S1 option to allow the Duet to recognise that characters have been lost. In 1.09k I also increased the UART interrupt priority to reduce the chance of dropping characters. I still use the checksum option with my PanelDues and 1.09j 1.09k, so I am unable to understand why your PanelDue has stopped working.

Edited 1 time(s). Last edit at 10/01/2015 05:08PM by dc42.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

> I still use the checksum option with my PanelDues and 1.09j, so
I assume the "j" here is a typo and you mean "k" ?

If so I will start testing once my big print stops and report back.

Thanks!

Sorry, it was a typo, I meant 1.09k.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Quote
dc42
...btw I published a firmware configuration guide at [reprap.org].

Much appreciated, Thank You!

Erik

Ok, I did go back to 1.09j and PanelDue worked right away. Problem is that it didn't pass the "double blind test": when I went back to 1.09k it also worked... ???... Before with 1.09k it didn't work for multiple days and multiple power cycles, so not sure what was going on.... I'm certain there have been no hardware or config changes in between...
So looks like a false alert for know .. sorry for that...
Thanks!

Hi David.

I am getting this error after doing a G32 command.
20:03:38
Error: Bed calibration error: 0 points provided but only 3, 4 and 5 supported
20:03:27
G32
Bed equation fits points [38.8, 19.5, 0.039] [38.8, 199.5, -0.196] [180.8, 199.5, -0.735] [180.8, 19.5, 1.507]

Here is my config file.

; Configuration file for RepRap Ormerod 2
; RepRapPro Ltd
;
; Copy this file to config.g if you have an Ormerod 2
; If you are updating a config.g that you already have you
; may wish to go through it and this file checking what you
; want to keep from your old file.
;
M111 S0 ; Debug off
M550 PMick's Ormerod 2 ; Machine name (can be anything you like)
M551 Preprap ; Machine password (currently not used)
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address
M552 P192.168.1.99 ; IP address
M553 P255.255.255.0 ; Netmask
M554 P192.168.1.254 ; Gateway
M555 P2 ; Set output to look like Marlin
M570 S160 ; Set hot end timeout
G21 ; Work in millimetres
G90 ; Send absolute corrdinates...
M83 ; ...but relative extruder moves
M574 X0 Y1 Z0 S1 ; set endstop configuration (Y endstop only, at low end, active high)
M906 X800 Y1000 Z800 E800 ; Set motor currents (mA)
M563 P1 D0 H1 ; Define tool 1
G10 P1 S0 R0 ; Set tool 1 operating and standby temperatures
M92 E412 ; Set extruder steps per mm
M558 P1 X0 Y0 Z1 H3 F200 T5000 ; smart IR Z probe, used for homing Z axis only, dive height 3mm, probe speed 200mm/min, travel speed 5000mm/min
G31 P500 Z1.30 ; Set the probe height and threshold (deliberately too high to avoid bed crashes on initial setup)
M305 P0 R4700 ; Set the heated bed thermistor series resistor to 4K7
M305 P1 R4700 ; Set the hot end thermistor series resistor to 4K7
M557 P0 X38.79 Y19.47 ; Four...
M557 P1 X38.87 Y199.49 ; ...probe points...
M557 P2 X180.76 Y199.49 ; ...for bed...
M557 P3 X180.74 Y19.47 ; ...levelling
M557 P4 X100 Y100 ; 5th probe point for levelling (un-comment this if you are using a dc42 differential IR probe)
;M569 P0 S0 ; Reverse the X motor
;M556 S78 X-1.0 Y0.75 Z1.25 ;

Many thanks Mick

Setting the bed probe points using M557 commands is the old way, but it should still work if you don't have a bed.g file. So I think either you do have a bed.g file, or a bug has crept in that causes that error message if bed.g is not present. I'll test it when I get a chance. Feel free to remind me by PM in a couple of days.

Edited 1 time(s). Last edit at 10/08/2015 05:04PM by dc42.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Thanks David i did have a bed.g file on the SD card. I have removed that now and it is working fine :-) When you say using M557 is the old way what is the new way?

Many Thanks.
Mick.

The new way is to use a bed.g file. But I still use M557 too. Can you post your bed.g file?

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Thanks David here is my bed.g file contents.

G1 Z10 F200
G1 X38.79 Y19.47 F2000
G30 P0 Z-100000
G1 Z10 F200
G1 X38.79 Y199.49 F2000
G30 P1 Z-100000
G1 Z10 F200
G1 X180.76 Y199.49 F2000
G30 P2 Z-100000
G1 Z10 F200
G1 X180.76 Y19.47 F2000
G30 P3 S Z-100000
G1 Z10 F200
G1 X100 Y100 F2000
G30 P4 S Z-100000
G1 Z10 F200

Thanks, looks like the firmware is producing a spurious message when you use S0 or just S on the last G30 command. Changing to to S5 (as you have 5 probe points in the file) will probably avoid it. But I'll investigate it with a view to implementing a fix in the next release.

Edited 2 time(s). Last edit at 10/09/2015 05:33PM by dc42.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Is it okay that he uses the "S" for two times? I do not think so. It should be:

G1 Z10 F200
G1 X38.79 Y19.47 F2000
G30 P0 Z-100000
G1 Z10 F200
G1 X38.79 Y199.49 F2000
G30 P1 Z-100000
G1 Z10 F200
G1 X180.76 Y199.49 F2000
G30 P2 Z-100000
G1 Z10 F200
G1 X180.76 Y19.47 F2000
G30 P3 Z-100000
G1 Z10 F200
G1 X100 Y100 F2000
G30 P4 S Z-100000
G1 Z10 F200

---

Slicer: Simplify3D 4.0; sometimes CraftWare 1.14 or Cura 2.7
Delta with Duet-WiFi, FW: 1.20.1RC2; mini-sensor board by dc42 for auto-leveling
Ormerod common modifications: Mini-sensor board by dc42, aluminum X-arm, 0.4 mm nozzle E3D like, 2nd fan, Z stepper nut M5 x 15, Herringbone gears, Z-axis bearing at top, spring loaded extruder with pneumatic fitting, Y belt axis tensioner
Ormerod 2: FW: 1.19-dc42 on Duet-WiFi. own build, modifications: GT2-belts, silicone heat-bed, different motors and so on. Printed parts: bed support, (PSU holder) and Y-feet.
Ormerod 1: FW: 1.15c-dc42 on 1k Duet-Board. Modifications: Aluminium bed-support, (nearly) all parts reprinted in PLA/ ABS, and so on.

Quote
Treito
Is it okay that he uses the "S" for two times? I do not think so. It should be:

G1 Z10 F200
G1 X38.79 Y19.47 F2000
G30 P0 Z-100000
G1 Z10 F200
G1 X38.79 Y199.49 F2000
G30 P1 Z-100000
G1 Z10 F200
G1 X180.76 Y199.49 F2000
G30 P2 Z-100000
G1 Z10 F200
G1 X180.76 Y19.47 F2000
G30 P3 Z-100000
G1 Z10 F200
G1 X100 Y100 F2000
G30 P4 S Z-100000
G1 Z10 F200

Well spotted! That's almost certainly the problem.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Maybe there is a possibility to catch this error? I often changed my bed.g and tried 4- and 5-point probes so I had to add/ remove this "S" and I knew about the function as I was forced to read the documentation here several times. As you wrote about "S" I remembered it.
So I am not sure if this problem is related to the other thread.

---

Slicer: Simplify3D 4.0; sometimes CraftWare 1.14 or Cura 2.7
Delta with Duet-WiFi, FW: 1.20.1RC2; mini-sensor board by dc42 for auto-leveling
Ormerod common modifications: Mini-sensor board by dc42, aluminum X-arm, 0.4 mm nozzle E3D like, 2nd fan, Z stepper nut M5 x 15, Herringbone gears, Z-axis bearing at top, spring loaded extruder with pneumatic fitting, Y belt axis tensioner
Ormerod 2: FW: 1.19-dc42 on Duet-WiFi. own build, modifications: GT2-belts, silicone heat-bed, different motors and so on. Printed parts: bed support, (PSU holder) and Y-feet.
Ormerod 1: FW: 1.15c-dc42 on 1k Duet-Board. Modifications: Aluminium bed-support, (nearly) all parts reprinted in PLA/ ABS, and so on.

Thanks guys I will remove that and see if it then does the 5 point calibration properly :-)

Edited 1 time(s). Last edit at 10/10/2015 05:06AM by Mick747.

Hey Mick,

I am sorry but you did a mistake and it is up to you to remove your fault. I only asked dc42 if he can catch this error. "S" means store and you store your settings after the 4th probe point so until you do not change your bed.g the 5-probe-leveling will never work for you.

---

Slicer: Simplify3D 4.0; sometimes CraftWare 1.14 or Cura 2.7
Delta with Duet-WiFi, FW: 1.20.1RC2; mini-sensor board by dc42 for auto-leveling
Ormerod common modifications: Mini-sensor board by dc42, aluminum X-arm, 0.4 mm nozzle E3D like, 2nd fan, Z stepper nut M5 x 15, Herringbone gears, Z-axis bearing at top, spring loaded extruder with pneumatic fitting, Y belt axis tensioner
Ormerod 2: FW: 1.19-dc42 on Duet-WiFi. own build, modifications: GT2-belts, silicone heat-bed, different motors and so on. Printed parts: bed support, (PSU holder) and Y-feet.
Ormerod 1: FW: 1.15c-dc42 on 1k Duet-Board. Modifications: Aluminium bed-support, (nearly) all parts reprinted in PLA/ ABS, and so on.

LOL it was a typo i meant to say I will remove not U :-)

In this case all is good. It sounded like you are waiting for dc42 to change his firmware in a way that your faulty bed.g will work. Nice typo in this case.

---

Slicer: Simplify3D 4.0; sometimes CraftWare 1.14 or Cura 2.7
Delta with Duet-WiFi, FW: 1.20.1RC2; mini-sensor board by dc42 for auto-leveling
Ormerod common modifications: Mini-sensor board by dc42, aluminum X-arm, 0.4 mm nozzle E3D like, 2nd fan, Z stepper nut M5 x 15, Herringbone gears, Z-axis bearing at top, spring loaded extruder with pneumatic fitting, Y belt axis tensioner
Ormerod 2: FW: 1.19-dc42 on Duet-WiFi. own build, modifications: GT2-belts, silicone heat-bed, different motors and so on. Printed parts: bed support, (PSU holder) and Y-feet.
Ormerod 1: FW: 1.15c-dc42 on 1k Duet-Board. Modifications: Aluminium bed-support, (nearly) all parts reprinted in PLA/ ABS, and so on.

Quote
Treito
Maybe there is a possibility to catch this error? I often changed my bed.g and tried 4- and 5-point probes so I had to add/ remove this "S" and I knew about the function as I was forced to read the documentation here several times. As you wrote about "S" I remembered it.
So I am not sure if this problem is related to the other thread.

It does catch this error - it produces an error message! But perhaps the message text could be improved.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

David,

I've just pulled my Ormerod 1 with your Hot End upgrade out of mothballs and updated the firmware from your 0.78q release to 1.09k and updated the web interface files to the latest version.
The issue I now have is that the heating monitor for the bed works fine in terms of monitoring the bed temperature and being able to set it with the active drop down but the Head 1 Active and Standby drop downs do not effect the hot end temperature. Head 2 standby setting will start the heater and the temperature change is shown in the Head 1current box.
The only command I have in config.g which appears heater related is M563 P1 D0 H1 ; Define tool 1 to use extruder drive 0 and heater 1 (heater 0 is the hot bed).

Have I missed a change which was implemented between 0.78 and 1.09 and if so could you advise what I need to reset please.

Dave

Hi Dave,

you should compare the new config.g with your one. There are some new options which are explained in the file like the temperatures.

Kind regards,

Sven

---

Slicer: Simplify3D 4.0; sometimes CraftWare 1.14 or Cura 2.7
Delta with Duet-WiFi, FW: 1.20.1RC2; mini-sensor board by dc42 for auto-leveling
Ormerod common modifications: Mini-sensor board by dc42, aluminum X-arm, 0.4 mm nozzle E3D like, 2nd fan, Z stepper nut M5 x 15, Herringbone gears, Z-axis bearing at top, spring loaded extruder with pneumatic fitting, Y belt axis tensioner
Ormerod 2: FW: 1.19-dc42 on Duet-WiFi. own build, modifications: GT2-belts, silicone heat-bed, different motors and so on. Printed parts: bed support, (PSU holder) and Y-feet.
Ormerod 1: FW: 1.15c-dc42 on 1k Duet-Board. Modifications: Aluminium bed-support, (nearly) all parts reprinted in PLA/ ABS, and so on.

The convention now is that tool numbers start at 0 instead of 1. So change P1 to P0 in your M563 and G10 commands, and change T1 to T0 in your start gcode. Also check your version of the web interface, it should be DuetWebControl 1.06.

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Sven, David,

Thanks for the prompt responses, they were the pointers I needed. I've made the changes and also adapted the config.g from the latest firmware on Git.

Dave

Hello David,

I have some trouble with your FW. I often have to cancel prints for maybe known reasons. So after I pause and cancel a print the printer sometimes is not reacting or to be more precise it reacts only with a big delay. But it seems that only parts of the web-interface are affected. I can change temperatures but not drive or vice versa. Really strange.

Best regards,

Sven

---

Slicer: Simplify3D 4.0; sometimes CraftWare 1.14 or Cura 2.7
Delta with Duet-WiFi, FW: 1.20.1RC2; mini-sensor board by dc42 for auto-leveling
Ormerod common modifications: Mini-sensor board by dc42, aluminum X-arm, 0.4 mm nozzle E3D like, 2nd fan, Z stepper nut M5 x 15, Herringbone gears, Z-axis bearing at top, spring loaded extruder with pneumatic fitting, Y belt axis tensioner
Ormerod 2: FW: 1.19-dc42 on Duet-WiFi. own build, modifications: GT2-belts, silicone heat-bed, different motors and so on. Printed parts: bed support, (PSU holder) and Y-feet.
Ormerod 1: FW: 1.15c-dc42 on 1k Duet-Board. Modifications: Aluminium bed-support, (nearly) all parts reprinted in PLA/ ABS, and so on.

Sven,

I often cancel print too but I haven't seen this. Is there a particular sequence that triggers it? When it happens, does it help if you close the browser tab and open a new one?

---

Large delta printer [miscsolutions.wordpress.com], E3D tool changer, Robotdigg SCARA printer, Crane Quad and Ormerod

Disclosure: I design Duet electronics and work on RepRapFirmware, [duet3d.com].

Hello David,

thanks for the answer. It does not happen regularly. I pause and cancel the print immediately that means both buttons in the shortest time possible. Most effective is when you first activate the bed and than the nozzle heater. I think it is related to the nozzle heater as I today switched the sequence because sometimes I could not activate the bed after I activated the nozzle heater.

; Pause macro file
G1 E-4 F2500		; retract 4mm
G91					; relative moves
G1 Z5 F5000			; raise nozzle 2mm
G90					; absolute moves
G1 X0 Y200 F5000	; move head out of the way of the print

BTW I use S3D 3.02

---

Slicer: Simplify3D 4.0; sometimes CraftWare 1.14 or Cura 2.7
Delta with Duet-WiFi, FW: 1.20.1RC2; mini-sensor board by dc42 for auto-leveling
Ormerod common modifications: Mini-sensor board by dc42, aluminum X-arm, 0.4 mm nozzle E3D like, 2nd fan, Z stepper nut M5 x 15, Herringbone gears, Z-axis bearing at top, spring loaded extruder with pneumatic fitting, Y belt axis tensioner
Ormerod 2: FW: 1.19-dc42 on Duet-WiFi. own build, modifications: GT2-belts, silicone heat-bed, different motors and so on. Printed parts: bed support, (PSU holder) and Y-feet.
Ormerod 1: FW: 1.15c-dc42 on 1k Duet-Board. Modifications: Aluminium bed-support, (nearly) all parts reprinted in PLA/ ABS, and so on.

i think the print will pause at a certian point in the print not right away ,atleast thats my experiance so far ,it almost never stoped instantly after i pressed the pause button. it finished 1 line or 2 before it stoped and lifted and moved the head out of the way.

Hi Dave.

I am having issues connecting to my ormerod 2 since upgrading the firmware and it seems to be getting worse. I also have been having problems uploading files too. I seem to get a lot of ajax errors. Any clues as to why this might be?

I am on OSX El Capitan and use Chrome, Safari, and Firefox. I have given up trying to connect with Chrome and Safari altogether and only use Firefox but that is now failing. I have attached two images with some errors if that helps.

Cheers Mick.

Edited 1 time(s). Last edit at 11/02/2015 12:46PM by Mick747.

Hi all i think i have solved the issue. I had been using the micro sd card adapter and then placing that in my macbook sd card slot to format and put files on it. I have now used a usb adapter and gone through windows to format and install the files to the card and all seems to be working well again. :-)