Large Format Dowell to Duet conversion
-
Hi gents so after a few hours of work today here is my progress. I have the Rasberian Duet image on the Pi and thats working. I'm able to upload config files to the Duet 3 and have just tested my second config file (here are the config and bed files that might be relevant):
The fan on the extruder is spinning albeit with very very low power. I have two fans hooked up in series there but will sort that out using the fan cables from the second extruder that came with the printer that I don't use. Otherwise here are the highlights:
- When I try and move x or y motors it says:
When I try and home it makes noises but nothing happens. Maybe upping the mA power to 4000 will help to make the X & Y Nema 23 motors move.
-
The status light is flashing orange steadily on the main board. I tried searching but can’t work out what it means. What does it mean?
-
ENDSTOPS: How to setup z end stop. It’s a 3D Touch with a little switch wired into it? I can’t turn on the ‘Endstop type > switch’ in the config menu. 3.1 Is ‘low end’ when it’s at the furthest point from the extruder or closest?
3.1 Is ‘low end’ when it’s at the furthest point from the extruder or closest?
-
I have swapped the Thermocouple for a thermistor for the Nozzle thermistor because the thermocouple is not sheilded and runs down a rubber wire to the board alongside all the motor cables etc. I plugged it into ‘Temp 0’ on the expansion board but I only see PT1000 as an option with temp 0 (what is pt1000 please?).
-
How to set up additional z motors.
Where does the Gcode go that has to be entered into the ‘config’ and ‘bed’ file it does not say?
Is this right?
File config.g:
M584 X0 Y1 Z2:3:4:5 & DRIVER 0 on expansion board, what is the code for that (set as E3 in configurator);
four Z motors connected to driver outputs 2, 3, 4 and 5M671 X-15215 Y190:-10:190 S0.5 ;
What is the co-ordinate convention here? I can’t work it out at all. This is the location of the four z motors-
How to set up the 5v Pam as a fan to cool the boards with the Noctua please?
-
Here is a table with where all the wires are if that helps:
- It would be really great to have a video tutorial series that gives an overview of how the Duet ecosystem is designed and a crash course overview course on how to modify config settings with clear diagrams and high quality images ect. I'd be happy to help. Please direct me if there is an idiot's guide somewhere please. Many thanks
Charles
-
p.s: I tried it with 4000mA per nema 23 and now when I press ‘home’ x it clicks and clicks and cracks like something is being pushed and about to snap. I Try to press move x in the other direction and that doesnt work because of the same above fault, no home
-
I think the firmware on some of your boards is out of sync. Can you send send M122 and M122 B1 from the command console and report the results? The firmware should be 3.3 all around. If not, updating them all will be the first step.
-
@phaedrux thanks I’ll try
-
I'm guessing that means B1 is not speaking the same language (firmware) so will try to follow the firmware update instructions
-
How do I find the address of the expansion board please?
'If the expansion board is already communicating with the main board, send M997 B# where # is the address of the expansion board. The expansion board will commence a firmware update and the DIAG LED will go out for a while. When the update is complete, it will flash and re-sync with the main board.'
-
![0_1632675855516_IMG_3310.jpg](Uploading 100%) @phaedrux
I added the 'Duet3Firmware-EXP3HC.bin' firmware file to the /sys folder (it would be good to have a link to where these files on gitub are on the Getting started with duet page) by opening the zipped config file from the Duet firmware config, then copying the above file into the /sys folder, then zipping it again. When I update the system files on DWC it uploads all the files then gets stuck on the 'please wait while the updates are being installed' loading graphic.
Could this be because now there are two firmware files in the /sys folder? One for the mainboard and now another for the expansion board? I've left it updating for 20 mins which seems way too long and it doesn't come off this screen.
Please advise and please explain every step very clearly explaining how you do something step by step. Often so much knowledge is assumed that it's not clear how to do what you say to do
-
-
P.S What on God's sweet Earth does this mean?
A diagram maybe?) I have the correct cable specified
'RJ11 twisted pair cables to connect the expansion board(s). When connecting a version 0.5 Duet 3 main board to an expansion board, the wires must be crossed. When connecting a version 0.6 or later Duet 3 main board to an expansion board, or connecting two expansion boards together, the cable wiring must be straight-through. Only a single twisted pair is required, connected to pins 3 and 4 (the middle 2 pins) of the connector. Pins 2 and 6 on the version 0.6 Duet 3 main board are the connections for the secondary CAN bus, but the firmware does not use this yet.
2-core red/black cable to daisy chain power to the expansion board(s)' -
P.P.S: Why isn't the expansionboard firmware added by the firmware config tool?
I turned it all off after 30 mins of updating and nothing happening. Now I can't get the Pi to connect to the Duet 3 it just gets stuck on that loading screen to connect endlessly.
I'm going to re-install a clean firmware config on an SSD straight to the Duet 3 and then reinstal the Duet Raspian image on the Pi and start again.
Please provide clear instructions on how to get the expansion board firmware into the /sys folder because uncompressing, copy pasting and then recompressing does not work! Thanks
Charles
-
Now the Pi does not connect to the Duet 3!!!
I just tried to boot the Duet 3 in stand alone mode. I added a config file to a clean wipe of the SD provided and it just turns on and has this dim orange light on where the bright orange light used to be flashing. The expansion board now has an orange light on it too where previously it only had a blue light.
I thought this configurator tool would provide the firmware for the mainboard and the expansion board as is indicated by the process of configuring the firmware thusly. This is really not an intuitive or complete set of instructions. I feel abit conned by the lack of instructions or ability to get support on a phone etc
-
@charles-fraser shall we roll back and get started with just the main board and then move on to the expansion board afterwards?
Is your preference for SBC rather than standalone?
Do you know what firmware version is installed on the duet 3? If you are unsure, boot the board just off USB power and use YAT to get an output of M115 -
@jay_s_uk Hi there. Who is this sorry?
I am trying to connect to just the mainboard and nothing. I am trying in standalone mode, but I can't find the instructions for how to connect to the board through the local host IT IS NOT PROVIDED IN THE INSTRUCTIONS like so many other things.
Please, whoever you are, please help me get this thing working with a set of instructions that describe each step that needs to be taken. May thanks
-
@charles-fraser I don't work for duet3d or anything, just an end user.
You can follow these instructions
They will get you started in standalone mode.
But as I say, you don't actually need a config (or even an SD card) on the board to check what firmware you have installed.
It's pretty crucial that for SBC mode that the firmware and DSF are the same version.
But if we start with the basics, check the firmware version of the board and we can go from there. -
@jay_s_uk thanks! What's the DSF?
-
@charles-fraser DSF = DuetSoftwareFrame - i.e. the software running on the Pi
-
@jay_s_uk the link you provided does not work
-
@charles-fraser updated it. Didn't see the ) in the address and screwed it up
-
@jay_s_uk thanks I am trying to find the board using serial tools on my macbookpro m1 - it doesnt see the board which is now powered by that mini usb connector through the usb dongle (Macbook Pros only have usb c ports so need a dongle)
-
@charles-fraser hmm, i don't use a mac so I can't really help you with that one.
Are you using the USB cable that came with the board?