@AndrewG The config.g you have seems to be quite an old one, and that bed.g wouldn't work with it. I have no idea how that would suddenly revert, but I would try and download the correct variant of the config files to use for your printer
https://github.com/Modix3D/Modix-V3-configuration-and-Macro-files/releases/tag/v3.4.5.c
edit: It might also be worth updating your firmware, those files are made for RRF3.4.5
@Surgikill Good catch, I had overlooked the I1 parameter, though that shouldn't give any problems; the parameter is ignored. The rest of the deployprobe.g and retractprobe.g are correct though, and that should not give an error.
@Surgikill That's quite interesting, I've been working hard to re-write the entire code of the printers, and I am pretty sure I caught all of the depreciated code. But if you point me to anything that was missed, I would love to fix it.
@dc42 Thanks for that.
Good to know that the choice selection for the M291 T0 S4 does not need to be indented, that makes a large difference and with that I should be able to get everything in a single file
@dc42 The problem is not in the variable name, I tested it and it did not work with the following script:
M30 "0:/sys/test/config_globals.g"
M28 "0:/sys/test/config_globals.g"
M29
M291 T0 S4 R"Welcome" P"Welcome to your Printer. Please select the version of printer you have" K{"V1","V2"}
if input = 0
M291 S3 R"Version V1" P"According to this, you have a V1 printer. Press OK to confirm, or cancel to re-start"
echo >"0:/sys/test/config_globals.g" "if !exists(global.config_version)"
echo >>"0:/sys/test/config_globals.g" " global version = 1"
global version = 1
if input = 1
M291 S3 R"Version V2" P"According to this, you have a V2 printer. Press OK to confirm, or cancel to re-start"
echo >"0:/sys/test/config_globals.g" "if !exists(global.config_version)"
echo >>"0:/sys/test/config_globals.g" " global version = 2"
global version = 2
if global.version = 1
M291 T0 S4 R"V2 to V3" P"Do you have a A model or a B model" K{"A model","B model"}
if input = 0
echo >>"0:/sys/test/config_globals.g" " global printer_model = 1"
global printer_model = 1
if input = 1
echo >>"0:/sys/test/config_globals.g" " global printer_model = 2"
global printer_model = 2
elif global.version = 2
M291 T0 S4 R"V2 to V3" P"Do you have a C model or a D model" K{"C model","D model"}
if input = 0
echo >>"0:/sys/test/config_globals.g" " global printer_model = 1"
global printer_model = 1
if input = 1
echo >>"0:/sys/test/config_globals.g" " global printer_model = 2"
global printer_model = 2
That outputs (when choosing V1 and model A)
if !exists(global.config_version)
global version = 1
However this combination of scripts does work:
M30 "0:/sys/test/config_globals.g"
M28 "0:/sys/test/config_globals.g"
M29
M291 T0 S4 R"Welcome" P"Welcome to your Printer. Please select the version of printer you have" K{"V1","V2"}
if input = 0
M291 S3 R"Version V1" P"According to this, you have a V1 printer. Press OK to confirm, or cancel to re-start"
echo >"0:/sys/test/config_globals.g" "if !exists(global.config_version)"
echo >>"0:/sys/test/config_globals.g" " global version = 1"
;global version = 1
if input = 1
M291 S3 R"Version V2" P"According to this, you have a V2 printer. Press OK to confirm, or cancel to re-start"
echo >"0:/sys/test/config_globals.g" "if !exists(global.config_version)"
echo >>"0:/sys/test/config_globals.g" " global version = 2"
;global version = 2
if global.version = 1
M98 P"0:/sys/test/version1.g"
elif global.generation = 2
M98 P"0:/sys/test/version2.g"
M291 T0 S4 R"V2 to V3" P"Do you have a A model or a B model" K{"A model","B model"}
if input = 0
echo >>"0:/sys/test/config_globals.g" " global printer_model = 1"
global printer_model = 1
if input = 1
echo >>"0:/sys/test/config_globals.g" " global printer_model = 2"
global printer_model = 2
M291 T0 S4 R"V2 to V3" P"Do you have a C model or a D model" K{"C model","D model"}
if input = 0
echo >>"0:/sys/test/config_globals.g" " global printer_model = 1"
global printer_model = 1
if input = 1
echo >>"0:/sys/test/config_globals.g" " global printer_model = 2"
global printer_model = 2
That outputs (when choosing V1 and model A)
if !exists(global.config_version)
global version = 1
global printer_model = 1
I don't see a good reason why the script with everything contained in one file would not work, but that same script just split out over three files does work as it should
@dc42 a leftover from trying to diagnose the problems, I re-wrote the macro to be significantly simpler from the one I was working on, but the problems remained.
When removed it still doesn't work
Firmware: 3.5.0-beta.4
Duet web control: 3.5.0-beta.4
I am working on a script to write several global variables to a file, per a series of messages sent to a user, so the user can get the right set of variables for their printer after executing the script.
The first part of the code (line 1 through 15) work well, and in the resulting config_globals.g, the first parameters (version 1 or version 2) are set correctly
However the second set of parameters (printer model 1 or 2) are not set at all, it seems as if nestling the echo commands that deep is causing problems.
M30 "0:/sys/test/config_globals.g"
M28 "0:/sys/test/config_globals.g"
M29
M291 T0 S4 R"Welcome" P"Welcome to your Printer. Please select the version of printer you have" K{"V1","V2"}
if input = 0
M291 S3 R"Version V1" P"According to this, you have a V1 printer. Press OK to confirm, or cancel to re-start"
echo >"0:/sys/test/config_globals.g" "if !exists(global.config_version)"
echo >>"0:/sys/test/config_globals.g" " global version = 1"
global version = 1
if input = 1
M291 S3 R"Version V2" P"According to this, you have a V2 printer. Press OK to confirm, or cancel to re-start"
echo >"0:/sys/test/config_globals.g" "if !exists(global.config_version)"
echo >>"0:/sys/test/config_globals.g" " global version = 2"
global version = 2
if global.version = 1
M291 T0 S4 R"V2 to V3" P"Do you have a A model or a B model" K{"A model","B model"}
if input = 0
echo >>"0:/sys/test/config_globals.g" " global printer-model = 1"
global printer-model = 1
if input = 1
echo >>"0:/sys/test/config_globals.g" " global printer-model = 2"
global printer-model = 2
elif global.version = 2
M291 T0 S4 R"V2 to V3" P"Do you have a C model or a D model" K{"C model","D model"}
if input = 0
echo >>"0:/sys/test/config_globals.g" " global printer-model = 1"
global printer-model = 1
if input = 1
echo >>"0:/sys/test/config_globals.g" " global printer-model = 2"
global printer-model = 2
The output of this file, selecting first version 1 and then printer model 1 is this:
if !exists(global.config_version)
global version = 1
However the expected and desired code is:
if !exists(global.config_version)
global version = 1
global printer-model = 1
Executing the echo commands separately does work, so I am not sure why the commands are not working when used in this fashion.
As another test, I also created two files named version1.g and version2.g, that contained the sub-scripts. In that case, the echo commands correctly wrote the global parameters to the config_globals.g
if global.version = 1
M98 P"0:/sys/test/version1.g"
elif global.version = 2
M98 P"0:/sys/test/version2.g"
version1.g example:
M291 T0 S4 R"V2 to V3" P"Do you have a A model or a B model" K{"A model","B model"}
if input = 0
echo >>"0:/sys/test/config_globals.g" " global printer-model = 1"
;global printer-model = 1
if input = 1
echo big120x
echo >>"0:/sys/test/config_globals.g" " global printer-model = 2"
;global printer-model = 2
@droftarts These are official Duet boards, wiring connections are all good. Using a long ribbon cable, have not tested it out using the 4 pin cable
With the 3.4.1 firmware there are no problems at all
Testing out Paneldue firmware 3.5.0-rc6 (paneldue 7i) in combination with RepRapFirmware 3.5.0-beta.4 (on a Duet 2 WiFi) is giving a weird issue, in that after a certain amount of time, the paneldue stops responding to any kind of inputs on the LCD. I can still see updates coming from the display like temperature changes and homing status, but touching the screen does nothing.
Unplugging and re-plugging in the cable makes it work again temporarily, but after a bit of time (around a minute or so), it stops working again.
It doesn't seem to be linked to the screensaver, I have the screensaver at 120 seconds, and it stops working before the screensaver kicks in
Rolling back to 3.4.1 on the paneldue seems to fix the problem
It's not possible to set a different idle factor for different axises (axis?)
https://docs.duet3d.com/User_manual/Reference/Gcodes#m906-set-motor-currents
From the notes section:
The I parameter is the percentage of normal that the motor currents should be reduced to when the printer becomes idle but the motors have not been switched off. The default value is 30% and will always be at least 100mA - starting from RRF 2.02 setting it to 0 will disable the steppers after timeout like M18|M84 do and if an axis is related to the motor, throw out the "homing" of it, since it is likely that the position cannot be precisely determined anymore. Note that the idle current is applied globally for all motors and cannot be set per axis.
https://docs.duet3d.com/en/User_manual/RepRapFirmware/CAN_limitations
The link to "RepRapFirmware configuration limits" Is a broken link, and doesn't go anywhere
It can happen if one of the pins is badly crimped, or one of the wires is getting loose a little bit.
If you look up, You can see on the red wire of the 3 pin connector above, as well as the yellow wire of the 4 pin connector above that (it looks like that one might also be damaged?), that the metal part is not seated fully into the connector housing.
When that is the case, there is not a full connection to the pin on the motherboard, and that in turn can cause arcing, which over time will cause damage like you're having.
I would strongly advise you to re-crimp the wires there, those are not good crimps.
It's definitely normal that with a volcano length heater block and nozzles, you will tend to have a lot more oozing. Key things to do there are calibrate the printing temperature (you can generally print with a lower temp than with a V6 style heater block)
First thing to look at would be the temperature. I had a friend that noticed they needed to print around 10-20c cooler on their artillery than on a similar hotend. I suspect that on his machine, the temperature is not quite accurate, where it's reporting the temperature as lower than what it should be.
Based on those two, I would say that focusing on the temperature would be a good idea there.
I've spotted an interesting behavior where it seems like the zstop port is reporting about 10x times the pulses compared to other ports. I did not manage to find documentation about this, or was able to change the result
I've tested it out by swapping out the primary and secondary sensors, and the readings are consistent.
Swapping the secondary to a different port (ie the e0stop, ystop, or any other port) seems to work, it's only the zstop port that's giving weird readings
M591 D0 P7 C"e1stop" S1 L3.32 E10 R50:150 ; Primary hotend pulse type detector
M591 D1 P7 C"zstop" S0 L0.235 E5 R10:3000 ;Secondary hotend pulse type detector
Any clue why this is happening? is it a hardware related problem?
M122:
m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DLM-996RU-N8PS4-6J9D0-3S86R-KAU3N
Used output buffers: 3 of 26 (23 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 77464 of which 12 recycled
Never used RAM 7912, free system stack 172 words
Tasks: NETWORK(notifyWait,13.8%,237) HEAT(notifyWait,0.0%,329) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,86.1%,438) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:42:37 ago, cause: power up
Last software reset at 2023-05-12 16:57, reason: User, GCodes spinning, available RAM 7532, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 17.4, current 25.5, max 25.8
Supply voltage: min 24.1, current 24.2, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/15, heap memory allocated/used/recyclable 2048/228/8, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min n/a
Driver 6: standstill, SG min n/a
Driver 7: standstill, SG min n/a
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min n/a
Driver 10:
Driver 11:
Date/time: 2023-05-15 12:34:01
Cache data hit count 4294967295
Slowest loop: 17.74ms; fastest: 0.19ms
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 3.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0 sensor: no data received
Extruder 1 sensor: no data received
=== DueX ===
Read count 1, 0.02 reads/min
=== Network ===
Slowest loop: 16.32ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.27
WiFi MAC address ec:fa:bc:5b:3c:a9
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 22672
WiFi IP address 192.168.178.57
WiFi signal strength -61dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
Something that would be nice to get added for 3.5.0 would be addressing the info status messages during things such as G32 or G29 commands.
I just tested it out with 3.5.0-rc4 but the messages are still there.
https://github.com/Duet3D/PanelDueFirmware/issues/279
Do you have a direct drive setup? If so, you should look at very low PA settings, we're talking between 0.015 and up, up to like 0.3 at most.
I'm running 0.03 for example for a 0.4mm nozzle
@T3P3Tony Thanks, I had assumed so but was a good one to check. Will look at the slicer side for getting things working there.
What I do wonder is if it would be possible for the nozzle to do a diagonal move (shown in purple), it always seems to get back to the previous part's Z position before starting no matter what I do. It always does the up/down motion in orange or green
I tried using the following end bit in the tpost0.g and tpost1.g, but it would lower back to the Z position no matter what, even though there isn't anything in the tool changing scripts that would indicate that the Z motion should happen.
elif job.file.fileName != null ; When printing
G90 ; absolute positioning
if {(move.axes[2].machinePosition) < (move.axes[2].max - 4)} ; if there is enough space
G1 Z{(move.axes[2].machinePosition)+3} ; move up 3mm
else
G4 P1 ; wait 1ms
G4 P0 ; wait for moves to complete
Firmware version: RRF3.4.5
I'm trying to understand proper IDEX behavior with getting everything setup with the tool changing files, and one of the things I'm trying to accomplish is having a proper Z-hop movement added to the tool changing scripts. However I'm running into an interesting issue which I suspect cannot be fixed configuration side wise, and would need to be done slicer side
The idea is to have a Z-hop movement in the tool changing script, where the tool would move up, then away from the print, and on selecting the new tool it would move back down (the lines shown in the graphic below with the black lines). However
with the below tool changing scripts, it moves down, then to the next object (so the green pathway)
I was able to make a script that first moves back to the XYZ coordinates of the previous selected tool, and then go to the new XYZ coordinates, but sadly that's also not always an ideal solution (orange pathway). The code for this is in the last bit of the commented out tpost0.g and tpost1.g (so the G1 R2 Z3 X0 Y0 followed by G1 R2 Z0. I have also tried it without the G1 R2 Z0, but in that case it behaves the same as with just the G1 R2 Z3 X0 Y0)
If anyone has any things to try out, I would love to hear them, otherwise it is most likely a slicer side solution that I'll have to dig in more
Here are the tool changing scripts:
Tfree0.g
; tfree0.g
; called when tool 0 is freed
;
if job.file.fileName = null ; Check if printing a file
G4 P1 ; If you're not printing, don't extrude
else
if heat.heaters[0].current < 160 ; check for temperature
G4 P1 ; dont retract if heaters aren't at temperature yet
else
M83 ; relative extruder moves
G1 E-5 F1200 ; retract 5mm
M106 S0 ; disable fan
G91 ; relative moves
if {(move.axes[2].machinePosition) < (move.axes[2].max - 5)} ; check if there is >5mm space to raise head
G1 Z+4.5 F3600 ; move Z up by 4.5mm
elif {(move.axes[2].machinePosition) < (move.axes[2].max - 2)} ; if there is >2mm but <5mm
G1 Z+0.5 F3000 ; raise by 1.5mm
else ; if there isn't enough space, don't lift.
G4 P20 ; wait 20ms
G90 ; absolute XYZ moves
if job.file.fileName = null ; Check if printing a file
G4 P1 ; If you're not printing, don't extrude
else
if heat.heaters[0].current < 160 ; check for temperature
G4 P1 ; dont retract if heaters aren't enabled yet
else
G1 E-5 F3600 ; retract 5mm
G91 ; relative positioning
G1 H1 Y{(move.axes[1].max+5)*-1} F6000 ; home Y axis
G1 H2 Y2 F3000 ; go back a few mm
G1 H1 Y{(move.axes[1].max+5)*-1} F600 ; move slowly to Y axis endstop once more (second pass)
G4 P0 ; wait for movements to complete
G90
tfree1.g
; tfree1.g
; called when tool 1 is freed
;
if job.file.fileName = null ; Check if printing a file
G4 P1 ; If you're not printing, don't extrude
else
if heat.heaters[0].current < 160 ; check for temperature
G4 P1 ; dont retract if heaters aren't at temperature yet
else
M83 ; relative extruder moves
G1 E-5 F1200 ; retract 5mm
M106 S0 ; disable fan
G91 ; relative moves
if {(move.axes[2].machinePosition) < (move.axes[2].max - 5)} ; check if there is >5mm space to raise head
G1 Z+4.5 F3600 ; move Z up by 4.5mm
elif {(move.axes[2].machinePosition) < (move.axes[2].max - 2)} ; if there is >2mm but <5mm
G1 Z+0.5 F3000 ; raise by 1.5mm
else ; if there isn't enough space, don't lift.
G4 P20 ; wait 20ms
G90 ; absolute XYZ moves
if job.file.fileName = null ; Check if printing a file
G4 P1 ; If you're not printing, don't extrude
else
if heat.heaters[0].current < 160 ; check for temperature
G4 P1 ; dont retract if heaters aren't enabled yet
else
G1 E-5 F3600 ; retract 5mm
;G1 U{(move.axes[3].max-1)} F6000 ; back off 1mm
G91 ; relative positioning
G1 H1 U{(move.axes[3].max+100)} F6000 ; home U axis
G1 H2 U-2 F3000 ; go back a few mm
G1 H1 U10 F600 ; move slowly to Y axis endstop once more (second pass)
G90
G4 P0 ; wait for movements to complete
tpost0.g
; tpost0.g
; called after tool 0 has been selected
;
; Wait for set temperatures to be reached
if job.file.fileName = null ; if not printing
G4 P1 ; don't extrude
elif job.file.fileName != null ; When printing
if heat.heaters[0].current > 180 ; and the nozzle is heated to printing temperatures
M116 P0 S5 ; wait till printing temperature has been reached within 5c
G4 P0 ; wait
M83 ; relative extrusion
G1 E15 F500 ; extrude 5mm
G4 P0 ; wait
M106 R2 ; restore fan speed
G1 E1 F500 ; extrude 1mm
else
G4 P1
G4 P0
if job.file.fileName = null ; if not printing
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed || !move.axes[3].homed ; if axes aren't homed
G28 ; home all axes
else
G4 P1 ; wait 1ms
;elif job.file.fileName != null ; When printing
; G4 P1 ; wait 1ms
; G1 R2 Z3 X0 Y0 F6000 ; go back to 3mm above last position
; G4 P0 ; wait
; G1 R2 Z0 ; go back to the Z height of the last print
tpost1.g
; tpost1.g
; called after tool 1 has been selected
;
; Wait for set temperatures to be reached
if job.file.fileName = null ; if not printing
G4 P1 ; don't extrude
elif job.file.fileName != null ; When printing
if heat.heaters[1].current > 180 ; and the nozzle is heated to printing temperatures
M116 P0 S5 ; wait till printing temperature has been reached within 5c
G4 P0 ; wait
M83 ; relative extrusion
G1 E15 F500 ; extrude 5mm
G4 P0 ; wait
M106 R2 ; restore fan speed
G1 E1 F500 ; extrude 1mm
else
G4 P1 ; wait 1ms
G4 P0 ; wait
if job.file.fileName = null ; if not printing
if !move.axes[0].homed || !move.axes[1].homed || !move.axes[2].homed || !move.axes[3].homed ; if axes aren't homed
G28 ; home all axes
else
G4 P1
;elif job.file.fileName != null ; When printing
; G4 P1 ; wait 1ms
; G1 R2 Z3 X0 Y0 F6000 ; go back to 3mm above last position
; G4 P0 ; wait
; G1 R2 Z0 ; go back to the Z height of the last print
When uploading a filament configs zip with the wrong files, the error message states "fiels" instead of "files"
Version: Duet Web Control 3.4.5
@T3P3Tony Using M226 within the filament-runout.g had a weird behavior, the printhead would remain standing still on the bed, not moving on to execute the pause.g at all.
The normal M25 behaviour is much preferred over this, as the printhead should be moved away from the print as quickly as possible in a runout event, to prevent material from oozing out on the print and causing possible issues
I did notice some other small mistakes within the filament-runout.g (using if instead of elif on some parts), but those aren't the cause of the problem, just some oddities that I've fixed on my end now