New experimental firmware 1.19beta11
-
David,
Can't see the upgrade notes on that link.
-
Cool, I see everything for my quad idex is here…will try it soon
-
Just tried it
This is my HomeA code – HomeW is similar, just in the other direction:
G91
G1 A 600 F3000 S1
G1 A-4 F600
G1 A 10 S1
G90The G1 S1 line doesn't crash anymore, but the carriage doesn't move -- it thinks it homed, but it didn't go anywhere.
-
Is the space after 'A' really there? Or it's just copy and paste formatting?
-
G1 A 600 S2 – moves it into/passed the limit switch --
using S1 it doesn't move, doesn't crash, though it thinks it homed. M119 using move with G1 S2 to moves into the limit switch triggers the appropriate limit switches, and moving back releases them.
Let me know if you have patch for me to try, I have a build environment working -- or you can share a test bin file too.
I can try it when i get back from work --Double checked everything is connected correctly -- Driver 11 change works fine.
-
Is the space after 'A' really there? Or it's just copy and paste formatting?
The space between A and the number doesn't matter. FYI tried it with and without, but you can do G1 A 10 – that works the same as G1 A10 -- gcode parser doesn't care about the space after the axis.
-
David,
Can't see the upgrade notes on that link.
Sorry, the link got trashed by the forum editor. I've corrected it.
-
Just tried it
This is my HomeA code – HomeW is similar, just in the other direction:
G91
G1 A 600 F3000 S1
G1 A-4 F600
G1 A 10 S1
G90The G1 S1 line doesn't crash anymore, but the carriage doesn't move -- it thinks it homed, but it didn't go anywhere.
There are a couple of bugs in DWC that affect the ABC axes. Chrishamm is aware of them. Homing the A axis should work, and G1 commands with A parameters should work too. However, DWC shows the A axis as homed even when it isn't, and the jog buttons for the A, B and C axes don't work because the wrong command is sent.
-
Yes, I'm aware that the web console has some issues – home W and home A though don't work even sending commands manually.
for example
G1 A600 F3000 S1or
G1 W-600 F3000 S1doesn't produce a move, so I can't home them -- substitute S2 and they move, with S1 -- they don't, must be some other bug with S1 setting
-
Home A and Home W work for me in firmware 1.19beta11, using the homing buttons displayed by DWC. Are you sure you have the endstops configured correctly in M574? Use the Machine Properties page of DWC to check that the states of the homing switches are reported correctly.
-
Yes homing switches are reporting correctly in the machine properties and in M119
M574 X1 Y1 Z1 U2 V2 W1 A2 S0
here is homew.g
G91
G1 W-600 F3000 S1
G1 W4 F600
G1 W-10 S1
G90here is homea.g
G91
G1 A600 F3000 S1
G1 A-4 F600
G1 A10 S1
G90in all cases the S1 lines do nothing, they don't move, then I see them move in the opposite direction 4mm, and that's it.
In fact when I home other axis – I see the printer go into busy then come back to idle, these never go into busy mode.
I was homing with G28 A and G28 W too.
That's the version I'm using -- tried your bin in git, and tried building latest git myself. Same result
-
FYI
Not sure if it matters for this purpose. The end stops I care about for W and A are 5 and 6. (X-0,Y-1, Z-2, U-3, V-4, W-5,A-6)
They're not triggered when carriage is not near them, however end stops 7,8,9 say they are. They're not configured as anything – those steppers will be extruders, so not sure if those end stops should be configured as something? -
The other bit, let me know if this is not right – I'm using 2 wires with my end stops -- I can add a third if it's necessary. 2 wires work with other axis. I don't have 3.3v connected -- I leave it unconnected, I assume you have a pullup. Let me know if that's not right in this case.
-
You are using normally open/active low endstops (S0 in M574). This is opposite to what most people use, i.e. normally closed switches, which is what I tested with. It shouldn't matter, but might possibly be relevant.
-
I've started using them this was since IMO it's safer as the switch is only job is to sync the signal line to ground, and carries no current, so if there is a pullup on the board, then the switch does it's job and all is fine. Since I'm not done wiring yet, I normally clip off the third pin on the switch – the NC pin. And I just connect 2 wires. With other applications with Marlin and Smoothieware, I just enable the pullup, I am assuming you have a pullup there already. If you think flipping it around to active high with 3 wires will get it working. I can try that when I get home (I thought I was done wiring, but adding a third wire to the end stops would be fairly easy.
-
NC endstop switches are normally used so that if a wire falls off, the carriage stops immediately when homing, instead of the motor trying to drive it through the endstop.
-
NC endstop switches are normally used so that if a wire falls off, the carriage stops immediately when homing, instead of the motor trying to drive it through the endstop.
Yep, I was thinking it over – I'll rewire my switches when I get home I keep 2 wires and just swap the NO to NC. (I'll have to replace the switches since I clipped off the NC end because I was trying to make everything neat) -- I had my wife check and I have at least 6 limit switches left over -- so I have enough to replace all 6 to use NC active high, I haven't setup Z homing yet -- I am considering using 2 Z limit switches and add a second driver for my 2 Z steppers. No sure if it's worth the effort.
My thinking was to do active low and only have the end stop trigger on homing. I go over the top and use silicone wire with heat shrink everywhere -- so my wires are as secure as it gets, but it makes sense to use NC to keep the machine from going crazy if there is an issue.
-
Installed today no issues with installation. Running 1.19 beta 11 and wifiserver beta 10. Only tried one print but got this error message:
Error: Failed to load height map from file heightmap.csv: bad header line or wrong version header
Should I have read the release notes?
-
I forgot to mention in the release notes that the height map format has changed, to a!low different X and Y spacings. You will need to run G29 again to generate a new height map file.
-
Okay thanks David.
