@bearer said in Upgrade from 0.8.5 to Duet 2 Wifi:
I'm fairly new to Duets and RepRap myself, but I can't say I spot any reasons that config shouldn't more or less just work with a newer board. Maybe someone who is more familar with corexy and dual nozzle setups can chime in.
Odds are your existing screen will work with the new Duet 2 as well, the old duet board is configured for a standard PanelDue, which should be compatible. But if you're set on getting the 5i screen then thats a moot point. Otherwise feel free to upload a picture of the screen. Or just have a look at the silkscreeen on the board and tell us what it says.
Thanks for your help. The printer is corexy but only a single extruder (I have a Palette+ for multi-extrusion type stuff... when I can get the printer working that is!)
I've spoken with Fusion3 and they provided me with their firmware for the PanelDue but unfortunately it doesn't work. The PanelDue is v1.1. Unsure if this is the issue, I've also bought a new PanelDue PCB - and will keep the 4.3" LCD.
@dc42 said in Upgrade from 0.8.5 to Duet 2 Wifi:
@en_passant said in Upgrade from 0.8.5 to Duet 2 Wifi:
New member here, and not the most advanced super user!
I have a Fusion3 F400-S which I bought a while back and have had MASSIVE problems with... I've spoken with them today and explained that whilst printing the print simply stops, no warning - just decides it's had enough. I thought maybe something was going wrong with the gcode but they've told me that apparently it's the board and that I have a 0.8.5 board - I knew it was a Duet but not which version.
I was told that apparently there's been issues with this board doing this before. Also that I get a the "heater 1 appears to be overpowered..." warning basically every time the printer is on - they've said this was a legacy issue and not to be concerned about:
"When you reboot your printer with this new firmware you may see a message on the console that says something like “Warning heater 0 appears to be overpowered and may be a fire hazard”. This warning can be ignored – it’s built into the firmware. What it means is that if left at full power for a very long period of time, the print head could exceed its max temperature of 300C. This is necessary for quick heatup times and to have enough reserve heating power to respond to changes in ambient temperature (such as when the blower speeds up)."
I'm looking to change to a Duet 2 Wifi, which I believe I'll need to get a different screen for along with changing the firmware etc.
With the Duet Wifi would I simply change over the board, plug in a new screen (I'm unsure the difference between PanelDue and PanelDue Integrated - assuming I'd need the integrated?) and away I go?
The firmware I have is:
FIRMWARE_NAME: RepRapFirmware for Duet
FIRMWARE_VERSION: FusionWare 1.17e R2c+8
ELECTRONICS: Duet 0.85
Would I need to change this? It was provided to me by Fusion3 and I'm unsure if they've modified it in any way?
Basically, I'm wondering what I need to do to upgrade from the Duet 0.8.5 to the Duet Wifi and the PanelDue Integrated - simply buy them, plug them in and install the firmware?
In the first instance, I suggest you upgrade the firmware on the Duet 085. Firmware 1.24 is the latest, see https://github.com/dc42/RepRapFirmware/releases/tag/2.03. The older firmware versions had two bugs in the third-party files for the network stack, either of which could be responsible for the firmware crashing. These have both been fixed in more recent versions (one of the fixes unfortunately involved disabling MDNS, because the code turned out to be so bad that there was no easy fix).
If you do upgrade to a Duet WiFi, you can use your existing PanelDue with it.
Unfortunately, I didn't see this before I already bought the Duet Wifi. It came a few days ago and I was on a call with Fusion3 attempting to get it updated yesterday.
I didn't get a new PanelDue as was advised I wouldn't need to so I still have the v1.1. When I was speaking with them, going through the firmware update - I did the PanelDue first (and didn't manage to get to the Duet Wifi.) I tried to attach the firmware I updated the screen with but unfortunately it isn't on the allowed list so I've put it on Dropbox here. The firmware they've provided me for the Duet Wifi is here.
I've been informed that in later F400's and their newer model (F410), they moved from the 0.8.5 and use a Duet 2 Ethernet and this is the firmware they use for the later F400's (not sure about F410 but believe probably not because it also has filament monitoring).
When I installed the firmware to the PanelDue and connected it to my Duet Wifi, the screen just went white but didn't bring up the calibration page, as they expected so they advised me that when they've had customers who have had issues with their F400 0.8.5's - they've replaced it with a Duet 2 ethernet but they've also replaced the PanelDue and advised me to do the same, as there may be something that's changed between v1.1 and later versions which isn't behaving with the firmware. Alas, I've bought a PanelDue without screen last night and have had an email saying it's on it's way today.
What I'm hoping to find out is if there are any differences with this firmware that would not work with/ cause issues with my Duet wifi instead of Duet ethernet?
I'm also close to updating the firmware on the PanelDue and Duet Wifi with the most recent Duet3d ones rather than using the Fusion3 - but I believe they've changed the firmware include some forms of safety cutoffs? I was hoping someone could verify this from the firmware I've uploaded and perhaps enlighten as to whether I'm better to simply ignore this firmware and go with the most recent Duet3d one?
Thanks as always,
Thanks for all the information, everyone. I'm of the opinion now that a small amount of preload is desirable, which rules out the Misumi Standard Grade. The HiWin sets are specified as "Z0 - very light preload" with (apparently) 0µm clearance. The Misumi High Grade are listed as "-3 - 0 µm" clearance.
Based on experience posted here, I would think either is fine for typical printers. I actually have been very pleased with the stainless RobotDigg rails & guides I used on my delta. However, my RailCore is worth the extra money
Put a console message M code before/after the move you wish to time. Hook up to USB. Use a terminal program (such as YAT for windows) that timestamps each line to the millisecond.
However... that will really tell you when things pass through the planner. You MIGHT need to put a dwell command in several places, and subtract out that time.
Use a set of microswitches and an Arduino.
The DICE is a piece of art when it comes to packaging. It's a beautiful machine. I'm sure they made many tradeoffs when it comes to serviceability when they designed it. That's your problem now
I'm waiting for the same crowdfunding, and also reused the Maestro for other projects.
@bondus That's good news if you can test RRF3.
I am used to use Eclipse for Java, but I am often confused by the eclipse behaviour. Especially at RRF I am confused by the different setting for the different hardware and the error message that pop up here and there for some .h files not being compilable. I understand why David has it in the code, but my Eclipse tells me about errors, because a grayed file cannot be compiled or found.
I thought about a fork and throw out all those RADDS, Duet 085 and other hardware which is not relevant for my hardware. And I would like to throw out Delta, heatbed calibration code to have the pure logic in the code which I need, and to understand the code. But it's a lot of work, and then I have to synchronize somehow.
@bearer Thanks for the reply.
Yes I am using 'fancy' silicone stuff as I use a lot for my model helicopters.
BTW I did read the Wiki and searched the forum before posting.
It never gave a gauge, just thick!
Moved the extruder and the motor out the printer , on the top.
I had to move also the roll support. It need to stay hight.
Less weight for the head, and less thermal stress.
Now I'm printing some part s for organize the cables close to the head.
All this in prevision of the hot chamber tool.
@deckingman that's a good point, still I would have expected endstops to suffice, but I guess that alone isn't repeatable enough. I must have inadvertently been slicing with different settings before, which would be why I hadn't noticed it.
@veti said in BLV mgn Cube - 3D printer Project:
at a build plate of 500 i would expect that the 2 rails would not be enough to ensure the stability of bed.
you could modify the build and add 2 additional rails and obviously the front panel would not fit anymore.
if you are not comfortable about doing your own mods you could have a look at the voron 2.1, which allows for such build volumes
For bigger bed plate i would recommend adding one more rail (3 z axis setup) and using auto ture leveling. It will be much better then using 4 rails. (Installation of 4 rails is a nightmare)
Thanks once again @Phaedrux.
I honestly thought it was not being applied as it went 0.25 then to 0.20.
Is there a way to show the actual height as opposed to the corrected height, ie 0.25? For me it confirms that I have my settings in Cura correct.
(Damn, I had a 5 minute video, powerpoint presentation and the likes to show how it was not working!! )
I put the motors above the vertical frame profiles, so they don't bother me.
Note that I kept the top front profile, but it could be remove, to have full access to the printer (the frame uses 45x45 profiles I had, so is very rigid).
@3doeste Ah OK. I suspect that dosing tiny amounts of filament might be a bit challenging. Any idea what sort of range the ratio of dye to filament might be? Just looking at some numbers, for a 0.5mm segment length at 0.3mm layer height and 0.5mm layer width, the extruder move length is about 0.025mm which is about 0.00375 mm^3 of plastic. I would imagine that the Dye content would be in the order of parts per million of that?
Download this zip file https://github.com/dc42/RepRapFirmware/releases/download/2.03/Duet2Firmware-2.03.zip
Then upload the whole zip file as is to the Settings page in the DWC. That's all you have to do.
Looks like your connection to Duet3D was lost, please wait while we try to reconnect.