@dc42 Will one of these work
With this antenna
https://www.amazon.com/gp/product/B01KBU61S8/ref=ox_sc_act_title_1?smid=A169Z7QURE8JMH&psc=1
The 6dBi antenna looked as though it would fit my home situation the best. Indoor 1-50M with excellent reception
Or would I be better off just getting the one with an internal Antenna?
Ok I have 2.04 installed and Wifi Module is going into idle again. But I'm still getting Errror retrieving Wifi status message: SPI timout.
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.04 running on Duet WiFi 1.02 or later
Board ID: 08DAM-9K9K2-NGNS0-7JKDL-3SJ6J-K70HL
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 92696 of which 0 recycled
Exception stack ram used: 288
Never used ram: 12408
Tasks: NETWORK(ready,1280) HEAT(blocked,1208) MAIN(running,3808) IDLE(ready,200)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:02:07 ago, cause: software
Last software reset time unknown, reason: User, spinning module GCodes, available RAM 11444 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x04433000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 12.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 29.2, current 30.6, max 30.8
Supply voltage: min 0.4, current 0.5, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
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
Cache data hit count 808438268
Slowest loop: 392.09ms; fastest: 0.05ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 160, MinFreeDm: 160, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== 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 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 ===
Slowest loop: 401.11ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8
@aidar
If is not a valid command why does it say OK?
I've tried it with M552 S0 and M552 S-0
Both respond with ok.
The part that you read up above I copy and pasted the entire dialog and as you can see when I typed M552 S-0 it responded with ok.
I've tried M552 I don't know how many times and at one point it was saying the wifi module is idle but now it just keeps saying wifi module is starting.
@droftarts
I had it in idle mode last night for abou a few hours. I sent M997 S0 M997 S1 M552 M552 S1 M552 S0 M552 more times than I can count and not all it that particular order. I really think my M key on my keyboard is about worn out. I've pulled my Micro SD card and formatted, copy pasted, watched numerous youtube videos and have read on the WIKI till I started seeing double. Took a three hour nap an only think I can say that has gone right is after the three hour nap I"m not seeing double anymore.
I've explored fallback firmware #1 #2 & #3
#3 I even started with a different freshly formatted SD card and still can't get he 1.02 to update to anything other than 1.02
When I send M115 I get
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-06-13b2
I have uploaded firmwares 2.05RC all the way down to 2.03. But it always says Duet Wifi 1.02
If that 1.02 is referring to my board then how do I actually check my wifi server bin version
When I send M122 This is what I get.
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
Board ID: 08DAM-9K9K2-NGNS0-7JKDL-3SJ6J-K70HL
Used output buffers: 1 of 24 (10 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93636 of which 0 recycled
Exception stack ram used: 312
Never used ram: 11444
Tasks: NETWORK(ready,548) HEAT(blocked,1172) MAIN(running,3832) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 07:17:54 ago, cause: software
Last software reset at 2019-01-22 23:57, reason: User, spinning module GCodes, available RAM 5672 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 12.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 28.7, current 29.8, max 32.3
Supply voltage: min 0.5, current 0.5, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
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
Cache data hit count 4294967295
Slowest loop: 99.59ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== 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 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 ===
Slowest loop: 0.20ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8
M552 S-1
ok
M552 S-0
ok
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
Board ID: 08DAM-9K9K2-NGNS0-7JKDL-3SJ6J-K70HL
Used output buffers: 1 of 24 (10 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93636 of which 0 recycled
Exception stack ram used: 312
Never used ram: 11444
Tasks: NETWORK(ready,548) HEAT(blocked,1172) MAIN(running,3832) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 07:17:54 ago, cause: software
Last software reset at 2019-01-22 23:57, reason: User, spinning module GCodes, available RAM 5672 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 12.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 28.7, current 29.8, max 32.3
Supply voltage: min 0.5, current 0.5, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
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
Cache data hit count 4294967295
Slowest loop: 99.59ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== 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 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 ===
Slowest loop: 0.20ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8
This is killing me. I had the printer on wifi at my old house but not running. I could home and web control worked. I'm at my new house and haven't been able to touch my printer in months. Well its all leveled out now and I can finally sit down and have a little fun.
I have been down the firmware rapids and yat bossa rumble. I am stumped.
I```
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.03 running on Duet WiFi 1.02 or later
Board ID: 08DAM-9K9K2-NGNS0-7JKDL-3SJ6J-K70HL
Used output buffers: 1 of 24 (10 max)
=== RTOS ===
Static ram: 25680
Dynamic ram: 93636 of which 0 recycled
Exception stack ram used: 304
Never used ram: 11452
Tasks: NETWORK(ready,548) HEAT(blocked,1172) MAIN(running,3844) IDLE(ready,160)
Owned mutexes:
=== Platform ===
Last reset 00:13:54 ago, cause: software
Last software reset at 2019-01-22 23:57, reason: User, spinning module GCodes, available RAM 5672 bytes (slot 1)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0xffffffff
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 12.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 28.9, current 30.2, max 30.5
Supply voltage: min 0.5, current 0.5, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
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
Cache data hit count 1610437237
Slowest loop: 1.09ms; fastest: 0.07ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Move ===
Hiccups: 0, FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== DDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
=== 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 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 ===
Slowest loop: 2137.36ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 0 of 8
I have had the module idle although it won't idle now.
I downloaded the three files 2.03 from the firmware page
[0_1575446666755_DuetWiFiServer.bin](Uploading 100%) [0_1575446670220_iap4e.bin](Uploading 100%) [0_1575446678921_Duet2CombinedFirmware.bin](Uploading 100%)
Formatted a fresh SD card (Completely blank)
made a new folder called "sys"
copied those three files into it and safely removed the usb
removed the sd card from my usb reader
powered the board on and hit the erase button (not reset)
opened yat and the board would not communicate (just to verify the firmware had been erased)
pulled the usb cord
installed the sd card into the board
plugged the usb cord in
turned power main on
opened bossa
clicked the boxes for (erase all)(lock)(boot to flash)
hit the refresh button and it showed up on com4 (instead of 3)
browsed to C:\Users\stacy\OneDrive\Desktop\sys\Duet2CombinedFirmware.bin
hit the write button
hit the verify button
waited till it was done
opened YAT
hit M115
hit M997 S0
hit M997 S1
hit M552 (disabled)
hit M552 S1 (ok)
hit M552 (module is starting)
waited
hit M552 (module is starting)
waited
Hit M552 S0
before I wend down this road at least I would get a return of (wifi module is idle)
still shows old wifi firmware
I cannot get the wifiserver firmware to update even after hitting the erase button
This is what I get
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-06-13b2
I have tried multiple duetwifiserver.bin files and it will always says 1.02
Can my duet WiFi operate without end-stops? I remember coming across eliminating end-stops using stall detection. I think I remember seeing that some of the new boards can do this but wasn't sure if my 1.02 version could do this.
Ok I finally got my printer on wifi again and I can log into web control. But I never sent any firmware upgrade commands. I downloaded the 1.21 files and put them on the SD card. Then I went onto the reprap configuration tool and input all of my 3d printers specifications. Downloaded the file and copy and pasted the 4 home files and config.g file onto my SD card. It asked if I wanted to replaced the files and I said yes replace the files.
A couple of weeks ago during all my reading I came across a post that said while upgrading your firmware you need to copy the files on the SD card and then send a command. I can't seem to find this post again and am just wondering if when I send the M115 and it returns 1.21 that means I'm actually running that
Firmware Version (file Duet2CombinedFirmware.bin): 1.2
WiFi Server Version (file DuetWiFiServer.bin): 1.21
Web Interface Version (file DuetWebControl.zip): 1.21
Should I use the configurator or use a copy of the latest files on the sd card shipped now even though my board is 1.02
I promise I have read over the links that you have posted multiple times I'm just not sure which one I should use.
I have had this board for a while. I have loved this board ever since I got it. I totally messed something up a while back and have read and read and tried following the documentation and just keep making things worse. I'm at the point right now I'm not sure where to start. Now I can't even see it on the network. Making matters worse I left the micro sd card on my desk and my 3 year old decided that it looked like a yummy snack. So now I don't even have that. I just went and purchased a 16gb micro sd card and need to start from scratch. I have read so much its all starting to blurr, someone please pull me out of my downward spiral.
If I can get a printer on the network with the latest firmware that communicates with simplify 3d I would be so happy. As for tuning the config file for printer settings I think I have under control I still remember my old acceleration settings, speed, size, homing setup. So i can get that going after I can update the config file through the web interface.
Thank you in advance.
MM/sec
current layer height/total layers
current travel speed(live update mm/per sec instead of speed of percent of something you entered 10 hours ago on a long print)
current print speed(same)
current acceleration settings
extruder retratction settings (live update) Hard I know cause this is done in the slicing software but maybe could be done in firmware
Serial console of gcode that is being transmitted.
Is there a way to do exactly what you said but for all three axis and all at once and the it auto updates your configuration file. Or would that be a lot of programming. I guess this isn't really a much desired question because not many people change parts on their printer on a daily basis.
My printer is printing absolutely awesome though right now. My next questing is to use a filament thickness sensor that updates your filament thickness live while its printing.
Kind of t3p3
more like dc42 but a little bit more
Move all three axis to their furthest point away from endstop switch.
Now run SPECIAL GCODE (Gtardis) and it will measure or count till it hits and endstop. not only that but take those settings and put them into the printer dimensions settings.
Maybe if the min value was say 3 mA then no one else would make this mistake.
Wow I'm and idiot. I went back and looked at the configuration tool and it says 800 mA default and it was me who actually put 1.2.
Just delete this thread.
I acutally looked at the back of my motor and saw 1.2 amps and didn't convert to mA.
I Think I just discovered a bug. For some reason. I tried to reconfigure my printer with the RRC configuration tool. After re uploading my motors make sounds but wouldn't move. I noticed that in the config file of when it used to work I had to put 1200 mA instead of 1.2. Well the new file configured to 1.2 which is what I would suspect if the comment section to the right said amps. Well I changed it back to the 1200 mA and they are working fine again.
On a delta, I don't allow ordinary moves before the printer has been homed. I've considered adding this restriction to other printer geometries, but I am not sure whether all users would like it. On a Cartesian printer, users may wish to jog the axes before homing. What do other users think?
I would hate it if I could not jog axis when not homed…. think of an estop event where the IR probe failed to trigger (happened to me yesterday) I have an optical endstop located just above which triggers an estop event but I then need to jog the bed back down before I can home the machine. There are other times when I jog around when not homed as well and love the estop feature that has saved my butt a couple of times
If you can disable it in firmware yes. I have to use this all the time with my printer cause I'm constantly making changes to parts and have to recalibrate axis dimensions.
I'm on my 9th prototype printer. I"m constantly making changes to things , (Extruders, gantry's, pulleys, etc) every time I make a change I have to go in and extend my software axis limits so that I can sit there on each one microstep till it gets to the actual limit and make sure its not gonna crash into something like an extruder, fan, thermister, etc.
If I could physically move the axis where I want the soft limit to be the send a (Learn HOME ALL command) kept track of how far it moved and then either printed out in the G code console how far it moved or actually update the firmware. This would save me hours upon hours dialing in my axis dimension.
I have a way but it might be hard with your setup. Move your z to the pre leveled. Enable the motor motors your stepper should be locked pull to a full step loosen your coupler on your z height assuming you only have one Z acme shaft and then tighten your set screw. I have tried this before while calibration diagnosing but after that I didn't really have a use for it.
Ok all axis are working correctly except for Z. I think it is trying to use a probe. I can run and M119 to check the state of the three inductive sensors and they are not triggered the I can move the axis to there end stops to trigger. I run M119 to check the states again and all three change state but but when I try to home the Z it just crashes.
Should I make a new thread for this question and put it in the firmware section? BTW thank you DC42 for the response.
On another note I had all 3 axis and my extruder set to 256x with no interpolation and they can't barely move at 300mm a second. If I go in and set them up like my old controller board at 16x microstepping it will dry run at 900mm a second. I'm thinking it my be my stepper driver pulses being sent may have hit a cap. Is there a max pulses that I can be sent if so can it be raised?
