Posts made by ukflyer

If I had to guess I would say that it is almost as though the Web Server has shutdown rather than the WiFi connection.

Just started a print which is predicted to run for 2 hours plus so will keep an eye on it.

Not without issuing an M552 S-1 & M552 S1.

The logs are being taken from MacPronterface which is connected via USB

Suffered a disconnect during a print but print still running

Output of M122

m122
SENDING:M122
=== Diagnostics ===
Used output buffers: 2 of 32 (14 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.20beta11 running on Duet WiFi 1.0
Board ID: 08DGM-95BNL-MGPSN-6JKDJ-3S46N-1LWHW
Static ram used: 15488
Dynamic ram used: 97768
Recycled dynamiWiFi:
c ram: 1432
Stack ram used: 4328 current, 9212 maximum
NeWiFi: LINK
ver used ram: 7172
Last reset 18:45:25 ago, cause: power up
Last software reset reason: User, spinning module GCodes, available RAM 7400 bytes (slot 2)
Software reset code 0x0003, HFSR 0x00000000, CFWiFi: xmit: 0
SR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 1
[ERROR] Error status: 1

Free file entrieWiFi: recv: 0
s: 9
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 347.2ms
MCU temperature: min 36.8, current 42.3, max 42.6
Supply voltaWiFi: fw: 0
ge: min 11.5, current 12.5, max 13.1, under voltage events: 1, over voltage events: 0
Driver 0: ok
Driver 1: ok
Driver 2: ok
DriverWiFi: drop: 0
3: standstill
Driver 4: standstill
Date/time: 2017-12-03 15:10:06
Cache data hit count 4294967295
Slowest main loop (secondsWiFi: chkerr: 0
0.349178; fastest: 0.000040
=== Move ===
MaxReps: 5, StepErrors: 0, FreeDm: 163, MinFreeDm 137, MaxWait: 50818999ms, Underruns: 11, 1
Scheduled moves: 157311, completed moves: 157281
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.0WiFi: lenerr: 0
00 0.000
=== Heat ===
Bed heater = 0, chamber hWiFi: memerr: 0
eater = -1
Heater 0 is on, I-accum = 0.0
Heater 1 is on, I-accum = 0.4
=== GCodes ===
Segments left: 1
Stack records: 2 allocated, 0 in use
Movement lock held by null
http is idle in state(s) 0
telnet is idle WiFi: rterr: 0
in state(s) 0
file is doing "G1 X47.277 Y63.098 F9000" in state(s) 0
serial isWiFi: proterr: 0
ready with "M122" 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 sWiFi: opterr: 0
tate is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi: err: 0
WiFi firmware version 1.20b10
WiFi MAC address a0:20:a6:2f:bb:fe
WiFi Vcc 3.43, reset reason Turned on by main processor
WiFi flash size 4194304, freWiFi: cachehit: 0
e heap 28904
WiFi IP address 192.168.1.15
WiFi signal strength -27dBm, reconnections 0, sleep mode modem
HTTP sessions: 1 of 8
Socket statWiFi:
es: 0 0 0 0 0 0 0 0
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
WiFi: ETHARP
WiFi: xmit: 4
WiFi: recv: 1637
WiFi: fw: 0
WiFi: drop: 1923
WiFi: chkerr: 0
WiFi: lenerr: 0
WiFi: memerr: 0
WiFi: rterr: 0
WiFi: proterr: 1923
WiFi: opterr: 0
WiFi: err: 0
WiFi: cachehit: 24039
WiFi:
WiFi: IP
WiFi: xmit: 24104
WiFi: recv: 36990
WiFi: fw: 0
WiFi: drop: 0
WiFi: chkerr: 0
WiFi: lenerr: 0
WiFi: memerr: 0
WiFi: rterr: 0
WiFi: proterr: 0
WiFi: opterr: 0
WiFi: err: 0
WiFi: cachehit: 0
WiFi:
WiFi: IGMP
WiFi: xmit: 7
WiFi: recv: 39
WiFi: drop: 0
WiFi: chkerr: 0
WiFi: lenerr: 0
WiFi: memerr: 0
WiFi: proterr: 0
WiFi: rx_v1: 0
WiFi: rx_group: 0
WiFi: rx_genet 17033
WiFi: recv: 33948
WiFi: fw: 0
WiFi: drop: 0
WiFi: chkerr: 0
WiFi: lenerr: 0
WiFi: memerr: 0
WiFi: rterr: 0
WiFi: proterr: 0
WiFi: opterr: 0
WiFi: err: 0
WiFi: cachehit: 0

Okay I have the recommended Beta's installed -

Firmware Name: RepRapFirmware for Duet WiFi
Firmware Electronics: Duet WiFi 1.0
Firmware Version: 1.20beta11 (2017-11-28)
WiFi Server Version: 1.20b10
Web Interface Version: 1.19

And I have MacPronterface, connected via a USB cable, monitoring the WiFi debugging messages - fingers crossed.

Been following this thread for a while now.

What is the current consensus for stable WiFi ?

I have updated to the latest stable firmware and server releases. My printer is 300mm from the WiFi router and there are no other WiFi networks available and yet the network connection is currently dropping within seconds of starting the printer up.

I have managed to start one print in the last 2 days before the WiFi connection dropped and that ran to completion so it can only be an issue with the WiFi module.

Really beginning to wish I had paid the extra for an ethernet electronics board

As you will see from the link the controller is mounted to the top of the laser module - SW-LD62 V2.0 - I haven't been able to find any data sheet for it unfortunately but I will continue looking.

I have laser safe acrylic sheets to create an enclosure and also the laser module was supplied with safety goggles.

Okay, I have a question regarding wiring lasers to the DuetWifi.

I have a 2500mW 12V laser which is switchable between TTL & PWM that I would like to attach to my DuetWifi.

The laser (https://www.aliexpress.com/item/445nm-2500mW-12V-Laser-Engraving-Machine-Dedicated-Laser-Module-wit-TTL-and-PWM-can-control-laser/32807063746.html?spm=a2g0s.9042311.0.0.uWmzee) has three wires which are labelled VCC (power line), GND and PWM (control laser power).
My question is how should this be wired to the Duet ?

I would prefer to use PWM to control the laser as this would allow me to use M106 Snnn & M107 to control the laser and its intensity.

I have spent hours googling but to no avail.

TIA.

Okay, I suppose I have to ask the question. What do you recommend to use as a bed levelling probe ?

Thanks for the advice, I will spend some time checking the trigger distance across the bed. The bed is a 6mm cast aluminium tooling plate with no fixings within the print area so I would expect it to give similar results across the whole surface.

Okay, I placed a 3mm aluminium plate on the front of the build plate during the mesh probing and then ran the calibration print. As expected the nozzle attempted to print 3mm off the original build plate at the front and then dropped down to the correct height at the rear of the plate.

So it appears that the probed mesh is being taken into account.

The sensor is mounted 32mm in front of the nozzle hence - G31 X0 Y-32 Z0.05

Is this too far ?

The probe returns the same map every time, unless I adjust the levelling screws in which case I see a change to the relevant area of the map.
I am currently using an LJ12A3-4-Z/BX 4mm Inductive Proximity Sensor Switch Detector DC6-36V (NPN - NO), this is being powered from E1 Heater VIN. I have a LJ12A3-4-Z/BY 4mm Inductive Proximity Sensor Switch Detector DC6-36V (PNP - NO) on order for a separate project which I will test once it arrives.

As requested the output of M122 is as follows

M122
=== Diagnostics ===
Used output buffers: 3 of 32 (13 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19 running on Duet WiFi 1.0
Board ID: 08DDM-9FAM2-LW4S4-6JTD8-3SJ6J-TMVZY
Static ram used: 21176
Dynamic ram used: 95912
Recycled dynamic ram: 1696
Stack ram used: 1304 current, 4912 maximum
Never used ram: 7376
Last reset 00:09:15 ago, cause: power up
Last software reset reason: User, spinning module GCodes, available RAM 7440 bytes (slot 2)
Software reset code 0x0003, HFSR 0x00000000, CFSR 0x00000000, ICSR 0x00400000, BFAR 0xe000ed38, SP 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms
MCU temperature: min 41.4, current 41.8, max 42.1
Supply voltage: min 11.5, current 11.9, max 12.2, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: stalled standstill
Driver 3: standstill
Driver 4: standstill
Date/time: 2017-10-26 09:42:43
Slowest main loop (seconds): 0.014099; fastest: 0.000061
=== Move ===
MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 146, completed moves: 146
Bed compensation in use: mesh
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heater = 0, chamber heater = -1
Heater 1 is on, I-accum = 0.4
=== 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 state is running
WiFi module is connected to access point
WiFi firmware version 1.19
WiFi MAC address 2c:3a:e8:0b:11:8b
WiFi Vcc 3.15, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39168
WiFi IP address 192.168.1.15
WiFi signal strength -27dBm
HTTP sessions: 1 of 8
Socket states: 2 0 0 0 0 0 0 0
Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)

It appears as though the probe heights are not being recorded despite this output from the MeshLevel macro

M98 P0:/macros/MeshLevel
42 points probed, mean error 0.029, deviation 0.022
Height map saved to file heightmap.csv
Height map saved to file heightmap.csv

I have an inductive probe which is being used to detect a cast aluminium tooling plate. I am using a Duet WiFi with the following probe configuration

M558 P5 X0 Y0 Z1 I1 H5 F120 T6000
G31 X0 Y-32 Z0.05

I have a MeshLevel macro defined as follows

M557 X0:115 Y0:93 S18 ; Define mesh grid

G28 Y ; Home Y axis
G28 X ; Home X, always before Z
G28 Z ; Home Z

G29 S0 ; Run probing sequence

M374 ; Save calibration data

G1 X10 Y10 F3000

Which when run generates the following height map.csv

RepRapFirmware height map file v2 generated at 2017-09-25 12:20, mean error 0.027, deviation 0.022
xmin,xmax,ymin,ymax,radius,xspacing,yspacing,xnum,ynum
0.00,115.00,0.00,93.00,-1.00,18.00,18.00,7,6
-0.006, 0.011, 0.038, 0.051, 0.064, 0.051, 0.055
-0.002, 0.016, 0.029, 0.059, 0.064, 0.046, 0.051
0.011, 0.016, 0.033, 0.055, 0.059, 0.042, 0.033
-0.002, 0.007, 0.029, 0.051, 0.055, 0.033, 0.024
0.003, -0.002, 0.016, 0.029, 0.038, 0.024, 0.011
0.003, -0.002, 0.003, 0.029, 0.024, 0.003, -0.011

But when I print a simple bed calibration test I get the following