Duet web control is at version 3.4.6
RR firmware is at version 3.4.6
Thank you so much for your patience and assistance throughout this adventure.
I added the combined IAP file, then re-installed the 3.3.0 combined.zip file for 3.3.
That installed perfectly, then I installed the 3.4.6 combined zip and it just worked.
I have a dual extrusion machine that I am trying to create a good tool change sequence for and could use some guidance. I'm using a combination of simplify3d's tool change retraction values and duet's tool change macros. What I have so far is pretty good but there's some room for improvement, specifically what happens at the end of the tool change. I use a wiper into a trashcan so my process is like this. abbreviated to save time, and I'm not at my machine to copy/paste the actual code ATM;
End of print segment, retraction. (E-5.000 F6000)
S3D calls a tool change in process;
Duet runs Tfree;
Go to position behind wiper (out side of printable volume);
large retraction to get filament out of hotzone (E-10.000 F6000);
set corresponding idle/active temperature;
Duet runs Tpre;
nothing here
Duet runs Tpost;
Extrude material to prime active tool, (E20.0000 F2000);
Retract filament to prevent ooze (E-5.000 F6000);
S3D takes it back to position and moves over wiper in the process
That last line is where I'm having troubles. S3D has a rudimentary canned cycle for tool changes as a "tool change retract distance." Here I can also state an "extra restart distance" that is any additional (positive or negative amount) it will do when calling up a new tool. I have this value set as a -5.0 so that it "un-does" my retraction pre-wipe. This is also where my problem is coming from.
The behavior I'm looking for at the end of the tool change is to retract filament, wipe across the wiper and move back to the part, THEN do the negative retraction to start printing again. What is happening now, is that S3D's putting that extra restart distance from a tool change in the same line as the movement so what I end up getting is:
Extrude behind wiper to purge/prime nozzle (duet value);
retract to prevent ooze (duet value);
move back to part to continue printing, while extruding and creating a nice ooze-stringer line connecting to wiper to the part;
I'd like to know if there's a way to split that last line into 2 moves. I want it to move back to the print in one move, then do the negative retract distance to get the filament where it should be in the nozzle.
Anyone else have luck running a dual extrusion machine with a wiper-trashcan tool change process?
The parts off the machine are great so far and having PLA-PVA models is such a game changer. I took just about all my inspiration from my machine from watching a stratysus fortus 250mc for probably hours on end.
Duet web control is at version 3.4.6
RR firmware is at version 3.4.6
Thank you so much for your patience and assistance throughout this adventure.
I added the combined IAP file, then re-installed the 3.3.0 combined.zip file for 3.3.
That installed perfectly, then I installed the 3.4.6 combined zip and it just worked.
@Phaedrux Finally getting back around to this. I actually had some prints to do and other house projects to wrap up.
Looks like I'm running duet web control 3.3.0 and RR firmware at version 3.1.1
Aren't those 2 versions supposed to match?
Should I try and install version 3.3 again?
@Phaedrux How do I check the DWC version?
I quick google search only brings up checking the firmware version, not the DWC version.
These are the only files in the 0/firmware folder:
Followed your instructions, and started with 3.3, downloaded the *-3.3.zip file, and did not extract it. I followed the "Usual procedure" on the updating firmware documentation, DWC prompted me if I wanted to install the new firmware, I clicked "yes."
I got this error:
M997 S0:1
Error: M997: In-application programming binary "Duet2CombinedIAP.bin" not found
I don't know if this is worth noting, but now my system directory is full of firmware files.
I thought the documentation said that the firmware files are supposed to go into a new file 0/firmware.
@droftarts said in Ajax communication error: connection terminated:
Just redo the heater tuning
That's the only thing? Config.g and Homex/y/z and tool change files are unchanged?
will any config changes/pid tuning that I do on 3.1 need to be re-done after those updates?
@droftarts This morning I could not connect to the DWC. This morning I followed this video. Things were behaving a bit wonky and the file structure didn't match what was in the documentation so I figured I should start fresh. I followed the documentation for a new SD card and reformatted the card, and followed the above guide for flashing firmware. I tried substituting version 3.5.4 but I got a BOSSA error (I of course didn't write it down) so I figured I would just follow the guide explicitly.
And success! (?)
Looks like I'm successfully on version 3.1.1. I've copied my M122 below.
Can you confirm that the software versions are in order? I have:
Duet web control 3.5.0-rc.3
duet wifi server as 1.26
RR firmware for duet 2 wifi as 3.1.1
If that is correct, my next step is to install firmware version 3.5.4 through the DWC.
Edit:
Upon correcting my config file ( had some end stops set wrong) I get an error message about incompatible software:
Incompatible software versions
The installed software versions do not match. Please operate your setup only at equal versions to avoid potential incompatibilities and unexpected errors.
Please check out the docs on how to upgrade your Duet software components.
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4S4-6J1DD-3S46T-93T7X
Used output buffers: 3 of 24 (21 max)
=== RTOS ===
Static ram: 27980
Dynamic ram: 94132 of which 44 recycled
Exception stack ram used: 276
Never used ram: 8640
Tasks: NETWORK(ready,384) HEAT(blocked,1224) MAIN(running,1892) IDLE(ready,80)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:09:54 ago, cause: reset button or watchdog
Last software reset at 2024-03-01 21:07, reason: User, spinning module GCodes, available RAM 7744 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task ����
Error status: 0
MCU temperature: min 32.2, current 33.6, max 34.1
Supply voltage: min 0.4, current 0.5, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 2024-03-02 07:52:23
Cache data hit count 1042385207
Slowest loop: 28.30ms; fastest: 0.09ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.8ms, write time 10.8ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 201.56ms; fastest: 0.07ms
Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
@droftarts
I got up to firmware version 3.3, WIFI server version 1.26, and web interface version 1.22.3
Now I'm getting an Error:
M997: File 0:/firmware/DuetWiFiServer.bin not found
Tried a few older versions of that file name but all give that error.
Not sure where to go from here.
@droftarts I'm finally making progess on this, I had to go back and start at 1.2, then step forward one release at a time looking at the change notes to see when the big changes were.
I've had to go
1.19(start) > 1.2 > 1.21 > 2.0 > 2.1 > 2.05 > 3.0
I tried going to 2.05 first but it wouldn't take. I think in 1.2 and 1.21 had wifi server updates that conflicted with the files in 2.05.
Keep on chugging I guess.
@Phaedrux ill give earlier versions a try.
If I go with bossa, do I still need to install firmwares sequentially, or can I go straight to 3.4?