Core XYU Z Movement Issue

pcsentinel

@hackinistrator Same result, no change.

hackinistrator

@pcsentinel can you send m669 in console and paste the resuly here?

pcsentinel

@hackinistrator
Kinematics is modified Cartesian, matrix:
1.00 1.00 0 0 0
1.00 -1.00 0 1.00 -1.00
0 0 1.00 0 0
0 0 0 1.00 1.00

pcsentinel

Further observations.

Following a reboot, with tool 0 active all movement is as expected.
Issue a T1, to make Tool 1 active, issue a G1 Z5, Z moves down and U stays where it is.
Issue a T0 all movement as expected.
Issue a T1 (for the second time) the issue occurs whereby at the same time as the Z movement is taking place, U returns to the home position.

Further, When Tool1 is active G1 U commands acts as expected, but G1 X commands move the U carriage and not the X carriage.

Phaedrux

I don't suppose you'd be willing to update to RRF3?

pcsentinel

@Phaedrux Hi, I didn't want to, but I am now thinking it may be inevitable, if only to eliminate V2 as a source of the issue.

Just dreading having to go through the conversion process!

Phaedrux

It's not so bad really. Starting with a clean config might not be the worst thing to do in cases like this.

M201 X1000 Y1000 U1000 V1000 Z250 E250,250

I just noticed in your config a small error. You have a , that should be a :. Things like that can sneak in when you're doing a lot of manual edits.

If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them. Reboot after each. Use M115 to verify the firmware has been applied.
https://github.com/Duet3D/RepRapFirmware/releases/download/2.05.1/Duet2Firmware-2.05.1.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.0/Duet2and3Firmware-3.0.zip
https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip
That will get your firmware and DWC up to date.

You can see the change logs here:
https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x

For your config, might be a good idea to run through the configurator tool and generate a fresh set for RRF3.
https://configtool.reprapfirmware.org/Start

Then you can add back in your additional axis and things.

Backup your existing config files in the sys folder in case you want to switch back to RRF3. IT’s easy to switch back and forth, just upload the zip file for the version you want and then upload your config files.

These documents will come in handy during the conversion.
https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview
https://duet3d.dozuki.com/Wiki/Gcode

And testing your config for errors with M98 P"config.g" is helpful.

hackinistrator

@pcsentinel said in

Further, When Tool1 is active G1 U commands acts as expected, but G1 X commands move the U carriage and not the X carriage.

i think this is normal , when T1 selected x movement is tied to u .

what strange is u moves when you try to move z .
maybe remove m501 and try .

pcsentinel

@Phaedrux Hi Phaedrux, well I but the bullet and upgraded, it wasn't as bad as I had anticipated. Thanks for the kick up the butt!

I used K5 rather than a full matrix layout as that should be fixed in 3.2.2

Unfortunately it didn't stop the issue from occurring. However as I had spent so long looking at the config, something popped out, The Tool 1 definition includes the X3 command so that X moves are translated to U moves when a normal gcode file is processed. And this points to my other observation above that X moves with Tool1 selected move U and not X. So I thought I would experiment, if you remove the X3 from the line then the issue does not occur, i.e. with tool 1 active Z and Y moves operate exactly as expected.

But of course you cant leave it like that otherwise printing wouldn't work. So I thought well, lets just run a test print with Tool 1 as the active extruder. Guess what Z moves when printing do not cause the U carriage to move home.

So it appears that this issue is only present when not printing and probably (?) only occurs with a CoreXYU configuration. It just makes things hard to tune. And also made me waste peoples time with this non-ish issue.

Note, I have yet to do a full 2 extruder print, but I have more confidence that it will work now.

pcsentinel

@dc42 Hi dc, just thought I would add a prompt to my final comment in this thread, it may be worth a quick look and add it to the bug list.