I'm looking to upgrade my old Titan-Aeros. I have 4 Duet2 Delta printers.
The Orbiter V3 seems like the latest and greatest... not that there is a lot of info out there yet.
It says it's optimized for Klipper, that's about all I can find.
If I use the V3, can I make full/most use of it with my Duet2? If so how?
The touch screen portion came unglued, and fell off in a way that kinked/cracked the ribbon cable. Everything else is totally fine.
Is there a replacement touch screen I can get? 7"
Goals/TLDR:
I want the best experience, while remaining mainstream and "practical" on the budget. (Corvette vs Ferrari) Components that are well known/supported, "affordable".
I may avoid Unjustified-Proprietary parts.
I try to focus on significant upgrades first. Game-Changers.
My ignorant thoughts:
If going on intuition, because of the quantity vs. quality of information.
-Start with the hotend and sensors, then upgrade the rest based on that.
-Go down the Rapido or Revo path, and try to supplement with universal/cheaper components when practical.
-Get the Accelerometer and Flow sensor.
Current Setup:
-Four Duet2 printers. Delta printers(D300VS).
-E3D Titan Aero(Direct Drive), Copper volcano/nozzles...
(non-CHT, eager to try...clones?).
-FSR Pads for calibration. Reprap firmware.
-Average achievable flow rate: 20mm^3/mms.
-XY speed 70mm/s with 200mm/s travels, before artifacting becomes too ugly.
-Majority is PETG/PLA, 0.8 nozzle, may go up or down a size as needed. (I like to print with fine shell layers with chunky infill,)
?Question Section?:
Hotends and Nozzles:
I think the popular systems are the Revo, Rapido, Mosquito, and Dragon?
Some of which are more propitiatory than others... but there is adapters that can make things work ether way?
Extruders:
The couple that I've heard the most about are the Orbiter, and the Hemera XS.
This may be my last step in upgrades, as it's probably the most costly/time consuming, I'll have to design/print new delta specific parts... but I may have to do that for other add-ons... so... it may be in for a penny in for a pound.
Sensors: (last but not least?)
These are these easiest to understand on paper, but I wonder how significant they are in practice?
The Accelerometer helps counter the effects of speed artifacts. How much does it help? Is it more/less effective on a heavy setup?(my Direct Drive Delta)
Flow sensors/Filament Monitor; Can it adjust flow rate to maintain accuracy?
Better heat probes/temp sensors. I had one that came with a used printer, but it was hyper sensitive/problematic and removed it... but now that I'm wiser, I wonder if having accurate static heat is more important than I once thought, could I get some feedback?
How obsolete are my Delta FSR pads? I've felt like these have been a great calibration system; but if there is room for meaningful improvement? I print on hair-sprayed, textured-clear glass, onto of aluminum.
Any thing else that I should consider upgrading/advancing to get higher quality printing?
Is the duet2 a limiting factor to what meaningful "sensors/add-ons, available?
-any future tech on the horizon to factor around?
Thank you 
for your time in reading this, and for any future recommendations and thoughts!
@droftarts
Thank you for answering this so clearly, I appreciate it ! I'm back running again.
I may have questions in the future, but this will do for the moment.
Cheers!
@droftarts
Hello, thanks for helping; I have a inconstant amount of knowledge about the duet2.
I'm only running a heatbed and hotend, If there are more than 2 heater outputs, then yes. I do not know what VIN is. I use the type of fan that would come with an E3D Titan Aero.
I melted my hotend's heatsync cooling fan-wires against the hotend
This is a used duet2wifi, when I went to inspect the board, the FAN2 pins in usedhad a burnt MOSFET (the dot), but I was sadly surprised to find that FAN1 is also damaged... which I'm assuming happened with the previous owner.
I have a spare [aways on fan) pin... I guess I could use that?... can it be configured to to turn on with temperature? Are there other pins I could use besides that?
PS. what model of MOSFET do I need to replace these? (I know there are a couple options, can you state the most common and or best specifically?)
image url)
I have 4 Deltas with FSR pads for calibration (Ultibots D300VS).
Two of my 4 printers are no longer printing square enough, so one aspect of troubleshooting I'm trying to narrow down is this:
If your print bed is aggressively textured (peaks and valleys maybe around 1mm in difference) but averages out flat, and also prints acceptably flat after calibrating on it.
But could calibrating in such a manner cause the X/Y dimensions to be out of square?
I've been tinkering with this, and yes my network is surely the week point, but I'm not ready to setup the interface upgrade... I have found a work around but I need some help:
I have two wireless access points, 1. A=giving me trouble 2. B= works, but if I cycle the power on the printer it automatically jumps back to "A", the only way I know to get it back on to "B" is to turn A's radio off, then run my m552 script for B, to connect to B... otherwise it just goes back to A. it's super weird, since A and B are both different SSID, Password, and Physical hardware... but the Duet's remember the login to A; I don't know where duet saves login information.
in short: if both A and B wireless points are on, it will do everything it can to connect to A, however once connected to B it will stay on it until it disconnects/cycles.
And both printers/versions of firmware act this way.
How can I get it to just default to the last network it was connected to? or something of that nature?
I've had a pair of these duet2's running most of the year without any major connection issues, but this week they just wont play nice with the web interface. They will "Wifi Module is connected to access point" but can't get into it with a web browser; it might connect for a few mins but then get booted off for indefinite/ever.
I have two firmwares between the two of them, 3.4.1 and 3.1.1, both behaving identically on this note.
I've played with my network things quite a bit, and can't get an improvement.
A family member is wifi gadget obsessed, I don't know if they polluted the pool in the last week by adding yet another "smart bulb" on it, but nothing I've done has changed on the network, they printers just became more and more fragile to stay connected to this point.
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1rc1 (2022-05-03 09:34:00) running on Duet WiFi 1.02 or later
Board ID: 08DAM-9K9K2-NGNSN-6J9D6-3S46N-TPS3J
Used output buffers: 3 of 26 (23 max)
=== RTOS ===
Static ram: 23868
Dynamic ram: 74424 of which 24 recycled
Never used RAM 10572, free system stack 102 words
Tasks: NETWORK(ready,13.5%,200) HEAT(notifyWait,0.1%,321) Move(notifyWait,3.5%,295) MAIN(running,82.8%,421) IDLE(ready,0.2%,30), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:27:19 ago, cause: power up
Last software reset at 2022-11-22 18:55, reason: User, GCodes spinning, available RAM 13644, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x10
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 33.1, current 49.4, max 50.5
Supply voltage: min 23.7, current 23.8, max 24.7, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/66/22, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok, SG min 0
Driver 1: ok, SG min 0
Driver 2: ok, SG min 0
Driver 3: ok, SG min 0
Driver 4: standstill, SG min n/a
Driver 5:
Driver 6:
Driver 7:
Driver 8:
Driver 9:
Driver 10:
Driver 11:
Date/time: 2022-12-01 01:11:53
Cache data hit count 4294967295
Slowest loop: 478.34ms; fastest: 0.16ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 2.2ms, write time 559.7ms, max retries 0
=== Move ===
DMs created 83, segments created 14, maxWait 275333ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 41685, completed 41645, hiccups 5, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state 3
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.3
=== GCodes ===
Segments left: 1
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is doing "G1 X-11.541 Y-2.060 E0.0199" 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
=== Network ===
Slowest loop: 564.27ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 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.26
WiFi MAC address 5c:cf:7f:f8:2b:ed
WiFi Vcc 3.31, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25416
WiFi IP address 192.168.1.191
WiFi signal strength -40dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
(GMT-8) BC Canada, west coast.
I can usually make myself available for any time.
I have autism, specifically in this way I have very hard time absorbing written knowledge, I'm a better visual+auditory learner.
I do fine in some aspects, but these firmware guides might as well be trying to defuse a Korean-time-bomb, my business depends on these machines, hence the extra stress.
I'm still on 1.19.2 and 2.01.
If someone is able to spend some time walking me through the paces, and or even taking over with a remote desktop sort of thing, I would be very grateful. If that means compensating someone for their time, I would be glad to do that.
Thank you for the explanation.
I do believe I found the gremlin that started this, seemed the power wires to the fan's PCB start to fray and looked possible that they were shorting... but I tossed it just in case it was something else.
I sure hope this repair isn't too tricky.
I ordered a few of both the AO3400A and AOSS32334C, last night, thanks.
Do you know which one is "better" ? more robust/reliable?
So... I believe I have a faulty fan that over taxed the FET that it was on the past number of years; I feel silly that I didn't consider it bad to keep using since it still powers on and blows hard... I don't know why it's shorting out these FETs?
So I tested it for a bit on FAN0... then I think I heard a lil pop, and the fan stopped... then I tried a new fan on it... and it's only blowing at 20% or so even set to max. when I looked at the FETs, I could swear that 0 had a dot on it, but not 1 or 2, then 2 had a dot on it after the popping sound... least I'm pretty sure there was a physical change.
SOOO I'm with out of cooler fans it seems... I need to replace these FETs... Can someone tell me where to order new ones?... and also note if this problem could be worse than just loosing those?
ALSO! as a work around is it possible to use a different set of pins to power a cooler fan? I have spare heater and extruder slots free.
@o_lampe said in FAN0 =dead - Need FAN2 to turn on with FAN0? How?:
use M563 P0 D0 H1 F2, if you have defined F2 before
This is what I tried, no luck.
; Fans
m106 P0 H-1
M106 P1 T50 S255 H1
M106 P2 H-1
; Tool definitions
M563 P0 D0 H1 F2 ; Define tool 0, the extruder (D0 = Default slot/plug)
G10 P0 S0 R0 ; Set tool 0 operating and standby temperatures
M92 E414 ; Set extruder steps per mm(last850
My duet2-wifi 's FAN0 no longer seems to work; when testing with my volt meter, it seems as though the read out blips to 19 volts, then holds at 1v , no difference if the FAN0 is toggled on or off.
FAN 1 = heatsink
FAN2 = Spare, and works.
How can I get FAN 2 to turn on when the sliced file tells it to / so that the web interface's slider works with it?
Firmware 1.19.2 (yes... I'm afraid to update).
I've tried "M563 P0 D0 H1 F0:2" Former was M563 P0 D0 H1... no difference.
@dc42 said in Delta: Increase/Override bed radius?:
Change the M665 B parameter (bed radius) to 150 or 151.
Oh! thank you, I'll give that a try asap.
https://reprap.org/wiki/G-code#M665:_Set_delta_configuration
I was reading here that M665 B was the "Safe probing radius" which through me off, I didn't realize it was the Bed Radius.
I have a well calibrated/auto calibrated delta (d300vs+) with a 300mm print bed.
M665 L379.000 R206.671 H445.327 B140.0 X0.171 Y0.186 Z0.000
I want to print up to and or beyond(for prime/purge) the maxim radius of the bed.
As it is after auto calibration, it stops about 10mm from the edge of the bed.
So if printing a box with the corners reach to the edge of the virtual slice bed, they will get cut/rounded off when printing. (I've already tested/adjusted, and this is not a slicing issue).
The arms/effector can physically reach beyond the bed (tho I realize caution when applying speed at those limits).
If I cheat by changing M665 in the config_override.g R to 215, it gets much closer to the edge... but I don't think that is the correct answer).
How can I get the duet to print up to the 300mm diameter of the bed, or even 302mm for purge/prime?
D300VS Delta.
I've attempted to fix by replacing switch and sinch up the wires involved.
The LED on the board is dim/ not fully on/off, making it impossible to home.
I've attempted disconnecting/reconnecting the switch, which sometimes can get it to perform as intended, but can also go back to a dim state at random.
Help? Suggestions?
@phaedrux said in Is it safe to connect/charge a USB Micro Android to the Duet2?:
These work really well too and can be wired into the PSU directly.
I can't do that with a 24v PSU tho... right?