@droftarts I think were back up and running now. I hadn't changed the IP address when creating the new config.g file, Id taken note of what it defaulted at and then tried to connect to that. I changed that and then I was able to connect.
Still having the strange banding issues but thats not for this topic.
Thanks for your help.
@droftarts thanks,
Ive got the firmware re-flashed to 2.05.1 with Bossa
I ran the RepRap firmware configuration tool and generated the system files, as it states I put the Reprap Firmware file in the /sys directory, the web control bundle in the /www directory and the system files into the /sys directory.
I cannot connect to the duet via DWC however (checked IP settings too).
I restored the card back to its backup manually and was then able to connect to the printer via the previous IP address, I was greeted with a new DWC page so it looks like the firmware update has worked.
I have tried as the config tool also suggests uploading the configuration bundle zip file via upload system files in DWC. When I do this, it creates another /sys folder within the directory and puts the new files in there.
However I don't think its reading the config files properly.
I can take manual control of the printer, heat the heaters.
I cannot however select files to print - I can see them and tick their box, but don't know how to print them.
Theres a new option 'load filament' which when I click it returns the error 'failed to load filament'
Ive tried various incarnations of moving the files round and nothing seems to bring the right results.
What have I missed? Apologies if its something blazingly obvious.
Thanks
I've re-read your post again. Yes erasing and re-flashing with Bossa sounds like the way to go. I'll give that a shot.
Thanks @droftarts
So, can I just clarify so I don't end up with a doorstop...
That this is the correct version https://github.com/dc42/RepRapFirmware/releases/tag/2.05
Am I aiming for the Duet2CombinedFirmware.bin binary file which doesn't have the version after it?
And, its a simple case of following the 'usual procedure' as outlined in the updating firmware guide on the dozuki? Grab that binary file, upload and then install? Do I need to update the web control files too? or is this whats included in the combined firmware?
I've a copy of my config file so will copy across the info to the new one.
Thanks
Stuart
dc42 has suggested I head here from the RepRap forums for assistance in upgrading the firmware on my 0.85.
Background, i'm running a kossel mini with duet 0.8.5 onboard, and its been running great for a while with PLA. I've decided to give e3d's Edge a go which requires higher temperatures, i'm getting some strange banding on the prints which from a post on the RepRap forums has pointed in the direction of PID tuning not being configured for the bed.
I've made an attempt to setup PID tuning for the bed, however sending M303 H0 S80 returns an error.
I clearly need to do a firmware upgrade.
I've done a bit of googling and found the guide on how to update the firmware on duet2 but not for this older model.
Currently running:
RepRap Firmware
Version: 1.10+4
Web interface version: HTML:1.11, JS: 1.11
What steps need to be taken in order to update this board, and to which versions are stable to update to?
Thanks
Ive got a kossel mini with a duet running firmware: 1.10+4 (2016-03-30) and a DC42 IR probe.
Recently Ive had a few problems calibrating, the issue is that the Z probe height offset seems to vary.
So far i've:
Heated the bed and extruder to PLA temperatures.
Homed the printer
Brought the nozzle down to the print bed using a piece of paper to determine where Z=0.08mm and set Z to that height
Lifted the nozzle 5mm
Run G30 s-1
Read off the head position as Z=1.09 and updated the relevant section in the configuration file.
Run G32
Then when I bring the nozzle back down to the bed, I can take it all the way to Z=0 and there still be a slight gap between the nozzle and the bed.
Interestingly I noticed when bringing the nozzle down to the bed the IR probe is triggering at Z=1.30
If I repeat the above process again running G30 s-1 now gives me a Z height of 1.27mm.
Has anyone had any experience of this or is there something i'm overlooking?
The level of ambient light isn't changing and the z probe board is firmly attached to the Effector assembly.
Thanks
Stuart