@tristanryerparke we plan to implement torque mode experimentally on the EXP1HCL in the near future.

@stuartofmt Thanks, you're right - I could reproduce this. I will fix it in 3.4.6 and 3.5-b4.

@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.

@tecno as I indicated in my previous response, to use 2-wire mode you would need to add a pullup resistor to +10V or greater to meet the minimum voltage and current requirements, and even then it might not work because the voltage drop when triggered in 2-wire mode has not been specified.

@dc42 thank you! 😄

@supertb1 @Phaedrux, please go ahead and mark this issuer as solved. Thanks for every one help.

@Phaedrux Yeah thats a total shitstorm (pardon my French). So b3 is not a viable option regretably 😓

@dc42
Makes sense apart from DWC has always passed multiple M7xx commands for filament changes
Putting M703 in Tnpost.g doesn't really work as many time's your changing filament but not tools.
It could affect power loss scripts as well I guess?

@tom300z said in Delta (partially) ignores axis limits:

Your anti Spam bot is a bit trigger-happy

I’ve upvoted your post, which should help. Make sure you confirm your email address, if you haven’t already, otherwise you won’t be able to reply to this post.

Ian

@jay_s_uk said in 3.5.0-beta.3 - DWC reverting to 3.4.5 after upgrading:

@stuartofmt maybe clear your cache in your browser

OWATAGOSIAM !!
I usually have browser set to clear cache on exit. Had to change it a few days ago and forgot to set it back.

I'm going to add /# to that url so I don't get caught again!

THANKS!

@mikeabuilder thanks, bug confirmed and logged at https://github.com/Duet3D/RepRapFirmware/issues/804.

dc42 created this issue in Duet3D/RepRapFirmware closed [Bug]: Error on "echo tools" #804

You can mark this as solved.

Turns out for some reason I had to delete my old motion recordings to get the new ones to show up.

They are appearing for me now.

@Proschi78 As I said, if I select the tool before doing G29 so, T1 + G29 it works. But I think it should work without T1 as I specified U axis in M557. Also it should not go crash in other tool. Perhaps @dc42 can chime in. I'd be happy to try to help debug the issue.

@T3P3Tony
I've ditched using start.g totally because it made more problems for me than it solved.

If my recollection serves me right though, i'm pretty sure the changes David did in b2 solved this perticular issue.

I'll remove this thread as a question so it won't remain as "unsolved" at least.

@mikeabuilder thanks, I've logged this as a potential bug to be investigated before the next beta.

@chrishamm After many prints, this issue did not appear again. So I have good hope it is fixed.

@wiego the CPR of an encoder is usually four times the quoted PPR. So try specifying 2000 instead of 500.

500/2000 is still rather low, most encoders do at least 1000/4000.

@tas no worries. In your case I would have assumed bad signal, but your signal strength is pretty decent at -55dBm. Nonetheless, if your antenna is in an enclosure or close to a wall, consider reloacting it.

@Yordan Thanks for reporting this, I can confirm this bug. I am working on a fix.

Edit: Now fixed, we'll provide this as part of the next RRF 3.5 beta.

@chrishamm If you follow the thread, we don´t have to press EC-stop anymore.....

thats what I ment about a new thread. To messy here. Don´t wanna tell everything twice