m sorry you lost your print. Were you adjusting the speed factor from DWC, PanelDue, or some other input?

Quote Answer Report

I was using DWC to increase the speed 10% faster. The other strange thing that it has done since there 1.19 upgrade, is when I make a change to the config.g file, it asked if I want to reboot, when I do, I get a Ajax error and I have to reconnect. It really isn't an issue, but just something new.

i was about 3hrs in a print job, when i made an adjustment to the speed factor. at that moment, i was shown a message that the emergency stop had been activated. here is the m122 file
, i am still running 1.19.2 because it seemed like the newer versions were plagued with reset, disconnects, and ajax problems. Do i need to bite the bullet and upgrade to the latest and greatest versions

M122
=== Diagnostics ===
Used output buffers: 3 of 32 (5 max)
=== Platform ===
RepRapFirmware for Duet WiFi version 1.19.2 running on Duet WiFi 1.0
Board ID: 08DAM-9K9K2-NGNS0-7JTD2-3S46M-KP2RJ
Static ram used: 21176
Dynamic ram used: 96032
Recycled dynamic ram: 1576
Stack ram used: 1304 current, 4880 maximum
Never used ram: 7408
Last reset 00:00:53 ago, cause: software
Last software reset reason: User, spinning module GCodes, available RAM 3192 bytes (slot 4)
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 44.0, current 45.1, max 45.6
Supply voltage: min 12.4, current 12.5, max 12.6, under voltage events: 0, over voltage events: 0
Driver 0: stalled standstill
Driver 1: stalled standstill
Driver 2: standstill
Driver 3: stalled standstill
Driver 4: standstill
Date/time: 2017-12-06 10:27:05
Slowest main loop (seconds): 0.005385; fastest: 0.000034
=== Move ===
MaxReps: 0, StepErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heater = -1, chamber heater = -1
=== GCodes ===
Segments left: 0
Stack records: 1 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.2
WiFi MAC address 5c:cf:7f:f7:de:c3
WiFi Vcc 3.16, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 39616
WiFi IP address 10.0.0.61
WiFi signal strength -50dBm
Reconnections 0
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 would be nice to have a simple way to zero Z, by placing the nozzle to the build surface or the paper test, then enter a g code and have it set the z height in config.g.

This might be where the confusion comes from. Coyote Delta is the machine name and reprap the password set in the config.g file, which is what I used to set up the SetNetwork macro, is this wrong?

with the number of people having problems with network communications after upgrades, i would think that there is a problem somewhere in the instructions, possibly assumptions that we know everything. it appears that step one of loading the Duet Web Control can be done with DWC, but nowhere do i see a place to replace the /www folder, so i remove the SD card and replace and rename the files accordingly. i then send the M997 S0:1, which downloads fine, but i have to reboot the duet wifi module, after that everything works fine until i try to get the access point.

m98 p/macros/setnetwork
SENDING:M98 P/MACROS/SETNETWORK
WiFi module started
m587
SENDING:M587
Remembered networks:
Coyote Delta
COYOTE DELTA
m552 s1
SENDING:M552 S1
WiFi reported error: no known networks found
Wifi module is idle

i dont know what i am missing, i have tried this procedure several times including a m997 s0 then a m997 s1. if i try the update firmware button and the DWC it losese connection right after the firmware finishes updating.
as soon as i revert back to1.18, everything works fine. Could you rewrite the procedure a with a little more detail involved and include what to do if a certain step does not work. It would probably save you a lot of time having to answer all of the thread regarding network connection issues.

i have also noticed some inconstancy with my ir probe. I have a large format delta, using duet wifi, with a glass bed. I have tried sand blasting the backside of the glass, along with various colored paper glued to the back.
I noticed that my probe points vary .2 to .4 mm in the same spot. and my calibration factors are all over the place every time a run a auto calibration i have also noticed that the value given on the DWC is very erratic at some heights, and almost none responsive at others. When lower the probe close to the surface, i will start getting erratic reading 180 and 300, as i bring it even closer it will go back to 0. as i step it closer, it will eventually jump to 466 at about 2mm above the bed and stay there as i continue to bring it down, it will then switch to 535 and turn the red led on and stay a that reading until it is at Z0. i have M558 set to mode 1, i get 4 led flashes when it powers up. both emitters are producing a light when viewed threw a camera and my power is 3.3v ground is 0 and the sensor voltage is also erratic when slowly bringing it close to an object.
is this normal, or bad sensor. Its only 2 months old.