@knuxvomica See the ibom here:https://github.com/Duet3D/Duet3-RotoToolboard/tree/master/v1.0/bom

Is it this one? L10 - CM Choke - Wurth_CM_Choke_744231121
https://www.mouser.co.uk/ProductDetail/Wurth-Elektronik/744231121?qs=PGXP4M47uW7pR%2Fs6aP5qqg%3D%3D

Ian

Hi guys. I would like to ask @T3P3Tony or @dc42 for further instructions.

Chris

@dc42 Sounds promising! ☺️

Well that plain sucks, esp. after putting in the legwork! Hope you find a good substitute sooner rather than later! PD is getting a little but long in the tooth at this point.

@deckingman Hi im not trying to measure the RH at the HT but i need the sensor to survive the higher temperature , when drying filament at high temperatures the humidity sensor is in the same enclosure . also use it to dry desiccant.

@T3P3Tony
the altered firmware from DC42 seems to be working perfectly.
thanks!

I will report back when we run our first tests of printing 510 phosphor bronze from mcmaster.
https://www.mcmaster.com/9668K92/

@VoodooBane I don't know, I haven't seen them online for quite some time. It's pretty simple, however, to update and compile the firmware. To be honest it's been a hot minute since I touched it last.

I was looking around for someone else and either I sold them all or completely lost them in my shop 😄

I am considering a new order of them, if I get enough interest it would push my decision up a notch.

@Italiano85 thanks, in that case we need to replace your board. Please email warranty@duet3d.com and cc your supplier. Include a link to this thread in your email.

Barry, you might want to check this. It's a SAM-C21 evaluation board with 48V/10A BLDC support. (290$ 😞 )

@droftarts

How do I kiss these? I check the forums a couple times a week looking for new product announcements!

Oh well. I’m still waiting on the stepper motors, I don’t suppose those officially came out and I missed it too?

@o_lampe the resistor does not, but the insulation may!

@Merlin246 it just hasn't been implemented in the expansion board code yet. i believe there was talk of adding it to 3.5 IIRC

No idea if the hardware allows for it, but I would very much be in favor of some quality camera module than can interface with the Duet 3s in standalone mode, even if the update rate might be severly limited to like 1fps or so.

It would be nice to see this in a well-integrated package, space efficient so that it can be easily integrated in tight corners of the printer etc, maybe include a thermistor for measuring chamber temp?

Maybe via CAN even?

@TLAS we're not making any commitments at present, but I would hope sometime in Q2 2023.

@arnold_r_clark I just posted about this:

https://forum.duet3d.com/topic/28702/toolboard-v1-3-compatible-with-the-hemera-xs

Never used them, can not reach them with my fingers when mounted on my printer.

@samlogan87
Nice

OK, so far so good! It's been stable for a while now so maybe I can trust it I don't totally trust it. I had to change in a few more places.

@dc42 Well, that look promising 🙂

So now (I really hope it lasts):

Driver 0: pos 80000, 80.0 steps/mm,standstill, SG min 16, read errors 0, write errors 0, ifcnt 70, reads 13761, writes 1, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0 Driver 1: pos 574280, 574.3 steps/mm,standstill, SG min 16, read errors 0, write errors 0, ifcnt 68, reads 13762, writes 1, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0 $ git diff src/Movement/StepperDrivers/TMC22xx.cpp diff --git a/src/Movement/StepperDrivers/TMC22xx.cpp b/src/Movement/StepperDrivers/TMC22xx.cpp index 4b8a1acb..b301af8e 100644 --- a/src/Movement/StepperDrivers/TMC22xx.cpp +++ b/src/Movement/StepperDrivers/TMC22xx.cpp @@ -1441,7 +1441,7 @@ void TmcDriverState::AbortTransfer() noexcept #if TMC22xx_USES_SERCOM DmacManager::DisableChannel(DmacChanTmcTx); DmacManager::DisableChannel(DmacChanTmcRx); - sercom->USART.CTRLB.reg &= ~(SERCOM_USART_CTRLB_RXEN | SERCOM_USART_CTRLB_TXEN); + sercom->USART.CTRLB.reg &= ~(SERCOM_USART_CTRLB_RXEN/* | SERCOM_USART_CTRLB_TXEN*/); //UER while (sercom->USART.SYNCBUSY.bit.CTRLB) { } #else uart->UART_IDR = UART_IDR_ENDRX; // disable end-of-receive interrupt @@ -1497,17 +1497,18 @@ inline void TmcDriverState::StartTransfer() noexcept regnumBeingUpdated = regNum; #if TMC22xx_USES_SERCOM - sercom->USART.CTRLB.reg &= ~(SERCOM_USART_CTRLB_RXEN | SERCOM_USART_CTRLB_TXEN); // disable transmitter and receiver, reset receiver + sercom->USART.CTRLB.reg &= ~(SERCOM_USART_CTRLB_RXEN /*| SERCOM_USART_CTRLB_TXEN*/); // disable /*transmitter <--- UER*/ and receiver, reset receiver while (sercom->USART.SYNCBUSY.bit.CTRLB) { } #else uart->UART_CR = UART_CR_RSTRX | UART_CR_RSTTX; // reset transmitter and receiver #endif const uint8_t regNumber = (regNum < WriteSpecial) ? WriteRegNumbers[regNum] : specialWriteRegisterNumber; - SetupDMASend(regNumber, writeRegisters[regNum]); // set up the DMAC + //SetupDMASend(regNumber, writeRegisters[regNum]); // set up the DMAC <---UER #if TMC22xx_USES_SERCOM dmaFinishedReason = DmaCallbackReason::none; DmacManager::EnableCompletedInterrupt(DmacChanTmcRx); - sercom->USART.CTRLB.reg |= (SERCOM_USART_CTRLB_RXEN | SERCOM_USART_CTRLB_TXEN); // enable transmitter and receiver + sercom->USART.CTRLB.reg |= (SERCOM_USART_CTRLB_RXEN /*| SERCOM_USART_CTRLB_TXEN*/); // enable transmitter and receiver <--- UER + SetupDMASend(regNumber, writeRegisters[regNum]); #else uart->UART_IER = UART_IER_ENDRX; // enable end-of-transfer interrupt uart->UART_CR = UART_CR_RXEN | UART_CR_TXEN; // enable transmitter and receiver @@ -1520,19 +1521,20 @@ inline void TmcDriverState::StartTransfer() noexcept AtomicCriticalSectionLocker lock; #if TMC22xx_USES_SERCOM - sercom->USART.CTRLB.reg &= ~(SERCOM_USART_CTRLB_RXEN | SERCOM_USART_CTRLB_TXEN); // disable transmitter and receiver, reset receiver + sercom->USART.CTRLB.reg &= ~(SERCOM_USART_CTRLB_RXEN/* | SERCOM_USART_CTRLB_TXEN*/); // disable transmitter and receiver, reset receiver while (sercom->USART.SYNCBUSY.bit.CTRLB) { } #else uart->UART_CR = UART_CR_RSTRX | UART_CR_RSTTX; // reset transmitter and receiver #endif const uint8_t readRegNumber = (registerToRead < NumReadRegisters) ? ReadRegNumbers[registerToRead] : specialReadRegisterNumber; - SetupDMARead(readRegNumber); // set up the DMAC + //SetupDMARead(readRegNumber); // set up the DMAC #if TMC22xx_USES_SERCOM dmaFinishedReason = DmaCallbackReason::none; DmacManager::EnableCompletedInterrupt(DmacChanTmcRx); - sercom->USART.CTRLB.reg |= (SERCOM_USART_CTRLB_RXEN | SERCOM_USART_CTRLB_TXEN); // enable transmitter and receiver + sercom->USART.CTRLB.reg |= (SERCOM_USART_CTRLB_RXEN/* | SERCOM_USART_CTRLB_TXEN*/); // enable transmitter and receiver + SetupDMARead(readRegNumber); #else uart->UART_IER = UART_IER_ENDRX; // enable end-of-receive interrupt uart->UART_CR = UART_CR_RXEN | UART_CR_TXEN; // enable transmitter and rec

@gixxerfast maybe it's something simple like needing to add a delay between initialising the UART (so that the TxD output is high) and the first communication with the TMC2209.

@gixxerfast I will change the baud rate to be 115200 on the SammyC21 to match the bootloader.