Topics created by Giuliano

@giuliano
I don't really know how to interpret that report except it shows the trigger is active

My guess is that the trigger is being activated multiple times by switch bouncing or similar.

You might need some denouncing code at the start like

G4 P20 ; short delay if sensors.gpIn[1].value = 0 ; bouncing M99 ; exit macro

You might also create a global variable in config.g like

global macroRunning= false

At the start of your trigger file put

if global.macroRunning = true M99 set global.macroRunning = true ; do your other stuff set global.macroRunning = false ; last line

Well, it would be a shame to add another drive having 6 HC drives on the board..
Unfortunately I selected and bought the Duet3-6HC based more on the electrical requirements (motor power, temp sensors, FETs..), assuming that doing the SW-connection between an analog-in and the servo speed would be easier. I guess I overestimated my C++ skills 🙂

Can someone point me out how this connection could be implemented? Any input is welcome.

Basically, one analog in (temp or zprobe ? 0..10V would be ideal) should directly drive the extruder stepper speed (0..xxx rpm)
For all other settings I would use G-Codes over telnet

Thanks a lot!

Update: this works now, It was related to the way I imported the projects into the workspace.
This time I imported directly from git and now I can see the different targets SAMxxxx. Before I only had Debug and Release.

I think the import should be described more in detail in the doc, for those new eclipse.

I now run in another issue, that is already covered by this post:
https://forum.duet3d.com/topic/29146/failed-to-compile-rf3-4?_=1657517077311