Topics created by DeltaCon

@Phaedrux, thanks, exactly what I needed!

@jay_s_uk Thanks jay - I think I'm there....it's coming on and off anyway as planned - I noticed that the frequency F1000 line in the gcode seems to be controlled by the mm/sec speed setting in Lightburn - when I changed it to 500mm, it changed the gcode to G1 x160.587 F500 and the laser didn't work.

Changed that to 1000 mm/s and it worked. Also added S1 too and works fine.

Thanks for your help mate, I really appreciate it. I can actually use the thing finally! Awesome. Owe you one. Thanks so much.

@dc42 said in Endstop on 2nd Y motor:

... When you home Y, each switch will stop its own motor.

Okay, so in M574 the endstops pins must be defined in the order the motors were assigend in the M584. That seems an obvious thing to do, but I did not realise they would show up as one "virtual" endstop. I wil try. First I need to recrimp my endstop cables. In the factory ones I have most pins seem to make no contact...
Thanks!

Disregard my statement above - with further testing - it doesn't seem to play along.... - Let's wait for the firware update

@dc42 That sounds plausible. By now I wish I had not cheaped out on the 0.6, but it became a too good a deal when the DuetWifi becaime popular 😉 But it still works just fine. I will certainly buy a new one some time, but that will not be for my Rostock V2, but probably for a custom design.

@DeltaCon, it's not confined to the 0.6 version, but the build for the 0.6 version has fewer buffers so if buffers are being lost then they will run out faster.

Let me know if you manage to find a way to reproduce it. It's probably related to network activity (multiple network clients? clients disconnecting?), or USB activity, or turning debugging on (M111).

Yeah, that makes sense even for an electronics noob like me 😉
I changed that, and will report back. Thanks!