@ChrisP This will be fixed in the next versions. For now, you can work-around this problem by putting iterations into curly brackets. Something like job.build.objects[{iterations}].x[0] should work.

The next DCS version will send whole line comments to RRF, too.

Thanks for reporting this, I'll fix it in DWC 2.1.7.

@felek said in External trigger issue - RFF3.01 RC10:

Thanks @Danal for tips but it still doesn't work for me. I only get "busy" state.
I suppose that C parameter in M581 is problem. You didn't use this parameter

Correct, define the pin with 950, then link to that with M581.

DOH!!! Of course. I will give that a try.

Edit: That was it!! Of course, S1 is the default, so I actually had to set it to S0 when I got the "address" right. Final Result:

M584 X0 Y1 U2 Z3:4:5 ; X and Y for CoreXY. U for toolchanger lock. Z has three drivers for kinematic bed suspension. M584 E1.0:1.1:22.0 ; Extruders for three tools. First two on 3HC 1, third one on Tool Board 22 M569 P0 S0 ; Drive 0 direction | X stepper M569 P1 S0 ; Drive 1 direction | Y Stepper M569 P2 S0 ; Drive 2 direction | U Tool Changer Lock M569 P3 S0 ; Drive 3 direction | Front Left Z M569 P4 S0 ; Drive 4 direction | Front Right Z M569 P5 S0 ; Drive 5 direction | Back Z ; End of main board drivers. Expansion boards have three each. ; Expansion CAN 1 M569 P1.0 S1 ; Extruder T0 M569 P1.1 S1 ; Extruder T1 ; At this moment, nothing on expansion CAN 2 ; Tool board CAN 22 M569 P22.0 S0 ; Extruder T2

P.S. THANK YOU! I knew it was something I was staring right at and not seeing.

@dc42 , only panel due restarts, I see the initial screen with the logo, instead the printing proceeds without problems. The strange thing is that when I restart Duet wifi a series of line errors are displayed but I cannot tell you which ones because it is too fast to do it and they do not remain stored in the console. Tomorrow night I check the 5V, but if it were unstable that line can also create all the other problems?

@gtj0 said in G28 doesn't accept object model variables:

@dc42 Would it be a big deal to allow that?

Yes in RRF, less so in DCS.

@Nuramori said in PanelDue no longer connecting on Duet3/io0 with 3.01-RC11:

I decided to just avoid the issue by reprogramming the arduino (Adafruit Metro Mini) to create and use a soft serial port, and poll a different digital pin instead. I'm suspecting that there's something odd about the Rx pin on that board, since it also shares the built-in USB comms with that UART pin. The documentation says I can use it as a normal UART Rx, but hmmmmm......

I recoded it, and now everything is working. Thanks for the input, I hope I didn't waste anyone's time (too much).

Yay! No time wasted but yeah, I got my directions mixed up with the setPullup. It was late (for me anyway). 🙂

I have put new internal builds of RRF at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0 that report the virtual extruder posiion in 'move.virtualEPos'.

Just upgraded to 3.01RC11 and the bug is fixed.
Many Thanks 🙂

@dc42 said in Bug: Unable to home U axis on 3HC:

It's a documented limitation of current Duet 3 firmware that an endstop connected to the main board cannot stop movement of an axis motor connected to an expansion board unless that axis also has a motor connected to the main board. See the Known Limitations section of the release notes, also https://duet3d.dozuki.com/Wiki/Duet_3_firmware_configuration_limitations.

True. But the OP initially had his U axis motor and his U axis end stop on the same expansion board.

EDIT. He fixed the problem by moving both the motor and the end stop to the main board.

Edit 2. From his original config g.
M569 P1.1 S1
M574 U1 S1 P"^1.io3.in"

@dc42 Same here now. I just powered up the printer and the PanelDue is working fine @115200 with the two M575 entries. Not sure what happened last night. Maybe I didn't really reboot after editing the config file. Anyway, all is well for now.

This doesn't just affect the aux port in raw mode, it affects commands received by the Duet USB port too.

@Phaedrux Yeah I remember you mentioning that recently. Maybe the OP just needs to add those as well but if he didn't need them for 2.05 maybe there is a different behavior.

it works again now. I just deleted M550 and reinstalled it. Thanks for all you do.

Thanks. If the problem occurs again, please start a new thread, but you may wish to link to this thread in it.

(hope i didn't step on any toes (too hard) just didn't want to see the new thread locked if the trend continued)

I found out that my tpost0.g is corrupted. Recently after updating the firmware, it seemed like some of my files were corrupted.

Thank you. After update firmware to 3.01-RC11 extruder fan turn on and works after starting print.

@mwolter Thanks, I can reproduce it now. Will be fixed in the upcoming DWC 2.1.6.