Duet3: Tool Coordinates N/A in DWC
-
Also, if it helps, I modified a bit of code to log position to the chrome developer console, so that I could continue to commision a new printer with Duet 3. I believe the following proves that basic JSON parsing of the socket output of the Duet3-to-DWC2 is working down in the connector itself. I did not attempt to trace any further through the code, so I don't know where the eventual disconnect occurs.
The "console.log" statements added to this spot in the code:
case 6: // Process model updates data = JSON.parse(e.data); // Deal with generic messages if (data.move) { if (data.move.drives) { {console.log("X",data.move.drives[0]);} {console.log("Y",data.move.drives[1]);} {console.log("Z",data.move.drives[2]);} } } if (data.messages) { data.messages.forEach(
Produce output like this:
app.fee4fdb1.js:139868 Y {position: 86} app.fee4fdb1.js:139869 Z {} app.fee4fdb1.js:139867 X {} app.fee4fdb1.js:139868 Y {position: 36} app.fee4fdb1.js:139869 Z {} app.fee4fdb1.js:139867 X {} app.fee4fdb1.js:139868 Y {position: -10.7} app.fee4fdb1.js:139869 Z {} app.fee4fdb1.js:139867 X {} app.fee4fdb1.js:139868 Y {position: -0.7} app.fee4fdb1.js:139869 Z {} app.fee4fdb1.js:139867 X {position: 13.1} app.fee4fdb1.js:139868 Y {position: 354.3} app.fee4fdb1.js:139869 Z {position: 5.05} app.fee4fdb1.js:139867 X {} app.fee4fdb1.js:139868 Y {} app.fee4fdb1.js:139869 Z {} app.fee4fdb1.js:139867 X {} app.fee4fdb1.js:139868 Y {position: 279.3} app.fee4fdb1.js:139869 Z {} app.fee4fdb1.js:139867 X {position: 12} app.fee4fdb1.js:139868 Y {position: 280} app.fee4fdb1.js:139869 Z {position: 0.05}
-
Well... very interesting. It suddenly started working.
I am not 100% sure, but the thing that changed seems to be moving to Beta12 firmware.