Posts made by Condensedcloud

Can I buy you guys a beer?(EDIT where/who do I donate/paypal) I do plan to support the project with future builds utilizing the chip but I do appreciate the above and beyond support you've provided.

YASSSSS, Thank You. Thank You. Thank you Gentleman. I was losing hope and we are online. I thought I had a dead printer on my hand. I've heard you are the best in the business and your customer support has proven it to be so. (not to mention the quietest and smoothest delta I've ever worked with due to your handiwork) I plan on building a few more printers in the near future with some friends and I hope to not be such a pain in the arse for you guys soon. You get my standing ovation for your diligence standing behind your product.

@dc42 I dropped the .zip file into the /www folder I then double clicked it to extract it into the folder. I then followed the Getting Connected to Your Duet Steps into the Terminal. Same result (EDIT: left the .zip file in the /www folder)

confirmed: https://imgur.com/a/30g8QEV

@dc42 Tried clearing cached data in browser (EDIT: also tried a different browser), same result, wall of text:

Connecting...
Printer is now online.

M552 S0
SENDING:M552 S0
WiFi module started
M122
SENDING:M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.0 or 1.01
Board ID: 08D6M-91AST-L23S4-7J1DG-3S86K-TPXFK
Used output buffers: 1 of 20 (1 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98588 of which 0 recycled
Exception stack ram used: 256
Never used ram: 6704
Tasks: NETWORK(ready,1492) HEAT(blocked,1296) MAIN(running,3868) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:00:48 ago, cause: power up
Last software reset details not available
Error status: 0
[ERROR] 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 16.0, current 21.2, max 21.4
Supply voltage: min 0.0, current 0.5, max 0.8, 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 86005194
Slowest loop: 99.20ms; fastest: 0.06ms
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: 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 ===
Slowest loop: 1.28ms; fastest: 0.00ms
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.22
  WiFi MAC address a0:20:a6:19:45:f5
  WiFi Vcc 3.38, reset reason Turned on by main processor
  WiFi flash size 4194304, free heap 33632
  Socket states: 0 0 0 0 0 0 0 0

M552 S1
SENDING:M552 S1
WiFi module is connected to access point interwebs, IP address 10.0.0.28
M552
SENDING:M552
WiFi module is connected to access point interwebs, IP address 10.0.0.28

@dc42 Sending M122 from pronterface (w/o getting connected in terminal) :

M122
SENDING:M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.0 or 1.01
Board ID: 08D6M-91AST-L23S4-7J1DG-3S86K-TPXFK
Used output buffers: 1 of 20 (1 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98588 of which 0 recycled
Exception stack ram used: 304
Never used ram: 6656
Tasks: NETWORK(ready,1872) HEAT(blocked,1324) MAIN(running,3868) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:00:24 ago, cause: power up
Last software reset details not available
Error status: 0
[ERROR] 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 16.1, current 19.7, max 19.9
Supply voltage: min 0.0, current 0.6, 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 41978028
Slowest loop: 0.28ms; fastest: 0.06ms
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: 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 ===
Slowest loop: 0.18ms; fastest: 0.00ms
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 disabled
  WiFi module is disabled
  Failed messages: pending 2779096485, notready 2779096485, noresp 2779096485
  Socket states: 0 0 0 0 0 0 0 0

@dc42 renamed /www to /www-old Created new /www file and unzipped DWC 2.0RC3 into it (no index.html or .vs file was added) Same result. No idea how to run disc checking on an SD card on a MAC. Could this have something to do with my DuetWebControl.bin file in /sys being dated to 2016?

@dc42 ran M39 in pronterface, returned this:
M39
SENDING:M39
SD card in slot 0: capacity 7.74Gb, free space 7.04Gb, speed 20.00MBytes/sec, cluster size 32kb

Appears to be mounted
(EDIT: here is an image of what my SD card currently looks like: https://imgur.com/a/30g8QEV )

@dc42 1. M503 seemed to read the contents of the the .config.g ... M39 returned this: Error: G-Code buffer 'serial' length overflow (Edit: see next comment running command in pronterface, sdcard appears to be mounted)

2. unzipped reprap.htm.gz file in /www folder ... /js folder is in /www folder ... /sys folder is in the main SD folder and not in the /www folder

Still cannot connect to web interface

@phaedrux extracted the duetwebcontrol-1.22.6 into the www/ folder (it was previously version vr. 1.19 which I deleted) after following the Getting Connected Steps again I came up with the same result:

Your Duet rejected the HTTP request: page not found
Check that the SD card is mounted and has the correct files in its /www folder

@dc42 thank you, it appears I am getting closer. I got to step 9 in the instructions and when attempting to connect to the IP address in the chrome browser I get this message:

"Your Duet rejected the HTTP request: page not found
Check that the SD card is mounted and has the correct files in its /www folder"

I haven't messed with any of the files in its /www folder ... Should I?

@dc42 Ok so it appears the Firmware is now on : RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.02(RTOS) ELECTRONICS: Duet WiFi 1.0 or 1.01 FIRMWARE_DATE: 2018-12-24b1 I then sent the M997 S1 command which completed successfully. I then disconnected my printer and ran a LAN SCAN to try and find an IP address to connect to the web interface and nothing popped up.

Bossac isn't allowing me to put it in the Bin folder for 1.19 and 1.18 says the file is damaged and I need to eject installer so this command line terminal situation also does not seem to be panning out

@phaedrux I do not have access to a windows computer, I also just tried Bossa on a different macbook running High Sierra 10.13.6 and had the same problem. Do I need to track down a windows computer? I might be able to figure something out over the course of the next week.

el capitan 10.11.6 it's an old AF macbook pro. no security blocks

@phaedrux well, I installed it. It opened up for a second but then when I went to click the port it closed itself and now whenever I try to open it, it just closes itself immediately without opening anything. Just pops up in the dock and disappears immediately. Tried reinstalling it and restarting my computer.

It says interactive Boss doesn't work on high DPI screens and I get this error: BOSSA cannot be opened because of a problem. Check with the developer to make sure BOSSA works with this version of OS X. You may need to reinstall the application. Be sure to install any available updates for the application and OS X.

also when I open this 'Bosac' in terminal it just shows me this:
Last login: Thu Feb 7 22:47:56 on ttys000
Benjamins-MacBook-Pro:~ condensedcloud$ /Volumes/BOSSA/bossac ; exit;
bossac: you must specify at least one option
Try 'bossac -h' or 'bossac --help' for more information
logout
Saving session...
...copying shared history...
...saving history...truncating history files...
...completed.

[Process completed]
and then doesn't let me type anything

@phaedrux so it says i need to do this: bossac --port=COMxx -b -U -e -w -v path\DuetWiFiFirmware.bin -R
Replace COMxx in the above by the COM port number (e.g. COM3) and replace path\DuetWiFiFirmware.bin to the path and name of the firmware file to install but as far as I know Macs doesn't use COM port numbers? Sorry I have no idea what I am doing and this is very frustrating and I appreciate you helping me out.

@phaedrux thank you I will try this, just to check though, will this procedure erase the firmware for my specific printer? and if so how would I back that up?