Z map with no probe

AZERATE

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.05.1 running on Duet WiFi 1.02 or later + DueX5
Board ID: 0JD0M-9P6M2-NW4SN-6JKD2-3SD6Q-9VTML
Used output buffers: 3 of 24 (7 max)
=== RTOS ===
Static ram: 25712
Dynamic ram: 93684 of which 0 recycled
Exception stack ram used: 320
Never used ram: 11356
Tasks: NETWORK(ready,628) HEAT(blocked,1232) DUEX(suspended,160) MAIN(running,3800) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:28:45 ago, cause: power up
Last software reset at 2021-11-24 18:50, reason: User, spinning module GCodes, available RAM 11284 bytes (slot 3)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 28.7, current 30.4, max 31.5
Supply voltage: min 12.0, current 12.2, max 12.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available
Driver 5: standstill, SG min/max not available
Driver 6: standstill, SG min/max not available
Driver 7: standstill, SG min/max not available
Driver 8: standstill, SG min/max not available
Driver 9: standstill, SG min/max not available
Date/time: 2021-11-25 11:39:12
Cache data hit count 4294967295
Slowest loop: 5.59ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle in state(s) 0
file is idle in state(s) 0
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.75ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
- WiFi -
Network state is running
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.23
WiFi MAC address 84:0d:8e:b3:02:04
WiFi Vcc 3.42, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 21728
WiFi IP address 192.168.0.5
WiFi signal strength -42dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0

Also, thank you very much Ian

AZERATE

@phaedrux
I'm sorry, Settings>General>Plugins there is a Height Map plugin. Also on the PanelDue, if I hit the little wavy icon just above Macro, it homes everything and starts to move like it wants to start mapping with the probe. I've just gone through all *.g files and deleted everything related to G30, so now it doesn't start trying to map with a non-existent probe, but I still can't move Z any further than 5mm past homed.

droftarts

@azerate after removing the G30, you don’t have any Gcode homing the Z axis. You need a G1 H1 Z… move towards your Z micro switch.

Ian

Phaedrux

@azerate said in Z map with no probe:

if I hit the little wavy icon just above Macro,

That button would be running bed.g which would explain what you're seeing.

AZERATE

@droftarts
Thanks a lot for the help. This is what I show in homez.g
So where should I put G1 H1 Z?0?
Sorry. Like I said, I'm great with the mechanical build, but I'm terrible with anything firmware related.

;; Use relative coordinates.
G91

;; Move Z down 10 mm and obey max limit switch.
G1 Z10 F240 S1

;; Use absolute coordinates.
G90





;; Move Z to nozzle.
G1 Z0 F200

Phaedrux

See some examples here: https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Homing_files

AZERATE

@phaedrux
Perfect. That solves the no-probe issue.
But I still can't move the Z motors. Any ideas?

Phaedrux

With the print head place safely away from the bed, send these commands to test movement

G92 Z10
G91
G1 Z5 F100

That should cause some z motor movement. If not, please post your config.g.

This may also be a good time to think about upgrading your firmware from RRF2 to RRF3 before you get too far along.

AZERATE

@phaedrux

No movement from any of the commands. here's my config.g

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Communications
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

;; Disable debugging output.
M111 S0

;; Machine name, which will be displayed on the LCD screen. Please note that
;; this setting does not change the name of your printer as seen by your WiFi
;; router, as this setting is stored on the WiFi chip.
M550 PIcarus

;; Set the IP address of the printer. '0.0.0.0' means the printer should use
;; the DHCP server on your WiFi router to get an IP address. In most cases,
;; this will work without any trouble. If this does not work and you do not
;; have control over the network you are trying to use, contact your system
;; administrator for assistance.
M552 P0.0.0.0                  	                 	

;; Set the netmask. '255.255.255.0' is the correct setting for most cases.
;; If this doesn't work for you and you don't have control of your network,
;; contact your system administrator for assistance. 
M553 P255.255.255.0                

;; Use Marlin-like output for GCode responses. If you use an alternative host
;; to control your Horizon H1, select "Marlin" for the firmware type.
M555 P2

;; For LCD Screen (PanelDue): Require checksums (S1) and set the serial port
;; to 57600 baud.
M575 P1 B57600 S1

;; Set the password for all external interfaces into the machine such as the
;; web interface, telnet, etc. The default password is "printit". To override,
;; issue M551 P<your password without spaces or special characters> and then
;; issue M500 to save your changes.
M551 Pprintit

;; Enable the WiFi chip on the board. This command will cause the WiFi chip
;; to connect to its configured network (if set and the network is responsive). 
;; If the network cannot be reached or no network has been
;; configured yet, this command will create a WiFi hotspot
;; named "Duet Wifi." You can connect to this access point 
;; and configure your Horizon H1. After connecting to the "Duet WiFi" network, 
;; go to http://192.168.1.1 and follow the instructions.
M552 S1

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Motion configuration 
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;


;; Configure drive mapping for Z. Z uses four stepper motors moving together,
;; connected to drives 5, 6, 7 and 8 on the Duex2 expansion board.
;; In clockwise order from the front of the machine, drive 5 is the back right
;; motor, 6 is the front right motor, 7 is the front left motor and 8 is the
;; back left motor.
M584 Z5:6:7:8

;; Endstop configuration.
;; We home the machine at X,Y min (X1 Y1) using mechanical endstops.
;; Z has a max endstop (Z1).
;; We use normally-closed switches (S1).
M574 X1 Y1 Z1 S1

;; Obey build volume dimensions by default.
M564 S1

;; Set units to millimeters.
G21                                 

;; Use absolute coordinates.
G90              	

;; Set minimum travel (S1) for each axis.
;; (-22.5, 0, 0) is the homing position for the Horizon H1.
M208 X0 Y0 Z0 S1

;; Set the build volume to 355 mm x 240 mm x 248 mm.
M208 X255 Y240 Z177

;; Set drive directions. All steppers are connected to the board in the same
;; orientation at the factory. The firmware defines the proper step direction
;; for each motor.

;; X motor goes forward
M569 P0 S1	

;; Y motor goes backward
M569 P1 S0
			
;; Z motor goes forward
M569 P2 S1

;; Extruder (E0) motor goes forward
M569 P3 S0

;; Set motor currents for X, Y, Z and extruder (E0) in milliamps.
;; We use a 100% idle current (I1) so that the motors remain locked once 
;; enabled.
;; We set Z separately from the rest to ensure it is set correctly despite our
;; mapping of the Z drives.
M906 X1400 Y1400 E950 I100
M906 Z1400

;; Define steps per millimeter for X, Y Z and extruder (E0). 
M92 X80 Y80 Z160 E277.6

;; Set acceleration in mm/s^2 for X, Y Z and extruder (E0). 
M201 X5000 Y5000 Z2000 E10000

;; Set the maximum speed in mm/min for X, Y, Z and extruder (E0).
;; X, Y at 30000 mm/min = 500 mm/s
;; Z at 240 mm/min = 4 mm/s
;; E at 2000 mm/min = 33 mm/s
M203 X30000 Y30000 Z2000 E2000

;; Set the maximum standing start ("jerk") speed in mm/min for X, Y, Z and
;; extruder (E0).
;; X, Y at 1800 mm/min = 30 mm/s
;; Z at 150 mm/min = 2.5 mm/s
;; E at 30 mm/min = 0.5 mm/s
M566 X1800 Y1800 Z150 E30


;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;; Heater and Thermistor Configuration
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

;; Set the maximum HotEnd temperature to 290C. 
;; Reaching 300C or above WILL damage the thermistor in your E3D v6!
M143 S290

;; Bed thermistor configuration for the Cantherm MF52A1104F4150 thermistor
;; on Calidum HALE 8" x 8" 12v heat bed.
;; Datasheet URL: http://www.cantherm.com/media/productPDF/cantherm_mf52_1.pdf
M305 P0 T100000 B4150 R4700 H0 L0

;; Extruders (E0) - E3D v6 thermistor configuration for the Semitec 
;; 104GT-2 thermistor.
;; Datasheet URL: http://www.atcsemitec.co.uk/gt-2-glass-thermistors.html
;; E3D Wiki page listing the recommended B and C values:
;;      https://wiki.e3d-online.com/wiki/E3D-v6_Assembly
M305 P1 T100000 B4725 C7.06e-8 R4700 H0 L0

;; Give extruder 3 minutes to reach the target temperature. If it does not,
;; trigger a heater fault (cancel all heating).
M570 S180

;;Extruder (E0) uses drive 0, heater 1.
M563 P0 D0 H1


;; Extruder uses 1.75 mm filament and a 0.6 mm nozzle stock.
M404 N1.75 D0.6

;; Set heating process parameters for the Calidum HALE 8" x 8" 12v
;; Retrieved using the following commands:
;;      M303 H0 S100
;;      M307 H0
M307 H0 A139.8 C516.6 D7.7 S1.00 B0 ; B0 disables bang-bang

;; Set heating process parameters for the E3D v6 12v
;; Retrieved using the following commands:
;;      M106 S255
;;      M303 H1 S245
;;      M307 H1
M307 H1 A438.8 C154.1 D6.0 S1.00 B0 ; B0 disables bang-bang
M307 H2 A438.8 C154.1 D6.0 S1.00 B0 ; B0 disables bang-bang

;; Operate fan 1 in thermostatic mode, activating when the extruders 
;; (E0) get at or above 45C.
M106 P1 T45 H1

;; Set bed and HotEnd active/standby temperatures to zero, and
;; configure nozzle offsets. P0 is the left nozzle, and P1 is the right
;; nozzle, corresponding to extruder drives E0 and E1.
M140 S0
G10 P0 S0 R0 X9 Y-9

;;Activate tool 0 (E0), as it is the only extruder on the machine
T0

;; Load additional settings from config-override.g, if it exists. You should
;; use config-override.g to change settings, instead of altering this file.
M501

fcwilt

@azerate

Your comment for the M584 command says you are using a Duex 2 board - is that correct? If it is you cannot connect 4 steppers.

I think you should update your config file by:

adding X and Y to your M584 command
adding a M350 command

Frederick

AZERATE

@fcwilt
That is correct. I suppose I should go down the list real quick.
Duet Wifi (bought less than a year ago)
Duex to expand for 4 Z motors
PanelDue 7i

I'm basically finishing the build from another printer that uses the same electronics, and have just been modifying the files piece by piece to make it reflect this particular machine (e.g. this machine is a single extruder, non-Core XY, no probe, etc.) Hope that clears it up a little.

fcwilt

@azerate

Did you modify the Duex 2 in some way to support 4 steppers?

Frederick

AZERATE

@fcwilt

No. I simply copied the files from the other printer with Quad Z and uploaded to this machine, then tweaked as I went.

droftarts

@fcwilt where are you getting Duex 2 from? His M122 says Duex 5.

Ian

Phaedrux

If you're willing to take the plunge to RRF3 now might be the ideal time to do, though it would mean starting with a fresh config file set. Though you'd be able to generate a good starting base to work from with the online config tool.

If you still have access to DWC. Upload these 3 zip files, one at a time in the system tab. Don't extract them first. Reboot after each. Use M115 in the gcode console 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.3/Duet2and3Firmware-3.3.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

Backup your existing config files in the sys folder in case you want to switch back to RRF2. 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

fcwilt

@droftarts said in Z map with no probe:

@fcwilt where are you getting Duex 2 from? His M122 says Duex 5.

Ian

I didn't see the output from M122. His config file comments mentioned Duex 2 and I asked him to verify if that was true. He said it was. I guess he was confused.

Frederick

AZERATE

I want to thank you all very much. I ended up deleting everything related to probe and G30 and now while Z motion homes rrrreeeaaallllyyyyy slow, I was able to make some calibration prints to dial in the machine.

This is a great community and I appreciate you time!