Posts made by St Taw

@dc42

Thanks for the explanation. Does the object model have anywhere, the hidden value applied to the machine co-ordinates? Not that is will actually help me, just interesting.

I will turn off bed compensation whilst investigating my BL Touch problem just for clarity.

On a slight aside. it occured to me that, as the term implies, 'Bed compensation' assumes the error in height is due to the bed shape. If the error was actually due to the X gantry being in error, say lower in the middle), then applying bed compensation to correct it would result in other errors. It would be expected to improve bed adhesion but as the the correction tapers off the top surface of the print could be dished. I not sayinbg this needs to be addressed, just a thought experiment.

In my attempt to diagnose a z height problem (using BL Touch) on my machine I have embarked on a quest to understand the co-ordinate system.
By this I mean how the co-ordinates are acted upon and reported. What are machine co-ordiantes and user co-ordinates. If their is a document that explains this can someone reference it please.

With no mesh compensation (G29 S2) and no offsets (G10 P0 X0 Y0 Z0) .

I send the tool to Z10. The obect model reports
move.axes[2].machinePosition = 10
move.axes[2].userPosition = 10
The DWC reports Z10

In the Console I then enable bed mesh compensation from a previous learn (G29 S1) load mesh.
move.axes[2].machinePosition = 10
move.axes[2].userPosition = 10.137
The DWC reports Z10.14
So by implication its showing the mesh offset by the difference in machine and user positions.

However if I now send the Tool to 10 (G1 Z10) I get
move.axes[2].machinePosition = 10
move.axes[2].userPosition = 10
The DWC reports Z10

So this suggests the Mesh compensation offsets are hidden thereafter.

I have yet to figure how the BL Touch (sensors.probes[0].lastStopHeight) affects the machine to user co-ordinates reporting.

@chrishamm

I was struggling to even see the difference you suggested but eventually spotted it.
Always have had trouble with spelling

Many thanks.

I'm trying to diagnose a first layer Z height problem which could be a BLTouch fault.

In doing so I wanted to report various variables. By way of example...

echo "sensors.probes[0].lastStopHeight=",sensors.probes[0].lastStopHeight

echo "heat.heaters[0].current=",heat.heaters[0].current

echo "move.axis[0].babystep=",move.axis[0].babystep

The first two above report OK. However the babystep property fails with...
Error: in file macro line 31 column 31: meta command: unknown value 'axis^.babystep'

Can anyone suggest what the problem is.
Thanks

Question: Does the Duet Wifi have the ability to receive on any of its inputs RS232. If so what would be involved in interpreting messages?

The reason for asking is that I have been watch videos of the BambuLabs X1. This has a micro lidar for calibration. But I understand it has problems with some bed surfaces, namely reflection or textures. I would have thought the textures though could be resolved by averaging.

I have a tool changing machine and I thought I could put in place of one of the nozzle tools a Digital Dial Indicator (and perhaps other scanning sensors). e.g. https://www.ebay.co.uk/itm/364668106198

The rational is that we may have very sophisticated ways of sensing nozzle height above bed but its really the physical layer height that is important as extruded. Perhaps a Dial indicator would solve the bed texture and reflection problem.

Really this is no different to a CNC machine where it measures the parts during machining.

Welcome opinions.

Yes that works. So I'll make the request for multi-line.

Any views on the object model enquiry?

@dc42
Thank you for reply.

I will make the suggestion. However before I do, I have been unable to get a single line message reporting variables. Have tried

M291 P "Camera X"^global.CameraX S2

The documentation does not describe anything other than P"message" with no example of variables.

Also I have an associated question.

I would like to find out what the current offsets I have applied via the G10 command are during the calibration.

As a test via the console I did
G10 P0 X-22
Then I move tool 0
G1 X40

Looking in the object model I find

move|axes|0|machine position 62
move|axes|0|userPosition 40
So I can deduce it believes offset is 40-62 = -22

Are the offets for all the tools visble in the object model specifically and without selecting the tool?

Having calibrated my four tool corexy I would like to report the offsets it has found.
I currently echo the variables by calling a macro

echo "Camera X",global.CameraX, " Y", global.CameraY, " Z",global.CameraZ
echo "T0Offset X",global.T0OffsetX," Y", global.T0OffsetY," Z",global.T0OffsetZ
echo "T1Offset X",global.T1OffsetX," Y", global.T1OffsetY," Z",global.T1OffsetZ
echo "T2Offset X",global.T2OffsetX," Y", global.T2OffsetY," Z",global.T2OffsetZ
echo "T3Offset X",global.T3OffsetX," Y", global.T3OffsetY," Z",global.T3OffsetZ

This results in the console
03/01/2024, 10:13:40 M98 P"0:/macros/Calibration/Report Offsets.g"
Camera X 6.577 Y 96.720 Z 0
T0Offset X 0 Y 0 Z 0
T1Offset X 0.060 Y 2.200 Z 0
T2Offset X 0.220 Y 3.620 Z 0
T3Offset X -0.043 Y 0.120 Z 0

However not all the lines are always reported. Sometimes T2 and T3 lines are missing. Why could this be?

What I would really like to do is report the variables with a Message dialog and require the user to Ok the message to continue. Like using a M291. However I have not found a way of reporting variables and putting them on multiple lines using M291.

Any suggestions?

@OwenD

Thanks for quick reply. Have got it working using echo.
I did see echo before but looked more verbose.

I have a four tool printer and wanting to automate calibration for xy offsets.
Have created a macro for global variable creation - That OK.
Have automated tools presented to a camera cross hairs - Jog to location and calculate offsets - Thats OK.
I can apply the offsets found using G10 command - Thats OK.

However I want to write the global variables to a file.g Then when the printed is powered up it executes the file and restores the offsets.

Whilst searching for solutions I find many posts make references to details in docuz which no longer seems to be supported. I have not found an example like the following...

So my macro to save the global variables is of the form

M28 "0:/macros/Calibration Values.g" ; Open file
set global.CameraX=(global.CameraX)
set global.CameraY=^{global.CameraY}
set global.CameraZ=global.CameraZ

set global.T0OffsetX={global.T0OffsetX}
set global.T0OffsetY={global.T0OffsetY}
set global.T0OffsetZ={global.T0OffsetZ}

....
M29 ; Close File

The file it makes is
set global.CameraX=(global.CameraX)
set global.CameraY=^{global.CameraY}
set global.CameraZ=global.CameraZ
set global.T0OffsetX={global.T0OffsetX}
set global.T0OffsetY={global.T0OffsetY}
set global.T0OffsetZ={global.T0OffsetZ}
set global.T1OffsetX={global.T1OffsetX}
set global.T1OffsetY={global.T1OffsetY}
set global.T1OffsetZ={global.T1OffsetZ}
set global.T2OffsetX={global.T2OffsetX}
set global.T2OffsetY={global.T2OffsetY}
set global.T2OffsetZ={global.T2OffsetZ}
set global.T3OffsetX={global.T3OffsetX}
set global.T3OffsetY={global.T3OffsetY}
set global.T3OffsetZ={global.T3OffsetZ}

As you can see I have tried various formats

So I am not getting the actual values into the file. I want it to be I believe of the form
set global.CameraX=6.54
set global.CameraY=96.740
set global.CameraZ=0
...
set global.T1OffsetX=0
set global.T1OffsetY=2.240
set global.T1OffsetZ=0.2

Running

Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.6 (2023-07-21)
Duet WiFi Server Version: 1.27

Thanks for any help

@jay_s_uk

Thanks for the guidance. All installed.

I am in the process of testing for input shaping.

Have wired accelerometer and get reported.

The documentation states Accelerometer plugin has been replace by Input Shaping plugin.

My machine is

Which appears the latest official release

However their is no input shaping files in the "Duet2and3Firmware-3.4.5.zip".

I have found InputShaping-3.4.1-b1.zip in " Duet3D / DSF-Plugins "

Where should this be put or can it simply be installed using upload system files.

Few more observations

Cannot define PWM Port for more than Fan#2 e.g. Duex.fan3 etc

Cannot define extruder drives D1, D2, D3

Typing in values for X or Y causes 'Enable Mesh Bed Compensation to be turned off"

Using Firefox

I'm using firefox on Windows 10 and not aware of using any add blockers.

I tried in on MS Edge and H3 is still missing,

@jay_s_uk You are correct. I have now fixed it. Much appreciated and thanks for your reply.

I am upgrading my machine from RepRap V2 to V3.

Most functions are operational. However on tools 1 to 3 the thermosatic fan on the hot end is not turning on when the hot end is heated. Tool 0 hot end fan works correctly.

I test by setting the hot end to 50C and expect the hot end fan to turn on. IT works on tool 0 but not 1-3.

I have created test macros to prove the fans are all configure correctly and can be turned on/off by the appropriate commands.

The temperature of the hot ends appears correct of PanelDue and DWS.

Board: Duet 2 WiFi (2WiFi)
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.5 (2022-11-30)
Duet WiFi Server Version: 1.23

Extract from config.g for Tool 1

; Tool 1 Heater
M308 S2 P"e1temp" Y"thermistor" T100000 B4138 C0 R4700 ; New temperature sensor allocation
M950 H2 C"e1heat" T2 ; Heater H2 uses Temperature Sensor T2
M143 H2 S270 ; Set temperature limit for heater 2 to 270C
M307 H2 R3.416 K0.391:0.401 D3.02 E1.35 S1.00 B0 V24.1 ; Set Tool 1 Heater 2 Tuned 03/07/2023

M950 F2 C"fan2" Q500 ; Part Cool Fan 2 to "fan2" PWM 500
M106 P2 S0 H-1 ; Set fan 2 (P2), H-1=Disable Thermostatic control. Will be Tool 1 Part Fan (M563)

M950 F3 C"duex.fan3" Q500 ; Hot End Fan 3 to "fan3" PWM 500
M106 P3 S1 H1 T45 ; Set fan 3, H1=Thermostatic controlled, T45=max temp 45C, Tool 1 Extruder Heastsink

Any suggestions if this is a configuration issue or something else.

Should I supply full config.g in this topic?

Thanks.

@jay_s_uk Actually the config.g generated does have the H3 present in the M950 and M307.

As you say not a problem.

I'm in the process of upgrading my firmware from RepRap firmware V2 to V3. Having a few problems so decided to use the Config Tool to see what it would produce. When defining the tools and associating a Heater, the Config Tool is not offering H3 which I want to allocate to Tool 2.

My machine is a four tool CoreXY.

I defined the Heaters 0 to 4.

However Heater 3 is not being offered in the Tool section.

GitHub suggests posting here before reporting bug.

That has resolved the issue.

Many thanks.