That worked perfectly, thank you! I was afraid the issue might have had to do with how the SBC sends commands to the Duet. Startup script is running normally now.
@dc42 Could the new conditionals be used to accomplish this? I've just started to add them to my macros and things this evening. Would it be possible to say something along the lines of:
while sensors.filamentMonitors[0].distanceMoved <= 300
G1 F600 E-25
I'm still learning the syntax and what all of the implemented object models are, but is there a way I could make that happen?
I just want to chime in, had the same issue after adding bed levelers and getting my bed really flat.
This created a new problem where Babystepping was "undoing" itself within 1-2 seconds. I could hold my hand on the Z rod and feel it bumping back. and watch the lines flatten out on the bed while printing, and then unflatten as it reset to Z=0.
This totally solved it for me. I typically have to babystep -0.25 and now I can again.
@dc42 Something I just thought of - why not use the rotating magnet filament sensor for this? I could place it in the bowden path between the selector and my extruder (much closer to the selector) and use that to monitor whether the commanded retraction to the selector matched the actual distance traveled by the filament. I would then only need the single sensor - no switches or combinations of switches with other sensing techniques. That would also allow me to monitor filament feed issues during a print.
Many programs used to send GCodes convert all characters to uppercase. In firmware 1.19.2 and later, within any quoted string you can use a single-quote character to indicate that the following character should be changed to lowercase. For example, M587 S"ABC" P"P'A'S'SW'O'R'D" would specify that the password is "PassWord". Use two single quote characters to represent one actual single quote character in the password or in the SSID. For example, if your SSID is "Pete's network" then enter "Pete''s network".
@dc42 I got it figured out. Not sure what I was doing the first time around, but after playing with the config for a bit I finally went back to the RRF configurator and was able to get the proper setup. Everything is up and running now on RRF 3.0 and I'm loving it. Thank you again for all of the help over the past couple of days
Got it! My machine is now running 3.0. I had to revert back to 1.19, but the second time around I was able to successfully update everything. Time to update my config file and start playing around. Love the new WebControl design, btw!
if its a relay module with a transistor to drive the coil, then maybe check the markings on the relay to see if its a 12v coil? it could get a bit toasty if fed 24v
@dc42 I will upload a video this weekend of the material change in process, so that everyone can see where the issue lies and better understand how the mechanical side of my filament selector works.
On another note, Thank you for always being so attentive to this forum! I don’t think I’ve ever posed a question that you didn’t have some input on. I really appreciate that!
Has run into same issue with E-axis today. Was trying to set up print resuming after power loss and found out that RRF is ignoring G92 command in the "resurrect.g" file.
Basically, what happens is when I resume printing after power down the print head goes over the print and then it starts extruding all the way from 0 to the value that has been stored in "resurrect.g".
@danal I do not have a webcam at the moment. I’ll probably add one in the future, but for the time being I’d just like to be able to control my printer from anywhere, so If I need something last minute I can start it from work/school. I’ll check out setting up a reverse proxy. Thanks!