I didn't, DC42. That must be it. Thanks much (and enjoy your holiday)!
Posts made by tonydacrow
-
RE: Question re: Expansion Board Error
-
RE: Question re: Expansion Board Error
Thanks for the info, Snowcrash!
-
Question re: Expansion Board Error
Quick question for those of you in the know. I bought an expansion board for my WiFi to add additional extruders and just hooked it up w/ the supplied ribbon cable. When I turn on the machine, I get an error stating the additional drives on the expansion board are "shorted" and in "over temperature." Is this normal? Will I get this error until I actually hook-up extruders or is there something wrong?
Thanks in advance!
-
RE: WIFI Access Denied!
Mystery (Apparently) Solved.
First a big thank you, as always, to DC42 for such great support!
I believe the problem was with a Windows 10 update. This morning, I noticed that the machine had recently updated so I uninstalled/reinstalled the update. Everything is now working fine. Just one of those things we (or I) don't normally check. So, lesson learned.
-
RE: 60000mm/sec (1m/sec) 3D printer
@kulitorum said in 60000mm/sec (1m/sec) 3D printer:
xpected speed at 300mm/sec. We'll see what the c
Impressive!
-
RE: WIFI Access Denied!
Some additional information:
I just remembered that for the past few days, my Duet WiFi has been randomly disconnecting several times during various printing sessions. The print continued, but the connection was lost several times and I had to manually reconnect. Bad WiFi module?
-
WIFI Access Denied!
Here's hoping for a simple fix. When I tried to start my Duet WiFi printer today, the computer couldn't find the http I use for my printer. When I plugged my Duet into the computer via USB and started YAT to see if I just needed to turn on WiFi again, I got the following message for the com port on which I have the Duet:
**Terminal Error
Unable to start terminal!
System error message (System.UnauthorizedAccessException):
Access to the port 'COM6' is denied.YAT Hints:
Make sure the selected serial COM port is available and not already in use. Also, check the communication settings and keep in mind that hardware and driver may limit the allowed settings.**I get the same error message regardless of which COM port I use. I'm assuming it's a problem with the WiFi module. Any help would be appreciated!
Thanks in advance,
Tony -
RE: Corexy 3 lead screws problem with height
I had a similar issue and it turned-out one of the Z-motors was going bad. Just a thought...
-
RE: Newb Configuration Problems
All axes homed and on to tuning. THANK YOU ALL!
-
RE: Newb Configuration Problems
@stealthy_tt said in Newb Configuration Problems:
ove them, but when I installed mine i got the same thing
Much appreciated, all! I'll give it a try.
-
Newb Configuration Problems
Greetings, all. Request for help configuring.
I have my shiny new WiFi Duet connected and ready to power my Tronxy X5S CoreXY. I'm going through the Duet3D tutorial #3 on Configuration and get to step 12 (configure endstops) with no problem. At step 13 (Check Stepper Motors) I get the following error message when I try to move X,Y or Z axes 1mm:
! M120
G91
G1 X0.1 F6000
M121
Error: G0/G1: insufficient axes homed
Error: POP(): stack underflowI know I'm doing something wrong, but don't know what. Any help is GREATLY appreciated.
Thanks,
Tony -
RE: New Board Can't Connect to Wi-Fi.
Huzzah! That was the issue; a silly little apostrophe in the network name. My Duet Wifi is now connected to my network.
A big THANK YOU to all who helped, but especially to you dc42 for you patience and generosity with this issue!
-
RE: New Board Can't Connect to Wi-Fi.
Sadly, still no joy.
I updated both firmware and wifi drivers to 1.21.
When I run M122, I get:
m122
=== Diagnostics ===
Used output buffers: 1 of 32 (8 max)
=== Platform ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4S4-6J1DA-3S46R-K3TZW
Static ram used: 16152
Dynamic ram used: 100800
Recycled dynamic ram: 1832
Stack ram used: 3576 current, 4900 maximum
Never used ram: 7388
Last reset 00:17:35 ago, cause: power up
Last software reset details not available
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 31.8, current 35.3, max 35.4
Supply voltage: min 1.6, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Slowest main loop (seconds): 0.100089; fastest: 0.000041
=== Move ===
MaxReps: 0, StepErrors: 0, LaErrors: 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 heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== 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 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 ===
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8- WiFi -
Network state is running
WiFi module is idle
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.21
WiFi MAC address 60:01:94:73:5b:4b
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 19808
Socket states: 0 0 0 0 0 0 0 0
=== Expansion ===
ok
When I run M587, I get:
m587
Remembered networks:
TNCAP2FCC19 IP=192.168.1.14 GW=0.0.0.0 NM=0.0.0.0
MY NETWORK NAME IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
your=network-MY NETWORK NAME IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
your-network-MY NETWORK NAME IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
MY NETWORK NAME IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0
MY NETWORK NAME IP=0.0.0.0 GW=0.0.0.0 NM=0.0.0.0Yet, when I run the M552 S1 after setting-up the network with the M587 S"MY NETWORK NAME" P"MY PASSWORD" command, I get:
m552 s1
ok
WiFi reported error: no known networks found
WiFi module is idleok
My wifi network has an apostrophe in its name. Perhaps that could that be the problem? Any additional thoughts? At this point I'm close to stumped…
- WiFi -
-
RE: New Board Can't Connect to Wi-Fi.
Here is the command response in proper format:
ok
m122 <cr>=== Diagnostics ===
Used output buffers: 1 of 32 (9 max)
=== Platform ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4S4-6J1DA-3S46R-K3TZW
Static ram used: 16152
Dynamic ram used: 100800
Recycled dynamic ram: 1832
Stack ram used: 3576 current, 4584 maximum
Never used ram: 7704
Last reset 00:01:29 ago, cause: power up
Last software reset details not available
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 26.5, current 27.2, max 27.2
Supply voltage: min 1.6, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 1970-01-01 00:00:00
Slowest main loop (seconds): 0.004284; fastest: 0.000042
=== Move ===
MaxReps: 0, StepErrors: 0, LaErrors: 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 heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== 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 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 ===
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8- WiFi -
Network state is running
WiFi module is idle
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.19.2
WiFi MAC address 60:01:94:73:5b:4b
WiFi Vcc 3.08, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 40544
Socket states: 0 0 0 0 0 0 0 0
=== Expansion ===
ok</cr>
- WiFi -
-
RE: New Board Can't Connect to Wi-Fi.
I noticed that in my last post, I exceeded the number of bytes per line which truncated the command reply. Here is the full display with the M122 command:
m122
=== Diagnostics ===<lf>Used output buffers: 1 of 32 (1 max)<lf>=== Platform ===<lf>RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later<lf>Board ID: 08DDM-9FAM2-LW4S4-6J1DA-3S46R-K3TZW<lf>Static ram used: 16152<lf>Dynamic ram used: 100600<lf>Recycled dynamic ram: 2032<lf>Stack ram used: 3576 current, 4420 maximum<lf>Never used ram: 7868<lf>Last reset 00:02:09 ago, cause: power up<lf>Last software reset details not available<lf>Error status: 0<lf>Free file entries: 10<lf>SD card 0 detected, interface speed: 20.0MBytes/sec<lf>SD card longest block write time: 0.0ms<lf>MCU temperature: min 18.7, current 25.6, max 25.7<lf>Supply voltage: min 0.5, current 1.7, max 1.7, under voltage events: 0, over voltage events: 0<lf>Driver 0: ok, SG min/max not available<lf>Driver 1: ok, SG min/max not available<lf>Driver 2: ok, SG min/max not available<lf>Driver 3: ok, SG min/max not available<lf>Driver 4: ok, SG min/max not available<lf>Date/time: 1970-01-01 00:00:00<lf>Slowest main loop (seconds): 0.001768; fastest: 0.000041<lf>=== Move ===<lf>MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0<lf>Scheduled moves: 0, completed moves: 0<lf>Bed compensation in use: none<lf>Bed probe heights: 0.000 0.000 0.000 0.000 0.000<lf>=== Heat ===<lf>Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1<lf>Heater 1 is on, I-accum = 0.0<lf>=== GCodes ===<lf>Segments left: 0<lf>Stack records: 1 allocated, 0 in use<lf>Movement lock held by null<lf>http is idle in state(s) 0<lf>telnet is idle in state(s) 0<lf>file is idle in state(s) 0<lf>serial is ready with "m122" in state(s) 0<lf>aux is idle in state(s) 0<lf>daemon is idle in state(s) 0<lf>queue is idle in state(s) 0<lf>autopause is idle in state(s) 0<lf>Code queue is empty.<lf>=== Network ===<lf>Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)<lf>HTTP sessions: 0 of 8<lf>- WiFi -<lf>Network state is running<lf>WiFi module is idle<lf>Failed messages: pending 0, notready 0, noresp 0<lf>WiFi firmware version 1.19.2<lf>WiFi MAC address 60:01:94:73:5b:4b<lf>WiFi Vcc 3.08, reset reason Turned on by main processor<lf>WiFi flash size 4194304, free heap 40544<lf>Socket states: 0 0 0 0 0 0 0 0<lf>=== Expansion ===<lf>ok</lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf> -
RE: New Board Can't Connect to Wi-Fi.
I had Firmware version 1.19.2 but upgraded to the latest 1.21 via SD card in the hopes that would help. When I run M122 I get the following:
m122
=== Diagnostics ===<lf>Used output buffers: 1 of 32 (1 max)<lf>=== Platform ===<lf>RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later<lf>Board ID: 08DDM-9FAM2-LW4S4-6J1DA-3S46R-K3TZW<lf>Static ram used: 16152<lf>Dynamic ram used: 100600<lf>Recycled dynamic ram: 2032<lf>Stack ram used: 3576 current, 4420 maximum<lf>Never used ram: 7868<lf>Last reset 00:00:18 ago, cause: power up<lf>Last software reset details not available<lf>Error status: 0<lf>Free file entries: 10<lf>SD card 0 detected, interface speed: 20.0MBytes/sec<lf>SD card longest block write time: 0.0ms<lf>MCU temperature: min 21.3, current 23.6, max 23.7<lf>Supply voltage: min 1.4, current 1.5, max 1.5, under voltage events: 0, over voltage events: 0<lf>Driver 0: ok, SG min/max not available<lf>Driver 1: ok, SG min/max not available<lf>Driver 2: ok, SG min/max not available<lf>Driver 3: ok, SG min/max not available<lf>Driver 4: ok, SG min/max not available<lf>Date/time: 1970-01-01 00:00:00<lf>Slowest main loop (seconds): 0.001772; fastest: 0.000041<lf>=== Move === <warning: maximal="" number="" of="" bytes="" per="" line="" exceeded!="" check="" the="" end-of-line="" settings="" or="" increase="" limit="" in="" advanced="" terminal="" settings.="">I can't tell you how much I appreciate the help, DC!</warning:></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf> -
RE: New Board Can't Connect to Wi-Fi.
The latest: now an M587 command reports "M587: Failed to retrieve network list<lf>ok<lf>" This is after an M552 command that shows WiFi module idle. Seems like I have a defective board. Anyone else have any ideas before I return the board as defective?</lf></lf>
-
RE: New Board Can't Connect to Wi-Fi.
This post is edited to add correct information:
Sadly, no joy.
When I use the 587 command, I get the following: "Remembered networks:<lf>TNCAP2FCC19<lf>My Network Name<lf>your=network-My Network Name Fa<lf>your-network-My Network Name Fa<lf>My Network Name <lf>My Network Name 2<lf>ok<lf>"
When I type the 552 S1 command, I still get: "ok<lf>WiFi reported error: no known networks found<lf>Wifi module is idle<lf>"
Hope I'm not being dense…</lf></lf></lf></lf></lf></lf></lf></lf></lf></lf></lf>