@dc42 Thanks for the help I managed to do it

If your windows / arduino can generate HTTP you can use https://github.com/Duet3D/RepRapFirmware/wiki/HTTP-requests. This is quite a straightforward interface, e.g. a GET of http://11.22.33.44/rr_gcode?gcode=G28 will execute G28 (ie home all) on the duet machine at 11.22.33.44. It has file operations (upload, download, list, delete etc.), execute arbitarray gcode, and let you get any part of the object model (which lets you check almost every element of the state or status of the machine).

If you install curl you can do this from pretty much any scripting language (even .bat files).

If you have a Pi connected to the duet device there's also the DSF: https://github.com/Duet3D/DuetSoftwareFramework This will let you do anything the duet can do, but requires more detailed and particular programming knowledge.

@jay_s_uk said in RFF 3.42 extruder change:

@paolozampini1973 you have more than 1 tool defined though. you don't need to have a physical toolchange to have different tools

So what do you think I should do delete them?

@tecno said in Suddenly extrusion buttons Extrude/Retract are grey!:

M563 P1 H1 F0

You don't have a motor assigned to the tool. You need a D value.

EDIT: I see Gloomyandy got you there first.

@selva_tvi T1 just pauses so if you want to do more than that you'll have to use a different trigger and create a trigger file accordingly.
See here about setting up power resume https://docs.duet3d.com/en/User_manual/Tuning/Resume

@jay_s_uk

Thanks for the help...I actually got it working now. This time I only commented the M558 line out

@selva_tvi Your tpost2.g has M568 P2 S1 with the comment to turn on mixing. However, M568 to turn on mixing was deprecated a long time ago and M568 is now used for tool settings. So if you are using firmware 3.3. beta 2 or later, then M568 P2 S1 will set the active temperature for tool 2 to 1 deg C, which is consistent with the behavior you are seeing.
I suggest you remove or comment out and M568 commands or use them to set the desired temperature as per the documentation https://docs.duet3d.com/User_manual/Reference/Gcodes#m568-set-tool-settings

@selva_tvi We got the solution. Pin assignment in config.g has to be changed.

;Filament Runout sensor
M591 D0 P1 C"e1stop" S1
M591 D1 P1 C"e2stop" S1

Accordingly it has to be connected to the board as per the given diagram

Octopus Pro Endstop Pins.JPG

We can consider this as solved and we can close this case. Thanks for the support

@jay_s_uk
Thank you
An issue has been solved

If you want to use your endstop as a emergency stop you can re-purpose them at the end of the homing file to act as an estop. Just be sure to set them as endstops again at the start of homing.

https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m581-configure-external-trigger

@phaedrux Ah yes thank you very much, adding g29 s1 to the cura start code seems to have solved the issue!

@gloomyandy this is a great idea. I would love to try it, but it seems the exp1.lcd_rst pin isn't exposed looking through https://github.com/Duet3D/RepRapFirmware/blob/3.4-dev/src/Config/Pins_Duet3Mini.h

Is there an alternative name @dc42 ?

Edit: Actually, I took a look at the big dipper schematic and it's simply shorted to 3.3v to pull the signal high. It seems like triggering lcd_rst wouldn't be possible

@hackinistrator thanks for your reply and sry for my delayed answer. Leadscrews aren't an option as I have to stick with the rotating movement instead of linear movement of the axis because it drives another belt.

The motors are running at 24V.
Yes, I need 2Nm roughly to be able to move the axle. I have a gear ratio of 5:1 with 1/8 microsteps and two 1.9Nm Motors which leaves me with 3.7Nm left if 19,51% of the max power of the motor is preserved through 1/8 microstepping regarding the faulhaber website.

In theory and in praxis this is enough, the motor is working fine now. Only thing that I've pin pointed is that the timing belt is flexing too much and I am working on a solution for this at the moment.

@gloomyandy I'll check it tomorrow since I want to finish this print(guess I'll just sit here all night and resume the print after every fault). Where should I look for the sensor on the hotend?

@re_tour said in BLTouch bed leveling is always off:

RepRapFirmware for STM32F4 based Boards (biquskr_rrf_e3_1.1) version 3.3.0_11 (2021-11-04 23:04:15) running on STM32F4

Ah, ok.

@jay_s_uk

So I used a fresh SD card and reflashed the firmeware and all seems well. Thanks for all the help.

@phaedrux @phaedrux Got it going, many thanks! I considered doing that but was unsure if that was the proper course at the time and decided to get some help before I dug a deeper hole lol.

@dc42 okay thx, but i installed RC3 already so it is okay for me i guess. 🙂

G10 P0 X0 Y-20 Z0 ; set tool 0 axis offsets

You only have a single nozzle, so why do you have an offset in Y? Tool0 nozzle should be considered 0,0,0

G1 X32.3 Y32.3 F10000
In your homez you should position the probe at the center of the bed for best results.

G10 L2 P1 X0.00 Y0.00 Z1.78
Not sure why that offset exists in your config-override.g. It shouldn't. Have you sent M500 at some point?

@geekoam said in Unable to set Z-offset, distance between nozzle and bed:

where is the right place to enter in that The nozzle needs to be -0.29 closer to the bed after a G28?

Adjust your G31 Z value. A higher value moves the nozzle closer to the bed after homing. A smaller value moves it farther away after homing.

So if you need to be 0.29 closer to the bed, add 0.29 to G31 Z

@whopping-pochard said in Single axis "printer" possible?:

Poe's Law strikes again!! 😂

But I did include the wink as required. 😉

Frederick