Posts made by tinkerz

@wilriker disregard, wrote a quick gcode file and figured it out, comes out on the WebUI. Perfect. Adding to end scripts. Now we just need logging.

Tinkerz

Way late to the game on this one. I've done a M200 conversion, sharing my config.g as I haven't had the time to read through all 99 posts on this thread (trying to finish an M300 mod by next weekend for MakerFaire PDX). Welcome any input if I've done something wrong. Hope it helps if you're having troubles.

I swapped hotend to a Slice Engineering Mosquito keeping the extruder, added a BLtouch for leveling and z-stop, removed the waffle board and added PEI (Buildtak Flexplate is going on it today).

Tinkerz

0_1536446140699_config-clean.g

@phaedrux Do you mind if I share pic on social media?

@wilriker In your end codes you say, then where does the response show up? Is it on the console page of the WebUI or console of the PanelDue (output is limited to 100 chars so the real data gets cut off doing it here).

Thanks,
Tinkerz

Hey all, been a bit since I was here. Getting ready for our local MakerFaire but had the SD card on the Duet die today so I ended up with a pre-filament sensor backup config and had to come get the filament sensor running again.

Tony, wanted to share the results I do have, I haven't updated (completed all the columns) but it's a living document and will get updated from time to time. Hardest part is remembering to do a M591 before hitting print again. Doh. Feel bad I keep forgetting it. Hmm, maybe I need a sticky not on the PanelDue.

Anyways results doc is here:
https://docs.google.com/spreadsheets/d/1yy3DLxXhCFD81EiPyyuIEZaPnIgQgkvuVNcFQiZ7ceU/edit?usp=sharing

Tinkerz

@kraegar Thank you! Not sure why I didn't think of putting it up on Google docs, here I have all my results in good 'ol Notepad++. Thank you again. This makes it easy to keep updated without worrying about saving, losing or sharing.

Tinkerz

@wilriker Thanks for clearing that up about there being both opened and closed. I saw the closed but also saw the one making reference to divergence of the light with the angled window. Guess I just assumed they had eliminated that already. Carry on all!

@guyaros Isn't the filament window in line (at least partially) with the filament sensor and therefore lacking in the background for the sensor to compare against? Ie, isn't light getting to the sensor?

I do love the design and was like "yes, let's print it. can I have the step file so I can put it on my extruder mount?" And was enjoying the filament window when it suddenly hit me that it may be letting light get to the sensor.

Thoughts? Have you tried it yet?

Hey everyone, I'm a little late joining the party but I'm here. Let's see if I get this all right.

Current Setup:
1 Filament Sensor on E0
Mount printed in Proto-Pasta Matte Fiber Black (hoping the matte helps with the readings)

Photos of custom mount + block provided via Thingiverse (not modified from STL yet)

Ok, I think that's everything about my setup. I did wonder though are we running the sensors disabled 100% of the time or is that up to us whether we want it active or not? Ie, if we get froggy and want to activate it after we feel confident with it do we want that data or just keep collecting data points.

Also, haven't looked into it, but couldn't we get the M591 D0 data dumped to a file automagically at the end of each print? I feel like I saw enough commands in the the RepRap playbook that that feels possible. I might dig into that.

Thanks, I'l be back with data, for now, I'm off to torture my filament sensor with matte fiber, CF, and glitter!

• TinkerZ

Greetings all! Operation WiFiSwap via ChipQuik was a success. Board seems significantly more responsive and stable now. I'll have a better idea once I upgrade the Zortrax M300 with it. But for now I'm happy to report that a WiFi module can be desoldered via ChipQuik and a new one installed.

Maybe some documentation on this would be nice. Or at least let people know to copy the DuetWiFiServer.bin file to the /sys folder and perform a M997 S1 to get the WiFi chip firmware loaded. Initially I was a bit sad to only see the light flicker once on the WiFi module. But once I tried poking it with commands I started to get the feeling it might not know how to respond appropriately so I flashed it's firmware. And all set. Connected!!

Yay! Thanks again folks.
Keith

That all makes sense. More hassle than it's worth. Thanks for the transparency.

Keith

Thanks, will do. Though I was hoping to get that module replaced under warranty. Yes I know it's outside the 6 month window but the board did sit quite some time before I got to use it to the point where I could see it had problems. Just hoping for a little good will on the replacement. If not, no worries!

Also, a quick question regarding the external antenna WiFi, can the Duet board be ordered with that installed, or is there a product variant without the WiFi chip installed so that we can add the antenna mount version? Asking for future development as it was posed to me by other engineers being concerned about essentially locking the board inside a faraday cage by burying it inside a box of metal. Or will we just need to plan to desolder and resolder each one?

Thanks again,
Keith

Thanks for getting back so fast. Agreed, I believe the whole issue on the old board is the WiFi module. If you were to send a replacement for that I'll get it swapped out, whether it be giving the ChipQuik a try for the experience or having someone with desoldering equipment do it I'll get it accomplished.

@t3p3tony Yes, very much so. I did order another DuetWifi for another system and to further troubleshoot I've placed the new board in place of the old one. And no connection issues so far. Significantly more stable. No loss of connection via USB, no drops via wifi, no issues communicating with the PanelDue. All comms instability has disappeared. Looks to be pointing to an issue on the board. GIven the number of times I've updated it. downgraded it and even completely erased it and reinstalled everything I'm beginning to suspect it's the board.

Thank you for the response, I will try that down the road. For the moment I'm happy the board is operational and the machine is running so I don't want to go back down that rabbit hole at the moment.

Spent a good portion of the evening last night fighting WiFi connectivity on the DuetWifi. Originally purchased the board in Oct 2017, had hooked it up to a single motor/rail to play with it while waited for the rest of the mechanical parts. Those parts never developed so I gave a printer a brain transplant with the DuetWifi last night (July 2018). That's when things went all wonky and the board wouldn't stay connected. Near the end I realized I had done all the updates to 2.0/1.21.1 shortly after bringing the board live as if I had just pulled it out the box. Doing the good dutiful thing of updating all the firmware. It then dawned on me finally that the connectivity issue hadn't been there before in Oct '17 so I got out a new SD card loaded it up with 1.19, reflashed all the firmware back to 1.19 and the unit is stable again. Not sure what's up with 2.0/1.21 but here are some of the M122 diag's I got back from it. I also have some pics of the PanelDue console showing that it was disconnecting and reconnecting every few minutes. In the troubleshooting process I had stripped the board down to just the board and power, and in fact used 2 different power supplies and even just powered the board via a 5v battery over USB for a bit, because I thought I was chasing ground loops or bad/noisy motors, all sorts of things in the connectivity troubleshooting. In the end rolling back to 1.19 resolved everything. I'm not sure if my board is of the age it can't be upgraded to the latest firmware or what but hopefully the attached M122 queries will shed some light.

Thanks for your time,
Keith

---

9:21:50 PMM122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS) running on Duet WiFi 1.02 or later
Board ID: 08DDM-9FAM2-LW4S4-6JTD0-3SN6N-T2VZY
Used output buffers: 3 of 20 (8 max)
=== RTOS ===
Static ram: 28380
Dynamic ram: 95740 of which 0 recycled
Exception stack ram used: 284
Never used ram: 6668
Task NETWORK ready, free stack 440
Task HEAT blocked, free stack 1256
Task MAIN running, free stack 3624
=== Platform ===
Last reset 00:01:08 ago, cause: reset button or watchdog
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.6, current 37.0, max 37.0
Supply voltage: min 23.9, current 24.0, max 24.2, 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: 2018-07-10 21:21:50
Slowest loop: 3.73ms; fastest: 0.07ms
=== Move ===
Hiccups: 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
=== 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: 14.22ms; 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 0, notready 0, noresp 0
  WiFi firmware version 1.21
  WiFi MAC address 2c:3a:e8:0a:f5:5f
  WiFi Vcc 3.35, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 15960
  WiFi IP address 192.168.1.95
  WiFi signal strength -49dBm, reconnections 0, sleep mode modem
  Failed to request ESP stats
  Socket states: 0 0 0 0 0 0 0 0
  === Expansion ===
  9:21:44 PMConnection established!
  9:15:04 PMDisconnected.
  9:14:45 PMM122
  === Diagnostics ===
  RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS) running on Duet WiFi 1.02 or later
  Board ID: 08DDM-9FAM2-LW4S4-6JTD0-3SN6N-T2VZY
  Used output buffers: 1 of 20 (13 max)
  === RTOS ===
  Static ram: 28380
  Dynamic ram: 95784 of which 0 recycled
  Exception stack ram used: 356
  Never used ram: 6552
  Task NETWORK ready, free stack 460
  Task HEAT blocked, free stack 1256
  Task MAIN running, free stack 3560
  === Platform ===
  Last reset 00:02:41 ago, cause: reset button or watchdog
  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 38.6, current 39.3, max 39.5
  Supply voltage: min 23.9, current 23.9, max 24.2, under voltage events: 0, over voltage events: 0
  Driver 0: standstill, SG min/max 0/216
  Driver 1: standstill, SG min/max not available
  Driver 2: standstill, SG min/max 0/589
  Driver 3: standstill, SG min/max not available
  Driver 4: standstill, SG min/max not available
  Date/time: 2018-07-10 21:14:45
  Slowest loop: 9.64ms; fastest: 0.08ms
  === Move ===
  Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 238, MaxWait: 4294915897ms, Underruns: 0, 0
  Scheduled moves: 10, completed moves: 10
  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: 3.01ms; fastest: 0.07ms
  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 0, notready 0, noresp 0
  WiFi firmware version 1.21
  WiFi MAC address 2c:3a:e8:0a:f5:5f
  WiFi Vcc 3.35, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 15640
  WiFi IP address 192.168.1.95
  WiFi signal strength -47dBm, reconnections 0, sleep mode modem
  Socket states: 0 0 0 0 0 0 0 0
  === Expansion ===
  9:12:21 PMM122
  === Diagnostics ===
  RepRapFirmware for Duet 2 WiFi/Ethernet version 2.0(RTOS) running on Duet WiFi 1.02 or later
  Board ID: 08DDM-9FAM2-LW4S4-6JTD0-3SN6N-T2VZY
  Used output buffers: 3 of 20 (8 max)
  === RTOS ===
  Static ram: 28380
  Dynamic ram: 95740 of which 0 recycled
  Exception stack ram used: 284
  Never used ram: 6668
  Task NETWORK ready, free stack 460
  Task HEAT blocked, free stack 1256
  Task MAIN running, free stack 3560
  === Platform ===
  Last reset 00:00:17 ago, cause: reset button or watchdog
  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 36.7, current 38.8, max 38.9
  Supply voltage: min 23.8, current 23.9, max 24.1, 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: 2018-07-10 21:12:20
  Slowest loop: 3.73ms; fastest: 0.07ms
  === Move ===
  Hiccups: 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
  === 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: 14.25ms; 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 0, notready 0, noresp 0
  Failed to get WiFi status
  Socket states: 0 0 0 0 0 0 0 0
  === Expansion ===
  9:12:14 PMConnection established!
  9:11:16 PMDisconnected.
  9:02:48 PMConnection established!
  9:02:25 PMDisconnected.
  9:02:09 PMConnection established!
  8:56:48 PMDisconnected.
  8:56:38 PMConnection established!
  8:55:52 PMDisconnected.
  8:55:40 PMConnection established!

I found a potential problem when configuring my DuetWifi for the first time.

After running the RRF Configuration Tool I downloaded the config.zip. I was unable to upload the .zip file from the Settings page because the Upload button did not appear. It did finally appear when I resized the browser window. Seems at a certain browser window size the upload button becomes visible. See attached images. The browser window is 983 wide in the image without the Upload button and 999 wide in the one with the upload button. Is perhaps the trigger width 990? Anyways, just wanted to share this because it was extremely frustrating trying to upload the configuration without the button.

Error information:
Browser: Chrome Version 60.0.3112.113 (Official Build) (64-bit)
OS: Windows 7
Duet Information is in the Images.

Thanks for all your hard work,
Keith

https://www.dropbox.com/s/6y57ix2nnktj7v5/DWI-1.png?dl=0

https://www.dropbox.com/s/xqcryku61tijuno/DWI-2.png?dl=0