Posts made by jay_s_uk

@flopo76 one for @chrishamm to fix with the config tool

@maximyz3d DWC is programmed in VUE.
There are some guides on creating plugins. Never tried it myself though

@maximyz3d RS485 support has been added in 3.6 (still in beta) so you can use that to read/write registers.
Otherwise you've got UART, MQTT or HTTP

@maximyz3d you won't be able to sync them and use them all together.
your only choice is CAN-FD.
What is the maximum cable run length you would be looking at?

@SpeedyDad sounds like a config error.
the "Tool Fan" in DWC is the part cooling fan of the currently active tool and not the hotend cooling fan

@awitc ok. Just wanted to mention that theres a fork of the duet firmware which runs on an STM32F4 (only the STM32F407 and STM32F429) which can have an spi2can module added so it can talk directly over CAN-FD to the duet 3.
Although that probably won't help you with the control of the extruder.

Have you added M575 in your config to enable the UART connector?

@awitc what are you ultimately going to use the STM32F4 based board for? Which specific STM32F4 processor does it run?

@dwuk the out of sync/delay issues with a mainboard in expansion mode has been fixed internally. Don't know if a build has been made available

@dwuk if you're doing any remapping of axes after movement in 3.5.4 that's unusable too.
You'll notice a difference when you come to print something as the movement code is way better in 3.6, especially pressure advance and input shaping

@dwuk mixing 3.5.4 and 3.6b4 based boards, with the amount of changes that have happened between the two, is a really bad idea

@rbjam83 you can't just add a thermistor like that.
If you look at the schematic, you need a connection to VSSA (3.3v) as a reference voltage and then a voltage divider.
It may be easier to add an SPI daughter board for the max31865 and convert your hotend to a PT1000, then you'll have a spare port

@developeralgo222 yes, that's still the case of 1 per axis.
It makes normal difference whether they are at min or max

@rero the next tool should be available in the object model under state.nextTool

@gershb0mb I suppose the only thing that could be a downside with the 6XD is that the Comms time with the drivers will be slightly longer than using internal ones so it could limit the maximum speed. How fast are you able to move the machine now?

@dwuk oh really? I'll try that and see if it works

@rero it would be nice to be able to have tfree.g etc work without the number and just call one set of tool change files, especially if it's a single head machine.
I'm lazy and use a macro to create multiple of the same file.
E.g.

while iterations < 4
        set var.filename = "tpost"^{iterations}^".g"
        echo >{var.filename} "; autogenerated tpost"^iterations^".g file"
        echo >>{var.filename} "M98 P""0:/sys/AFC/tpost.g"" A"^{iterations}

@gershb0mb you have one of two routes to go down.

• Buy a 6XD and use the existing external drivers. Wiring would be simpler as you'd just be modifying the wiring between the existing drivers and the mainboard to suit the 6XD. You also wouldn't have to change any settings on the existing drivers
• Buy a 6HC and replace the existing drivers and use the onboard ones. Cons going against you here is you may need some fairly significant cooling to run the built in drivers at ~5A. You also couldn't go higher than 48v in the future if you chose to.

I would probably go 6XD and stick with the existing drivers.

@darylprice out1, out2 and out3 are whatever the input voltage is

@qurt are you running standalone or in SBC mode? You mention an SBC in your first post

@emi100 you probably have only updated the firmware on the board and not DWC which is why you get messages about incompatibility.
You don't need to restart anything when making changes to homing files etc as they are only read when they are commanded to