Posts made by Alva

@oliof Hello,
Background story: I was trying to translate the error status bit which the board has reported back. I looked at the data sheet to figure out what the error corresponds to is and got confused.
As i attached the image of datasheet and the duet event table above, Tried to compare the values that i got back and computed the binary for it but the value was bit different.

the binary of 192 is 1100 0000 , but according to data sheet it is 96: 0110 0000 if we take the 8 bits from MSB 31 to 24.
Conclusion : The above mentioned discrepancy made me look into the RRF in the section CANlib/src/RRF3common.h -> union StandardDriverStatus , it is calculated differently. And it make sense now why the value was 192.
But can be a problem if someone wants to translate the error status bits to the proper error message. Thank you for your time.

Hello,
Can you please help me understanding how the error status bits are output when there is a driver warning or error based on the trinamic driver datasheet ?
.

I cannot really understand the values. For example 26th bit is high means Overtemp pre warning flag. What would be the output status from Duet?.

@dc42 Thank you , I will check it out

@dc42 It seems to be working. I have tried all the above conditions and works as intended. Can i expect the same fix for Duet3 6HC board as well, as i observed the same behavior in it as well. Thank you

@dc42 I have tried beta2 and same error happened. I think you are already working on it. I have another topic on multiple motion system active now. Thank you .

@dc42 Thank you

@Alva Looks like it is a timing problem or something.

@Alva

@dc42 I have edited the code and logic a bit. Found different cases:

; File Name: 		/sys/daemon.g
if(!exists(global.daemonStop))
	global daemonStop = false	; Set to 1 to stop the daemon.g, it can be use to upload a new daemon.g file

while( global.daemonStop == false )
    if(state.status== "processing")
        G91
        M596 P1
        G1 U5 F300      
        M596
    G4 P0
M99; Exit

test_2nd_MS.gcode
.
This happened when i activated the daemon before the move to X0 Y0. But if i activate the daemon after that then it works perfectly. Cannot relate whats going on.

set global.daemonStop = true ; stopped the daemon
M118 S{"starting to move"}
G90
G1 X0 Y0
M400 S1
G91
set global.daemonStop = false ; activated the daemon which only use U axis
G1 X100 Y100 F200
M400 S1
G90
M118 S{"move done"}
M99

@Alva Looks like there was a mistake in the 3.6.0.beta2 release and David updated the new one today. I will try out that one.

@droftarts

• daemon(2).g
• mini(1).gcode
  Hello , i have updated the machine to 3.6.0.beta2 and tried a simple logic as seen in the mini-1.gcode which is attached. while it starts the print i manually set the flag to enable the daemon.g and the daemon.g is also attached. And the same error occurred again. Do you think there is something wrong with the way that i understood the second motion system? or am i doing something wrong? weird that my logic worked in 3.5. fw version.
  Please let me know. Thank you.

@gloomyandy Okay, I will wait for the release then. Thank you

@gloomyandy Hello ,
Sorry for the late reply. Was on vacation for few days. I have continued the "experiment". Ignore the number of extruder drivers i had above. I rewired and reconfigured everything to the very simple set up. I have a Duet 3 mini 5+ board with CAN expansion motor board and a tool board. I have X;Y;Z set up via the motor board and the tool axes from the tool board. I have a stepper motor connected to the mini board and i configured it as U axis. It is just for the experimental set up. (My intended use is to load filament in the other tool while the machine is printing). So the U axis is my fake tool for example. I am just experimenting before i want to really implement it.
My findings so far.:

• With the firmware version 3.5.3 , it is working.
• With the firmware version 3.6.0.beta1 i am getting the error that i reported before.
  daemon(1).g config(3).g .
  Thank you .

@Alva I tried another test, while the machine was printing i trigerred daemon with a flag global.called and created the condition when global.called= true to select the second motion system and move the W axis. then the axes moved to the Y max and crashed and machine still remains in the printing state doing nothing.

@gloomyandy i am just setting the led strip colors of the corresponding active tool and moving the u or w axes based on which tool is activated to its minimum position

the same ocurred to me but it happened when i was experimenting with the second motion system. While the machine was printing , i wanted to move the unused axes. i have trigerred a flag in daemon.g to select the next motion system and move W axes and machine started moving to a different place and stopped. and the machine is still in printing state

@droftarts Is there any way to print back the axes used by the motion systems? I have tried the sample code that you have sent me above and it resulted in the error as shown in the figure below.
. I tested the above piece of code as a macro. In my system i have X, Y, Z, U , W axes and tool 0 is moved by u and tool 1 by w axes.

echo "start testing 2nd motion system"
T0
G1 X100 Y100 Z25 E0.1 F1000
G1 X110 Y100 E0.1 F1000
M596 P1 ; selects the second motion system
T1      ; select tool (set temperature changes from standby to active temperature)
M568 P1 S200 R200 ; wait for temperature to be reached
G1 E5 F1000 ; prime extruder
M596 P0 ; change back to first motion system, while the above happens
G1 X120 Y100 E0.1 F1000
M400 ; wait until motion stops, release owned axes and extruders from motion systems
T1 ; first motion system takes over T1, parking T0.
echo "done testing 2nd motion system"

Line number 6 is selection of the tool and is clearly not X axis.

Hello,
I am trying to experiment with the second motion system. I was reading the whole documentation about the second motion system and couldn't really understand how to assign the unused axes to the second motion system. Can someone please help me understanding the concept? How do i map the unused axes to the second motion system? Thank you

M596 P1 ; selects the second motion system.

I want to somehow maps the unused tool to the second motion system