You are here

Nano M2 and 3.16

8 posts / 0 new
Last post
We1btv
We1btv's picture
Nano M2 and 3.16

 

I decided to go for the 3.16 version and uploaded the software. Looked nice.
Weird enough the software thought it was a Bullit but seemed to run good on the Nano-loco.
Changed the distance, password and call. Added a tunnel, also no problem. Changed to ch -2 and told the Nano-loco m2 to save the changes. All data changed. Forgot to go to 10dbm. Changed it to 10dbm and told the Nanoloco M2 to save it all...
The only thing my computer came up with was “connection lost”. Localnode:8080 to get back in the nono was no problem. However, saving the changes was no option. Not even after a hard reset.
I tryed to reload the 3.16 file again. Same result. No way it would accept any changes. Whatever I tryed, no result at all. Kept losing the connection over and over.

Now what? I decided to load the 3.1 BBHN software in to one of my old Linksys routers.. (yes yes, ik know, hi) and reload the older 3.15 version in to the Nano again.

This was the only way to get the file in to the Nano and get it going again the way I wanted it to run.

Knowing how to solve the problem I followed the same steps al the way from the beginning again to figuere out what I was doing wrong but with the same result. The Nano would not accept any changes if connected by cable. Only through the air.. Did I do something wrong??

Hope this solution helps others when they get stuck in there node wanting to update the node data.

73, Ruud PE1BTV / WE1BTV

K5DLQ
K5DLQ's picture
did you perhaps try to access
did you perhaps try to access with either:
localnode.local.mesh:8080
OR
we1btv-xxxxx.local.mesh:8080  (your actual node name)

 
We1btv
We1btv's picture
Hi Daryl.

Hi Daryl.

Went in to the node using localnode:8080. Worked fine.
The problem only started after saving data the first time, call, password and distance i.g.
Without changing any IP-adress I could get in by using localnode again. So it's not looking like a IP issue.
The other thing was the software thought it was a bullit instead of the nano-loco M2 it is...
I'll reload the 3.16 version again later and play with it to see if there are more “funny problems”, hi

Ruud

KG6JEI
When you do a first time save
When you do a first time save the node name/password/etc the node IP address changes. Some browsers and computer combinations tend to work funny in this regard. I always recommend closing the browser (all windows) after doing an IP change which the first setup does changed.

As for loco thinking its s bullet: assume you mean form the firmware name or sysinfo page. Both of these are correct the Loco internally is wired similar to a Bullet (it does have second antenna port internal but that's handled)  so it should be w bullet machine type. As long as your not seeing an unsupported/untested warning your fine there.

 
We1btv
We1btv's picture
Hi Conrad.

Hi Conrad.

Been playing for a while now. Look you were right. The only browser behaving like that is Firefox.
Thanks.

Ruud
k1ky
k1ky's picture
Nano M2 and 3.16
I had the same problem with one of my nodes- turned out to be a browser cache issue.  Nothing I did would allow any changes, but changed to another node on another computer and it worked. Then rebooted the original computer and all worked fine.  All other node upgrades on Rocket, Nanobridge, Airgrid and Nanostations worked great.
KG6JEI
+1 on this.
+1 on this.

Seen it many time, the browser gets confused by the node changing IP address at one point in its life.

Generally if the node IP changes (as during initial setup) i recommend closing the browser.

Submission forms seems really susceptible to this. I just had this issue yesterday on Firefox, every page worked, except the firmware upload submission form.  Close the browser (meaning all tabs and instances of the browser) and then launch the browser again and everything is fine.
 
KA9Q
Might it be possible to avoid
Might it be possible to avoid a browser shutdown by deleting cookies and/or clearing the cache? Sometimes you have a lot of things going on and you don't want to have to completely shut down your browser.

Another possibility (especially easy on the Mac) is to use an alternate browser. E.g., Firefox is my primary browser, but I can run Safari or Chrome as an alternate, and they each have their own caches and cookie stores.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer