@exerqtor

https://forum.duet3d.com/topic/26170/neopixel-support-on-1lc?_=1648139969023 might give hope 🙂

@dc42 Perfect! Thank you so much!

@dc42
Thanks for the answer.
The problem is solved, I just had a loose pin in the connector.

Stefan

@phaedrux
Thank you for your support I could solve the problem.
I just used the comand M587 as it worked with my old DUET2wifi Firmware 2.. with intial ssid and network key with slash as seperator.
With the new Firmware (updated now no to 3.4.0) I have to use the user assigned network name and key without seperators.
Instead of
M587 S"FRITZ!Box 7530 DL" P"1234/1234/1234/1234"
M587 S"StefanHeim" P"1234123412341234"

Regards,
Stefan

@jay_s_uk said in Toolboard V1.2 question:

@tecno a docking switch for when used with a toolchanger

OK, got it 😉

@zapta Thanks I have now change them all, Blue on Red vice versa. And it seems to do the trick.
I'm using:
G91
G1 H2 Y10 F3000
G1 H2 X10 F3000
G1 H2 Z200 F3000
And it works.

But know I have problems with Homing.

Anyway thanks

I have to start a new tread, for the Coding, but before I do that, I'll give it one more go

@damaged_goods said in Are there genuine Duet2 wifi's in stock anywhere?:

@nuramori Do you know if I can run 2 small stepper motors, in parallel, off one stepper driver?

Yes you can.

@leckietech the default mode in 3.3 and earlier is stealthChop at very low speeds switching to spreadCycle at higher speeds. in RRF 3.4 the default mode is spreadCycle.

If the spurious short-to-ground reports are a side-effect of running in stealthChop mode, then using spreadCycle instead should avoid them.

Hello again thanks for the answers while I was waiting for the answers I realized the problem was from the config then I see the replies I disconnected the 24v from out0. also changed the bed output from out0 to out2. everything is working well right now sorry for the messy wiring and bad "color blob" wiring diagram. it was my first project

Thanks to everyone.

@mjimeyg Bootloader and firmware are two different things.

@dc42 - any ideas? or just toast?

@szalek we will replace the daughter board. Please email warranty@duet3d.com and include a link to this thread.

@bjornh i suggest you upgrade to 3.4 and test the issue again and report back

Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.

@kazolar Ref cooling the control boards, what I did on my old Duet Ethernet +Duex 5 setup was to attach thermistors to a couple of the driver chips with a small blob of epoxy adhesive, and use these to thermostatically ramp cooling fans (IE, fan speed increased with driver chip temperature). With my Duet3 setup, I've found that additional board cooling isn't necessary despite some of the motors being NEMA 23s @2.4 Amps. But my boards are all vertically mounted and "open" rather than enclosed so your mileage may vary.

@damaged_goods no, it's not possible

@barracuda72 there is no resistor, only the cables solderded.

Just cutted wired and it worked, thanks

@nuramori I have 5v and 24v on my Duet 3 and 5v, 24v and 48v on my fysetc spider. Each are connected to the same SSR and triggered by PSON

@droftarts @infiniteloop Thanks for your help