I've been away a while - now I could use some help/advice

David J

It's been a very long while since I've felt the need to access this forum - my Duet board hasn't required attention for a very long time, which is a testament to its functionality and reliability. Now I may need to make changes as I am awaiting delivery of a PanelDue 7i from Ooznest. I am wondering if the firmware I currently have loaded will match that in the display.

My current setup is:

Duet 0.6 (genuine, not clone)
Firmware 1.19.2
Web interface 1.19

Now this is probably well out of date, but it's been working well on my CoreXY and I hadn't felt the need to update!

As far as the wiring is concerned, I have no problems. Also, I'm using the on-board regulator rather than the add-on one, so the documentation suggests that I will have no trouble supplying power to the display.

So the help/guidance I'm seeking is:

Will the PanelDue work with this firmware, or will I have to update?
Where will I find the firmware if I need to update? I have looked, but it's not easy to identify the version for this old board.

All advice gratefully accepted,
David

dc42

I think the latest PanelDue firmware (1.24) will work with that version of RepRapFirmware, but it hasn't been tested.

If you do need to update the firmware on the Duet, the latest version for your board is at https://github.com/Duet3D/RepRapFirmware/releases/tag/2.05.1.

David J

Thanks David.

Am I right in thinking that it's the reprapfirmware.bin file I need from that location?

And should I use the DuetWebControl-1.22.6.zip with that?

(It's been so long since I updated this thing - I'll have to go and find the instructions!

David

dc42

@David-J said in I've been away a while - now I could use some help/advice:

Am I right in thinking that it's the reprapfirmware.bin file I need from that location?
And should I use the DuetWebControl-1.22.6.zip with that?

Yes to both.

David J

UPDATE: I've now received my PanelDue and wired it up - and it's mostly working.

The only problem I'm getting is that it can't run the macros. It lists them, but when I select one it comes up with

Macro file "0:/macros/<filename>" not found

Where <filename> is the correct name for whatever I've selected.

Odd that it lists them but can't find them to run, but maybe an update is required to get this working properly.

Now I need to get an enclosure sorted (I've seen yours on Thingiverse!)

David J

OK - I've updated the firmware and the web interface. Now, when click on home all axes, I get the error "G0/G1 insufficient axes homed". I also get this error when I try to do most things. Also getting "Heater 0 appears to be overpowered" error.

Presumably there were some config changes between version 1.19.2 and the latest - where can I find details?

And the other problem is... I can't print an enclosure!

All the designs I've found for the PanelDue 7i come out to around 205 - 210mm, and I have the choice of a 200x200 CoreXY or a 230mm diam Kossel. Sigh.

Never mind - time to design a 2-part front panel! It will be mounted on a backing plate anyway, so there's no problem with it falling apart in the future.

PaulHew

@David-J Hi, please post your config.g

Regards,
Paul

dc42

@David-J said in I've been away a while - now I could use some help/advice:

OK - I've updated the firmware and the web interface. Now, when click on home all axes, I get the error "G0/G1 insufficient axes homed". I also get this error when I try to do most things. Also getting "Heater 0 appears to be overpowered" error.
Presumably there were some config changes between version 1.19.2 and the latest - where can I find details?

Read the upgrade notes section of https://github.com/Duet3D/RepRapFirmware/blob/dev/WHATS_NEW.md for the firmware you have installed and for every firmware version you skipped over.

David J

OK - I get the message - RTFM!

Thanks again David

deckingman

@David-J I can give you a clue (because I am in a generous mood) to limit the amount you have to read.

One of the firmware updates along the way made a change (presumably at the request of OEMs) which prevents axis movement, other than homing moves, until the axes have been homed. The rationale being that the firmware will respect axis limits so you can't inadvertently send a carriage crashing into the frame. BUT, in order to do that, the firmware needs to know where the print head is and what the axes limits are, and the only way to establish those parameters is to home the printer. One thing that catches a lot of people out, is that they have a Z move in their home X or home Y to move the print head away from the build plate( or vice versa). That move will through up the error if you are using RRF 2.02 or later, so you'll need to use an "H" parameter with that Z move. Alternatively, if you want to restore the behaviour to how it was before, you can put M564 H0 at the end of your config.g file - but heed what I said about this not catching moves which might crash a carriage into the bed (although you are likely used to it and already aware of the danger).

David J

@deckingman It's OK - I spotted that one!

I'm good now, I think. All seems to be behaving itself... (he says quietly)

Once I've finished printing a 3DBenchy I'll be designing my multi-part PanelDue enclosure. I've got it sorted in my head, just need to get it into OpenSCAD. If it works, it will be published!