Issues addressing Duet 0.6

JonnyBrylcreem

I don't suppose you have a copy of RepRapFirmware-1.09r-dc42 do you?

dc42

You can get old versions of RRF from GitHub because the complete release and source code history is in there.

JonnyBrylcreem

Thanks for getting back to me so quickly. I had already had a look on GitHub but I couldn't find an old enough version, I managed to find a copy of 1.09 on my PC though so I used that to re-flash the board.

I copied the SD image directly from my Ormerod and tried that in the Duet 0.6 and it worked nearly perfectly.

The thermistor temps were all out but I guessed that was due to the difference in resistor values between the two boards. Once I'd amended the config file they were ok.

The hotend fan no longer ran though. I put a meter on the board and the pins were showing no voltage. It worked fine yesterday. Is the pin assignment different between the 0.6 and the 0.8.5?

Getting back to the original issue I was having it is obviously something within the software that is causing the problem. More specifically I'm sure it is something to do with the IP addressing.

The config file I pulled off my Ormerod has a static IP that actually bears no resemblance to the IP addressing of anything else on my home network and yet it seems to work. I think it came from when I originally set up my Ormerod many years ago. I can get my Ormerod to connect with the Web Control if I plug the Ethernet cable straight into the back of my PC or plug it into the network via a Powerline adapter.

The 0.6 board would only connect to the Web Control if I plugged the Ethernet cable straight into the PC though, I never managed to get it to connect via the Poweline adapter.

I really don't know enough about IP addresses to begin to fathom this out.

I guess my nest step is to play around with the addressing on a setup that works and then try to apply that to the firmware I'm after using.

If you have any ideas on the hotend fan though I would appreciate it.

Thanks in advance

dc42

The fan control is active low on the Duet 06, active high on the Duet 085. Later firmware versions manage the difference automatically, but older versions needed parameter I1 added to the M106 command on the Duet 085.

Phaedrux

@jonnybrylcreem It's far easier to manage IP addressing through the DHCP server of your router. If you can log into your router you can probably find a way to reserve an IP address for each device on the network. That way the Duet can ask DHCP for an address and it will get the same one every time without worrying about address collisions happening when two devices are trying to use the same IP.

JonnyBrylcreem

Thanks for the info @dc42, that resolved the issue with the fan.

@Phaedrux , I've tried using DHCP and I just can't get it to work for some reason. My printer never appears on the list of devices on the router. If I give it a static IP address that resembles everything else that is connected to the router then I can't get it to work either.

The only way it wants to work is if I give it an IP address that was set up years ago, when I first commissioned my Ormerod, on a different router. Using this old IP address (which I don't think should even work) the printer never appears as a connected device on the router (I can identify everything that appears connected) but it is clearly connected as I can operate the printer remotely via my iPad and upstairs PC. So I'm totally baffled.

I would leave it at that but I'm trying to get both the 0.6 and 0.8.5 board to work and the only way I can currently do that is if I effectively clone the setup, which means I would only be able to use one machine at a time.

I hope this makes (no !?) sense because it doesn't to me.

Thanks for all your help though.

ayudtee

@jonnybrylcreem You have a typo in your 540 command,

M540 PBE:EF:DE:AD:FE:ED should be
M540 PDE:EF:DE:AD:FE:ED instead. DHCP should work once this has been corrected.

JonnyBrylcreem

@ayudtee thanks very much I will give it a go.

JonnyBrylcreem

Ok, so I did manage to get the board to connect to the network using DHCP using old firmware. I had forgotten to add a comment to disable the M554 gateway line.

I should say at this point that I am pretty much blind in one eye and don't see too well with the other one, so I tend to miss little things like that. Sorry

Having re-flashed the board with RepRapFirmware-1.21 however I am pretty much back to square one in that the board will not connect to the network via DHCP, @ayudtee I'm afraid that didn't solve the issue.

I tried cutting and pasting the network commands from the other SD image as well but that didn't solve the issue.

The hotend fan has started running flat out for a split second and then runs at the normal rate for a minute or so before revving up again. The fan led turns off briefly before the fan revs as well, as if the board is resetting.

Any ideas?

Apologies for all these questions, I was hoping this was going to be a quick job!

ayudtee

@jonnybrylcreem I have a Duet 0.8.5 running 1.21 on my Ormerod 2 printer and the 540 command that I use for DHCP is:
M540 P0xBE:0xEF:0xDE:0xAD:0xFE:0xED ; MAC Address

Hopefully this other format for the 540 command like I am using will also work for you.

JonnyBrylcreem

@ayudtee that was the format that I cut and pasted in, it made no difference. I wondered if it was because my router already had that MAC address in memory from my other printer so I tried changing the last "ED" to "00". Still didn't work.

I'm bound to have done something stupid, I just can't figure out what it is though.

Cheers for the help

ayudtee

@jonnybrylcreem Try power-cycling your router, as DHCP was working for the Duet's mac address before you upgraded its firmware.

Phaedrux

Could you repost the networking portion of your config.g as it currently sits?

I was about to suggest modifying the mac address to make it unique, but I see that you've just tried that without success.

Here is what I would expect to work. If you copy and paste this into your config make sure that the gateway address matches your router. 192.168.1.1 is default commonly, but not always.

M540 PCB:E1:AB:70:29:79   ; Randomly generated MAC address
M550 PTESTPRINTERNAME   ; New unique name for the printer, all caps
M551 Preprap .  ; Default password
M552 S1 P0.0.0.0 .  ; Enable networking and use DHCP
M553 P255.255.255.0   ; Set default Netmask
M554 P192.168.1.1  ; Gateway IP address. Should match the IP of your router

If this were me troubleshooting, and that still doesn't work, I would attempt a factory reset on the router (after backing up and documenting the current configuration, and only connecting the Duet to the router and nothing else and seeing if the Duet shows up as a device.

JonnyBrylcreem

I think the first problem that I need to address is that the board keeps resetting itself since I have flashed firmware 1.21 to it.

I previously thought it was just the fan dropping in and out but having tried to connect to Pronterface I can see that the board will initially connect and then after about 30 seconds it seems to disconnect. All the LED's go out on the board, the hotend fan shuts down and then everything powers up again. This process then just keeps cycling.

I get the following message on Pronterface:

I've tried re-flashing the board but I get exactly the same problem.

I don't think the board stays powered up for long enough before resetting to even try to connect to the router.

Any ideas please?

dc42

After the board has reset itself, run M122 and look for the "Last reset reason" in the report. If it's a software reset, also look at the "last software reset" data.

There is a known issue with recent firmware versions on Duet 06/085 that I have been unable to reproduce or track down. It causes resets on some systems when DHCP is used.

You could also try the just-released 1.21.1 firmware.

JonnyBrylcreem

VICTORY IS MINE!

@dc42 @ayudtee @Phaedrux thanks for all your help.

@dc42 I had come to the conclusion it was a comms issue causing the reset as I had traced the fault to only occurring when the Ethernet port was connected to the network.

I've given the board a static IP address and that seems to have cured the problem. I'm afraid I was unable to look at the "last reset reason", the board just didn't want to report back.

I will give the new firmware a go at some point, first of all I want to finish putting the printer together and try to get it to print something!

Thanks again

Jon