@dc42, Thanks for the answer David.
Posts made by ocornet
-
RE: runonce.g file purpose ?
The file is named 'runonce.g', but the comment in this file mention 'run-once.g'
About the purpose, I don't have invented it, it's described in the comment in the file.; run-once.g ; called after config.g. When it has been executed, it is automatically deleted! ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Jan 30 2020 01:40:41 GMT+0100 (heure normale d’Europe centrale) M552 S0 ; disable network G4 P500 ; wait half a second M552 S1 ; enable network G4 P1000 ; wait a second M587 S"WiFi_SSID" P"WiFi_Password" ; configure WiFi M552 S1 ; enable network
-
runonce.g file purpose ?
Hello,
After generating a RRF3 config file with RepRapFirmware Configuration Tool, the Wifi settings of the board are located in a file called 'runonce.g' that is supposed to be deleted after being executed
As the M587 command could not be located in config.g file, I understand the purpose of the runonce.g file.
But it seems to not work. The file stays in the sys folder and is not deleted, and the wifi settings in it are not appliedI've searched infos about that, but found nothing.
Olivier
-
RE: IDEX and axis definition order
Strange ... reverted back to X3 in M563 and now it's working ...
Another question related to the tool change, in the tfree#.g, as per the wiki example I lift up the Z axis (in my case) 5mm before parking the tool.
After tool change, if I send the next position where to go, the Z go down 5mm just after living parking position and while moving to this new position.
Is there a way to move the Z down only after reaching the new position and not while moving to the new position ? -
RE: IDEX and axis definition order
Missed it.
In this case axis number are as this : X->1, Y->2, Z->3 and U->4 ? I'm a little bit lost ...
It's not X->0, Y->1, Z->2 and U->3
E0 and E1 are obviously not considered as axis.
I just tried with X4 in 563 but it does not work.
After tool change I don't see the U tool offset mapped to X
If I try to move X axis, the U carriage does not move.
I've double checked my config.g file and don't see obvious mistake.
I share my config.g file if you can have a look at it.
config.g -
RE: IDEX and axis definition order
Thanks for your answer David.
I forgot to say that I'm using RRF3 version.
In the case I use second X carriage on E2 driver with command M584 X0 Y1 Z2 E3:4 U5 (drive 5 on Duex) my M563 command for tool config should be : M563 P1 D1 H2 X5 F2
Am I right ? -
IDEX and axis definition order
Hello all,
I'm currently configuring a Duet2 Wifi in IDEX mode with dual X carriage on the same rail.
I've a question regarding the M584 command for the axis definition.
After reading wiki and other ressources I always see that the second X carriage defined as U use the E0 driver, E0 shifted on E1 driver and E1 shifted on E2 driver (drive 5 on Duex).In this case the M584 command look like this : M584 X0 Y1 Z2 U3 E4:5
Why not connecting the second X carriage (U) on E2 driver (drive 5 on Duex) and have the M584 like this : M584 X0 Y1 Z2 E3:4 U5 ?Is there any reason why we use E0 motor for the second X carriage (U) ?
-
RE: Duet WiFi and PanelDue Clones.
At least the price for the combo had indicated you that it was a clone, no ?
At this price you normally get only the Duet WiFi ... -
Duet3D and dual X carriage
Hello,
First message for me here and happy owner of a DUET3D Wifi on a CR-10.
I just have question for a friend of mine, is the DUET3D could be capable of managing a dual X carriage like on the Formbot T-REX3 ?
I'm aware that in this case I need the expansion board to increase the stepper driver number as 6 motors are to be driven.Thanks in advance,
Oliver