You are here

M9 Rockets bricked; M9 NanoBridge updates to 3.21.4.0;

6 posts / 0 new
Last post
WY7MAE
WY7MAE's picture
M9 Rockets bricked; M9 NanoBridge updates to 3.21.4.0;

NanoBridge updated well using GUI in admin tab.  2 different Rockets seemed normal through TFT file transfer. Multiple reset attempts with factory version behaved the same.  There seems to be no RF out.  ipconfig returns ip address   169.254.182.10.  address used in edge browser returns "refused to connect".
Anyone else experiencing Rockets bricked but NanoBridges update fine?

nc8q
nc8q's picture
169.254.182.10. address used in edge browser returns "refused t

169.254.182.10.  address used in edge browser returns "refused to connect".

You will likely/hopefully find a better response here later, but
169.254.x.x is typical trait of windoze assigning an address to a device when
a DHCP server is not found.

Likely 168.254.182.10 is the address that windoze assigned to the ethernet device in your computer.
In the TFTP procedure, first you assign a static address to your computer's ethernet device.
After the transfer, the computer is set to obtain an address via DHCP.
Is there any chance that your computer is not set to DHCP mode?

 Why are you saying that they are 'bricked'?
Can the rockets be placed into 'TFTP mode?

Chuck

 

WY7MAE
WY7MAE's picture
Bricked may not be the proper

Bricked may not be the proper term.  I have repeatedly place the rocket in TFTP mode by following the AREDN "How To".  Using static IP address the upgrade firmware was loaded, in 9 seconds.  Back in dynamic IP address the browser cannot find the rocket trying localnode 8080.  I have since tried to install the factory firmware several times with the same result.
Merlin

k1ky
k1ky's picture
Bricked? Access

Try a different browser, or clear your Browser Cache, different computer etc.  How about accessing the node directly by it's IP adress:8080?

nc8q
nc8q's picture
After firmware upload, wait minutes

After firmware upload, wait minutes before attempting to obtain an IP address via DHCP.
i have had to wait up to 8 minutes before the device's DHCP service is active.
I think 3.20.x.x and later firmware responds to :80 and :8080.
So, http://localnode.local.mesh is sufficient.
Like Tom mentioned, clear cache or try another browser or another computer or reboot.
i hope this helps,
Chuck
 

K6CCC
K6CCC's picture
I ALWAYS use the IP address

I ALWAYS use the IP address rather than localnode.local.mesh  I find that FAR more reliable.
192.168.1.1 initially as I recall.
 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer