Over The Air Update Causes SS Interface Issue

Stations Receivers
1

Hi everyone, I have been updating previously installed Motus stations with Sensorstations, with the newest disc image and firmware updates. Unfortunately, I have run into an issue after running an “over the air” firmware update after which, I can no longer connect to the Sensorstation Interface. This has now happened to me at three different Motus stations. Is anyone experiencing this issue? Is there a fix?

  1. In my case, upon arrival I am able to connect just fine to the SS interface using an ethernet cable.
  2. I go ahead and turn off the Sensorstation, place it in rpi.boot mode and write the new disc image with the Raspberry Pi Imager successfully.
  3. I restart the Sensorstation, and am able to connect to the interface successfully.
  4. I then proceeded to conduct an “Over the Air Firmware Update”, which seems successful, but then can no longer reconnect my laptop to the Sensorstation Interface, no matter what I try to do next (e.g., switch usb ports, restart my laptop, switch laptop ports, reboot many times the SS, switch browser, get rid of any proxies, etc.)…

Any help would be appreciated. My computer battery ran low by the end I didn’t want to attempt to start a disc image writing again, but is that the only solution? Thanks!

William

2

Hi William,

As far as I know that is the only solution (and then don’t run the firmware update!). Both Pat @user982 and I have experienced this issue at quite a few stations as we prep them for Blumorpho compatibility. My understanding is that there are many other users who have also experienced this. CTT hinted that there may be yet another disk image update needed to fix the issue, but I haven’t heard anything recently.

Levi

3

I just read @jsrs post about issues connecting. You might give that a read. I think the two issues are related.

4

Thanks Levi,

I figured there have to be more people out there experiencing similar issues. I did read jsr’s issue and it seems really similar to ours here, except the IP address does show up on the LCD of the SS board, although I can’t seem to connect to it.

I read Garrett’s response to jsr, but believe all the USB ports do work as they worked before the update.

I read David’s response to jsr, and I did try to switch the ethernet connector ends between the laptop and SS board, and that didn’t work.

Good to hear CTT was working on a potential fix as we were planning to update all of the PNW Motus disc images next year for bluetooth and overall performance of USB ports.

Thanks

5

William, that Rpi Compute Module I gave you the other day was recently reflashed with Image 2024-09-10T00:0 and ota software update run. It should be at system version 1.7.0. Everything checked out with it on the bench tests including recognizing multiple funcubes etc. Only thing that should be needed is to pop it in and run the radio updates which do not require ‘over-the-air’. If you still have access to the station you could give that a try. -Rich

1 Like
6

Did you run the “Over the Air Firmware Update” while your funcubes/RTL-SDRs were plugged in?

Did you do a hard restart (flip the power switch off, wait 10s, then on)?

7

kther is nothing Ive seen in the docs regarding running OTA updates with or without Funcubes installed. Should they be in or out? If they are required, I am curious - are OTA updates reprogramming them?

8

Our experience running radio updates on V3 SS has been to disconnect all the FCDs, run all the radio updates, then reconnect FCDs 1-by-1 confirming each is recognized in the SG interface as you go.

-Todd

1 Like
9

I did not unplug FCDs and was not instructed to do so. I’m curious if there’s an issue with not doing so, but will unplug them moving forward, thanks!

I do complete hard restarts by turning off completely the power using the power toggle switch.

Thank you all for the brainstorming and follow-up comments!

10

Hi everyone: PROBLEM SOLVED and identification of two separate issues:

After some testing with a spare compute module and a V3.3 Sensorstation (SS) board, I was able to identify whether the SS board, the compute module, or the ethernet cable/laptop were at fault in connecting to the SS interface. Using two separate compute modules (i.e., one module already clipped in my SS board, and a spare one Rich gave me [thanks, Rich!] - and both modules were rpi 3+ 32GB, running the latest disc image and station updates), I immediately identified an issue with using either compute modules:

  • The original compute module that came with my brand new V3.3 SS enabled me to connect just fine to my laptop using the ethernet cord (and usb adapters) but NOT enable a modem connection (Diagnostic B on SS board was off). The original compute module NEVER connected to the modem… despite my many tries and all the tricks up my sleeve.
  • Rich’s compute module swapped in my SS board instantly connected to the cell network (with diag. LED B turned on), BUT NO connection to the SS Interface using the ethernet cable from my laptop to the SS board!

This exemplifies the issues I’ve been having in the field, which were:

1- Sensorstations that do not enable you to connect your laptop to the SS interface.

2- Sensorstations that do not connect to cell network (diag. B off).

PROBLEM & SOLUTION #1: Sensorstation Interface connection to laptop using ethernet cable:

This is reminiscent of prior issues some users were encountering in the past with older SS boards when the modem would override network connections - in effect, disabling the ethernet cord connection. As to test this you can unplug the modem out of the SS board (when power is off) and you will instantly connect your laptop to the SS Interface, however you cannot perform “over the air” station updates, or radio port updates, without internet.

The solution that worked for me here was: On your PC, go to your “View your Network Connections” > Open your Ethernet Connection and click on “Disable” it > Then, go back to that same ethernet connection and “Enable” it again > Then, go to your local web browser and type in “sensorstation.local” in the search bar, and the SS Interface page should display.

PROBLEM & SOLUTION #2: Diagnostic B - Internet not connecting despite activated modem and strong cell signal:

From the best of my knowledge issues with modems connecting to a cell network where diagnostic B doesn’t turn on, despite strong cell signal and using booster antenna, etc., will not resolve. The only solution I have found is to reflash (or swap) the compute module. This was confirmed with a single SS board where I swiped between two compute modules, one worked, the other didn’t, in successfully, and repeatedly, obtaining a network connection and turned-on diagnostic “B” light.

Due to these issues, I highly recommend users write new disc images and perform a station update on compute modules before they go in the field and then swapping compute modules in the field with one you know is up to date (i.e., latest disc image and station updates), versus attempting to flash disc images in the field. Note: if you swap compute modules, you will still need to update your SS board’s radio firmware.

Hope this works for you!