@dc42 got it thank you
Latest posts made by unstableTable
-
RE: Unresponsive board, DIAG lit, next steps?
@jay_s_uk Hey Hey! The USB hub solved it! A new BOSSA COM port open in YAT.
Continue in YAT as per usual set up for a new wireless network? -
Unresponsive board, DIAG lit, next steps?
Hello all,
I have a Duet 2 WiFi V1.04 (no erase button), unknown firmware on an Ender 3 [V1] Pro.
It ran great until I moved and tried to connect to a new wireless network.I tried to connect via YAT under USB power only. No luck.
I checked Device Manager on two Windows laptops and the board did not appear anywhere
I found/followed the above link
The lights on board were: 5v, 3.3v, & red light b/t rest button and USB. The DIAG light lit up ~0.5sec then remained off
I jumpered the erase pins (no erase button), applied USB power (few sec, per the link) then removed USB power & jumper
I applied USB power lights are same, plus DIAG light now remains on
USB inserted I checked Device Manager and got "device descriptor request failed" (code 43)
Board still unresponsive, I even tried with/out SD card inserted. I bought through Filastruder two years ago so I am likely outside my warranty.How can I save her?
Thanks! *smiles in noob -
RE: HTTP timeout from laptop but not phone/tablet
Thanks, I will try that as soon as I get back home. I appreciate the help!
-
HTTP timeout from laptop but not phone/tablet
Hi, thanks for letting me be part of this community.
Problem:
HTTP request has timed out, occurs only on my Macbook. Works fine from smartphones and tablets. I'm not sure how to proceed and I would appreciate any help, thanks!M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DGM-9T6BU-FG3S0-7JKF0-3S46Q-KU47D
Used output buffers: 3 of 20 (14 max)
=== RTOS ===
Static ram: 28380
Dynamic ram: 95864 of which 0 recycled
Exception stack ram used: 348
Never used ram: 6480
Task NETWORK ready, free stack 324
Task HEAT blocked, free stack 1256
Task MAIN running, free stack 3568
=== Platform ===
Last reset 00:04:56 ago, cause: power up
Last software reset at 2019-04-08 18:50, reason: User, spinning module GCodes, available RAM 6440 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, 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 33.7, current 33.7, max 34.0
Supply voltage: min 24.3, current 24.4, max 24.4, under voltage events: 0, over voltage events: 0
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: 2019-04-08 21:36:37
Slowest loop: 181.61ms; fastest: 0.08ms
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 7, completed moves: 7
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: 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: 4.40ms; fastest: 0.01ms
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 175, notready 0, noresp 0
WiFi firmware version 1.21
WiFi MAC address 84:f3:eb:83:32:f4
WiFi Vcc 3.39, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 14224
WiFi IP address 192.168.1.105
WiFi signal strength -34dBm, reconnections 0, sleep mode modem
Socket states: 0 0 0 0 0 0 0 0
=== Expansion ===
confitg.g
; Configuration file for Duet WiFi (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Thu Sep 06 2018 21:21:12 GMT-0700 (Pacific Daylight Time); General preferences
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves; Network
M550 Pe3 ; Set machine name
M552 S1 ; Enable network
;*** Access point is configured manually via M587
M586 P0 S1 ; Enable HTTP
M586 P1 S0 ; Disable FTP
M586 P2 S0 ; Disable Telnet; Drives
M569 P0 S0 ; Drive 0 goes backwards
M569 P1 S0 ; Drive 1 goes backwards
M569 P2 S1 ; Drive 2 goes forwards
M569 P3 S0 ; Drive 3 goes backwards
M350 X16 Y16 Z16 E16 I1 ; Configure microstepping with interpolation
M92 X80 Y80 Z400 E95 ; Set steps per mm
M566 X600 Y600 Z24 E300 ; Set maximum instantaneous speed changes (mm/min) was 1200 you changed it to 600
M203 X30000 Y30000 Z300 E1500 ; Set maximum speeds (mm/min)
M201 X300 Y300 Z100 E5000 ; Set accelerations (mm/s^2) was 500 you changed it to 300 for stall guard
M906 X500 Y500 Z500 E500 I30 ; Set motor currents (mA) and motor idle factor in per cent
M84 S300 ; Set idle timeout; Axis Limits
M208 X-5.5 Y-10 Z0 S1 ; Set axis minima
M208 X258.5 Y246 Z260 S0 ; Set axis maxima; Endstops
M574 X1 Y1 S1 ; Set active high endstops; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
M307 H3 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M307 H4 A-1 C-1 D-1 ; Disable heater on PWM channel for BLTouch
M558 P9 H2.5 F120 T6000 ; Set Z probe type to bltouch and the dive height + speeds
G31 P25 X-31 Y0 Z.6 ; Set Z probe trigger value, offset and trigger height
M557 X50:185 Y50:185 S65 ; Define mesh grid M557 X20:215 Y20:215 S65; Heaters
M305 P0 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 0
M143 H0 S120 ; Set temperature limit for heater 0 to 120C
M305 P1 T100000 B4138 C0 R4700 ; Set thermistor + ADC parameters for heater 1
M143 H1 S280 ; Set temperature limit for heater 1 to 280C; Fans
M106 P0 S0 I0 F500 H-1 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H0 T45 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S0 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on; Tools
M563 P0 D0 H1 ; Define tool 0
G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C; Automatic power saving
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss; Custom settings
;M591 D0 P5 C3 R10:300 E3.0 S1 ; Duet3D laser sensor for extruder drive 0 is connected to endstop input 3 (E0), tolerance ;10 to 120%, 3mm comparison length - WiFi -
-
RE: Extruder 0 reports too little movement
@dc42 I am not using a filament monitor of any kind. But I suspect that I have improperly wired the board.
I can get all 3 axes to home properly.
Nozzle and bed get to proper temp.Any print stops within 2 min and "Extruder 0 reports too little movement"
-
Extruder 0 reports too little movement
New install on Ender 3, obvious under extrusion on the bed. Tried keeping extrusion clip very loose on the extruder thinking it was a failure to feed filament.
If it's a firmware tuning issue then I'm not sure where to start?