In a previous life, I was the admin of a large computer network. One of the best features of the Cisco gear we used was the command "show tech-support". It spits out a huge text file with the entire configuration of the device, along with a number of diagnostic command outputs, error and operation logs, component temperatures, version info, etc.
The file could either be used in-place for diagnostics or sent to Cisco tech support for further analysis, sidestepping a lot of back-and-forth with the support people.
It occurred to me that it would not be that hard to achieve something similar, either implemented in firmware or else done in DWC. That file, uploaded to the forum (perhaps via an automated mechanism direct from DWC?) would provide a huge amount of troubleshooting data very easily.
Even better would be a way to unpack that data into a visualiser/validator tool that showed common issues, potential conflicts, firmware upgrade 'gotchas', etc. Again, this is something we had with Cisco where complex configurations led to difficult-to-spot and subtle issues. I appreciate that this is not trivial to implement but it wouldn't have to happen all at once and, once done, might actually cut down on the time spent troubleshooting, especially with 'new user'-type issues.
Moin, I just grilled my Duet TC daughterboard by shortening it with the hotend pin. In order to still print some christmas presents in time, I would like to replace it with an Adafruit Max 31856 that I have at hand. Iam using at DuetWifi in combination with a Duex5 so I guess it can only be connected to the TC daughterboard pins, correct? If so, GND should go to pin 2: GND, Vin to pin 8: 3,3V, SCK to pin 4:SPIO_SCK, SDO to pin 5: SPIO_MOSI, SDI to pin 6: SPIO_MISO and CS to pin 1: CS6 (or any other CS pin in case i want to stack them?), right?
@spax said in Error: Heating fault on heater 0. + Bad Temperature Chart.:
M305 P0 T100000 B3950 R4700 H30 L0
Solved! I delete H30 L0 and now all work well.....hmm...I don't even remember where it came from.
@dc42 I just got this error also,
The connection between the browser and your machine has been interrupted.
Reason: Request Timeout
Please wait while a new connection is being established...
it then reconnects, the printer was just sitting there idling, I had homed the XYZ axis but nothing else. Just sitting there looking at the DWC. Looking over the M122 I am going to assume my wifi connection is very poor?
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02RC5(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-956GU-DJ3SN-6J1FA-3SD6Q-KURMG
Used output buffers: 3 of 20 (15 max)
=== RTOS ===
Static ram: 27284
Dynamic ram: 98488 of which 0 recycled
Exception stack ram used: 376
Never used ram: 4924
Tasks: NETWORK(ready,328) HEAT(blocked,1232) MAIN(running,3596) IDLE(ready,200)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:15:10 ago, cause: power up
Last software reset at 2018-12-11 23:23, reason: User, spinning module GCodes, available RAM 4908 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 34.5, current 34.6, max 34.7
Supply voltage: min 12.2, current 12.3, max 12.4, 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
Date/time: 2018-12-17 23:45:20
Cache data hit count 3375536241
Slowest loop: 1.10ms; fastest: 0.08ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 9, completed moves: 9
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -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 ===
Slowest loop: 157.72ms; fastest: 0.08ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
Network state is running
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.21RC4(08b3)
WiFi MAC address 5c:cf:7f:76:67:2f
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 15296
WiFi IP address 10.51.108.101
WiFi signal strength -73dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
Sorry I was at job I checked connection now at home and find the problem I made mistake and i connected that by old diagram.. (Prototype V2) So I really fed output to 3.3V.... could I somehow save my card???
@lui2004 said in Changed from anet Board to duet3d wifi:
I have it on front left x=0 y=0
Also now only Settings to do is in S3D?
If your printer moves by the correct amount (i.e. 100mm movement commanded in Duet Web Control causes the nozzle to move by 100mm), then you just need to configure S3D to centre the models at bed centre. However if your S3D profile worked before you upgraded the controller to a Duet, then you shouldn't need to change it.
If the movement amounts are not correct, you need to correct your steps/mm in the M92 command in config.g.