Topics created by jay_s_uk

@dwuk3d yes, it'll work with that

@dc42 https://github.com/Duet3D/RepRapFirmware/issues/1097

jaysuk created this issue in Duet3D/RepRapFirmware open [FeatureRequest]: Add support for MFMT command in FTP implementation #1097

@CrazyCreator
For anyone who has the same problem after me, here's how to connect or insert the ribbon cable.
You have to flip the small black bracket upwards, then insert the cable, and then flip the bracket back down. This secures the cable.
Of course, you should have known beforehand that there is a bracket on these mini jacks.

IMG_0786.jpeg

@Proschi78 I can't see any reason for it to be an issue👌

@oliof said in Fysetc StrideMax Dual - CAN-FD Expansion Board:

@Exerqtor seems your wish has been fulfilled

87d9956f-a184-48d0-aa61-acc25e5e0d2a-image.png

Oh wow! They managed to let the typo follow all the way to production though! The label on the product box i got mine in say Daul 😆

@gloomyandy This was my first time updating from the Duet; RC1 was a fresh flash from USB, but yep I'm on Duet3 MB6HC + SBC

You can write a code in daemon.g that would clear the global variable for you if your axes aren't homed (which would happen in you disable motors or idle hold anyway)

The only thing is that you might need to put the code in a while loop in daemon.g so the variable get cleared faster (daemon.g has some delay, that you can lower with a while loop)

Be aware, when you home an axis it gets "un"homed during a homing sequence, therefore you need to set up additional variables to prevent your G32 global variable get cleared when you home an axis that was already homed.

Just want to second this. I would love if it were a GCode value (like an M203, but for a ceiling on the flow rate). That way it could be input into the start GCode or filament files, and could be changed/checked via the console on the DWC.

Well I suppose one could say that X is always negative and Y is always positive and that if one thought about it hard enough and for long enough, there might be a reason for that. But it doesn't get away from the fact that 1 micro-step is 0.0125mm and a cheap mechanical micro-switch ain't gonna be accurate enough.

23/07/2023, 17:55:43 X difference is -0.038 at homing feedrate of 360 mm/minute
Y difference is 0.050 at homing feedrate of 360 mm/minute
23/07/2023, 17:55:06 X difference is -0.025 at homing feedrate of 360 mm/minute
Y difference is 0.075 at homing feedrate of 360 mm/minute
23/07/2023, 17:54:29 X difference is -0.038 at homing feedrate of 360 mm/minute
Y difference is 0.075 at homing feedrate of 360 mm/minute
23/07/2023, 17:53:52 X difference is -0.013 at homing feedrate of 360 mm/minute
Y difference is 0.088 at homing feedrate of 360 mm/minute
23/07/2023, 17:53:15 X difference is -0.038 at homing feedrate of 360 mm/minute
Y difference is 0.062 at homing feedrate of 360 mm/minute
23/07/2023, 17:52:01 X difference is -0.025 at homing feedrate of 360 mm/minute
Y difference is 0.087 at homing feedrate of 360 mm/minute
23/07/2023, 17:51:24 X difference is -0.212 at homing feedrate of 360 mm/minute
Y difference is 0.087 at homing feedrate of 360 mm/minute
23/07/2023, 17:50:47 X difference is -0.212 at homing feedrate of 360 mm/minute
Y difference is 0.113 at homing feedrate of 360 mm/minute
23/07/2023, 17:50:10 M98 P"0:/macros/endStopRepeatability.g"
X difference is -0.087 at homing feedrate of 360 mm/minute
Y difference is 0.150 at homing feedrate of 360 mm/minute

@jay_s_uk Thanks, I could reproduce this one as well and I've got a potential fix ready.

@Acid said in Wrap text on 12864 displays - 3.5b2:

Hi OwenD, I tried this out but for me it only shows line one with the example. Also, S should be P 😉

Yes I tried also with same results
The parser no doubt strips out the new line command and anything following

Would there be anything else we could try?

Nothing I know of.
Would require firmware changes, so one for @dc42

@jay_s_uk Word-based suggestions (autocomplete) will be disabled in the next version. I may add real G/M-code auto-completion to v3.6, but if I do, I'll probably add a new setting to disable it as well.

@jay_s_uk Thanks, will be fixed in 3.5b3.

@jay_s_uk
You could use the delayed start code I have posted here as the basis.
Send your soak time as a parameter and it will report the time remaining at the intervals set.
You'd just have to call it after you set your temps instead of at the beginning of start.g like I have, as I want to avoid having heaters on during that delay.

@jay_s_uk Thanks, I just had a chance to look at it. Monaco editor does not support mobile devices, so I'll disable it on devices with touch support.

@jay_s_uk that's excellent 👍