Update CR-10+Duet wifi from 2.05.1 to 3.0 firmware
-
the blue led on the board is lit... the duet is working fine... after dinner ill try a different computer
-
@Hélder-Rocha said in Update CR-10+Duet wifi from 2.05.1 to 3.0 firmware:
@Phaedrux said in Update CR-10+Duet wifi from 2.05.1 to 3.0 firmware:
@Hélder-Rocha I don't know if that's a problem or just what it normally does when it can't reach the site.
Are you able to connect the duet to your home wifi?
no... i am trying by the access point given by the board
Yes I understand that, but do you have a local WIFI network that you can test connecting to?
-
@Phaedrux yes offcouse. Also tried that way... could get in!
-
With my home network:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MSD-6J1F2-3S06L-T9VVB
Used output buffers: 1 of 24 (1 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 77144 of which 40 recycled
Never used RAM 11436, free system stack 170 words
Tasks: NETWORK(ready,408) HEAT(blocked,323) MAIN(running,474) IDLE(ready,19)
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 01:33:55 ago, cause: power up
Last software reset at 2021-01-30 15:46, reason: User, GCodes spinning, available RAM 15160, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 20.1, current 25.6, max 26.4
Supply voltage: min 0.7, current 1.6, max 1.8, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: position 0, ok, SG min/max not available
Driver 1: position 0, ok, SG min/max not available
Driver 2: position 0, ok, SG min/max not available
Driver 3: position 0, ok, SG min/max not available
Driver 4: position 0, ok, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 99.97ms; fastest: 0.14ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 0.7ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
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
USB is ready with "M122" in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 199.51ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 0 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.25
WiFi MAC address cc:50:e3:0d:1f:26
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 28272
WiFi IP address 192.168.0.23
WiFi signal strength -56dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
ok
- WiFi -
-
tried to access from a different computer, throw my home network and couldnt get there either.... what the hell can i be doing wrong!?
-
The duet IP address is 192.168.0.23
What is the IP address of your own computer?
Are they even in the same subnet?
-
@Phaedrux
IPv4 address.............192.168.1.2
subnet Mask.............255.255.255.0
Default Gateway.......192.168.1.1 -
@Hélder-Rocha i beleave i found the error.... when i was working on the RRF config tool, in the end, in the network setings panel, i havent change the Ip, nor the subnet mask or the gateway... i let it be as it was, thinking those were the correct ones!
-
@Hélder-Rocha said in Update CR-10+Duet wifi from 2.05.1 to 3.0 firmware:
@Hélder-Rocha i beleave i found the error.... when i was working on the RRF config tool, in the end, in the network setings panel, i havent change the Ip, nor the subnet mask or the gateway... i let it be as it was, thinking those were the correct ones!
so... whem i upload this settings as new config, i uploaded the wrong Ip etc etc
-
Are you assigning the IP address to the duet or is it getting a DHCP address?
If your PC is on 192.168.1 then the duet will also need to be on 182.168.1
-
@Phaedrux said in Update CR-10+Duet wifi from 2.05.1 to 3.0 firmware:
DHCP address
I dont know....is there a way to find out?
-
@Hélder-Rocha said in Update CR-10+Duet wifi from 2.05.1 to 3.0 firmware:
@Phaedrux said in Update CR-10+Duet wifi from 2.05.1 to 3.0 firmware:
DHCP address
I dont know....is there a way to find out?
it was the duet that gave me the ip address... i havnt select nothing!
-
when i uploaded the new files, for mistake i sent completly differrent ip and gateway
-
should i upload other DuetWiFiServer? To the card?
-
Post your config.g please.
No. Don't change any firmware at this point.
I want to see if your are setting an IP address in your config.g or if it's set to get an address from the router.
If the router is setting it and it's not in the same subnet as your PC that might mean the router needs to have some settings changed to let your wired and wireless devices communicate.
What is your router?
-
@Phaedrux said in Update CR-10+Duet wifi from 2.05.1 to 3.0 firmware:
Post your config.g please.
No. Don't change any firmware at this point.
i dont have access to my DWC. should i take it from the sd card?
-
Here it goes:
<; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.2 on Sat Jan 30 2021 16:42:08 GMT+0000 (Hora padrão da Europa Ocidental); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"CR-10" ; set printer name
M918 P1 E4 F2000000 ; configure direct-connect display; Network
M550 "CR-10"
M552 S1 ; enable network
M586 P0 S0 ; disable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S0 ; physical drive 3 goes backwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E93.00 ; set steps per mm
M566 X1200.00 Y1200.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X9000.00 Y9000.00 Z180.00 E6000.00 ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z100.00 E5000.00 ; set accelerations (mm/s^2)
M906 X800 Y800 Z800 E1000 I50 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X300 Y300 Z400 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S2 ; configure Z-probe endstop for low end on Z; Z-Probe
M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
G31 P500 X10 Y-40 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X20:300 Y20:300 S40 ; define mesh grid; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S150 ; set temperature limit for heater 0 to 150C
M308 S1 P"e0temp" Y"thermistor" T100000 B4092 ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S290 ; set temperature limit for heater 1 to 290C; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency
M106 P2 S1 H1:0 T45 ; set fan 2 value. Thermostatic control is turned on; Tools
M563 P0 D0 H1 F0 ; 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; Custom settings are not defined>
-
Ok. So your router is setting the IP address to a different subnet. So your PC can't reach it.
Can you try using your phone to connect to the duet? If they are both on WiFi they will likely be in the same subnet. Use your phone browser to go to the IP of the duet.
192.168.0.23
-
@Phaedrux rien de rien... no luck
-
shouldn t be th fact that i upload from the RRF diffrent IP and gateway?
