Topic: Red Firmware 6.0

[Cutty Sark Sailor]

Red Firmware 6 is out... major update.

[Jumpin Joe]

Thanks Mike!

Joe

[miraculon]

Thanks, again Mike.
There are many new goodies in 6.0. Monitoring windows to make gain setting easier.
Also enhancements for the AS3935.
The AS3935 settings and the RGND/Rseries settings for the MP voltage monitor had to be re-entered.

Greg

[Cutty Sark Sailor]

I think that un-synced "show noise" is going to help a great deal with tracking interference sources!!!!

[Jumpin Joe]

I think that un-synced "show noise" is going to help a great deal with tracking interference sources!!!!

I checked that out.... Seeing the noise or lack of is neat.

[W3DRM]

Just d/l'd v6.0. Noticed the following setting resets:

• Remote Control settings is set to "Automatic" - Blitzortung forum says it is not active as yet. I changed mine back to "manual".
• Web Interface settings were reset to null.
• GPS baudrate goes back to 38400. I changed mine back to 115200 which it had been set to before the upgrade.
• Amp 1 - antennas set to null. Changed them back to loop for my setup.
• Amp 1 - Parameters set to 10 * 10 for both channels. Changed them back to 4 * 4 for my setup.
• Amp 1 - thresholds remained at 120mv

After making all of the changes needed to get back to where I was prior to the update, all seems to be running just fine. Will continue to monitor for any other issues.

[miraculon]

    Remote Control settings is set to "Automatic" - Blitzortung forum says it is not active as yet. I changed mine back to "manual".
    Web Interface settings were reset to null.
    GPS baudrate goes back to 38400. I changed mine back to 115200 which it had been set to before the upgrade.
    Amp 1 - antennas set to null. Changed them back to loop for my setup.
    Amp 1 - Parameters set to 10 * 10 for both channels. Changed them back to 4 * 4 for my setup.
    Amp 1 - thresholds remained at 120mv

Strange, I didn't have any of these change. I had my GPS set to 38400 before the update.
Were they saved at some point prior to the update?


Greg

[W3DRM]

    Remote Control settings is set to "Automatic" - Blitzortung forum says it is not active as yet. I changed mine back to "manual".
    Web Interface settings were reset to null.
    GPS baudrate goes back to 38400. I changed mine back to 115200 which it had been set to before the upgrade.
    Amp 1 - antennas set to null. Changed them back to loop for my setup.
    Amp 1 - Parameters set to 10 * 10 for both channels. Changed them back to 4 * 4 for my setup.
    Amp 1 - thresholds remained at 120mv

Strange, I didn't have any of these change. I had my GPS set to 38400 before the update.
Were they saved at some point prior to the update?


Greg

Yes, all settings had been saved prior to the upgrade. The Blitzortung forum mentions that some settings have been set to defaults:

• Firmware 6.0 / 2014-01-05
  NOTE: Due to minor changes in the settings structure, some settings have been set to defaults.
  Please check your configuration or reset them to defaults.

[miraculon]

    Remote Control settings is set to "Automatic" - Blitzortung forum says it is not active as yet. I changed mine back to "manual".
    Web Interface settings were reset to null.
    GPS baudrate goes back to 38400. I changed mine back to 115200 which it had been set to before the upgrade.
    Amp 1 - antennas set to null. Changed them back to loop for my setup.
    Amp 1 - Parameters set to 10 * 10 for both channels. Changed them back to 4 * 4 for my setup.
    Amp 1 - thresholds remained at 120mv

Strange, I didn't have any of these change. I had my GPS set to 38400 before the update.
Were they saved at some point prior to the update?


Greg

Yes, all settings had been saved prior to the upgrade. The Blitzortung forum mentions that some settings have been set to defaults:

• Firmware 6.0 / 2014-01-05
  NOTE: Due to minor changes in the settings structure, some settings have been set to defaults.
  Please check your configuration or reset them to defaults.

These were the only ones that I lost.

The AS3935 settings and the RGND/Rseries settings for the MP voltage monitor had to be re-entered.

I wonder why the difference between your results and mine...

Greg

[W3DRM]

Not sure. I did upgrade from v5.0 and had pretty vanilla settings from what I can tell. Based on the note I saw on the Blitzortung forum, I had written down my settings prior to the upgrade so it only took a few minutes to review them and get them back to where had been.

Am wondering if it had something to do with my unit coming up in "Automatic" mode when it rebooted? That may have forced settings to be changed and then automatically saved which would have overwritten my original settings.

Here is what I see when I select Automatic mode:

• Remote Control
  Mode:
  Automatic Mode: Blitzortung.org servers try to find the best settings for your station. You don't have to worry about gain and other settings. The controller does not store any of those remote values in flash! You can see the current values on the "Status" page. See documentation which parameters could be transmitted (coming soon).
  
  Note: This feature is currently in a early beta stage on the server side. It will take some time to adjust this feature. Have a look into our forum for latest news about it.[/b]

The wording above contradicts statements on the B forum that it hasn't been implemented yet.

Uh-oh, just noticed that my firmware upgrade apparently did NOT install. I see it still shows as being the old rev level:

• Controller / CPU
  Firmware Rev. 5.0 / Dec 1 2013 11:20:02 (Git: 5.0-0-gd68f531)
  Hardware Rev. 10.3 (PCB-Id 1)
  Device-ID 3E00-3100-0747-3133-3235-3735
  HCLK / SYSCLK / PCLKs 168 / 168 / 42 / 84 MHz
  CPU 24%, 40.2°C, 2.95V
  Max. Memory usage 81kB + 65kB for Signals
  Signal Buffers 32, 1 currently used
  Input Voltage 4.97V
  

Am going to try to reload the v6.0 firmware as see what happens. Back in a bit...

[W3DRM]

Not sure what happened but now I am seeing Rev 6.0 on my status display so apparently the first attempt to upgrade did not go correctly even though everything appeared to be correct. This time however, all of my settings remained as they had been prior to the upgrade. Must have been some kind of a glitch with the first attempt that caused the rest of my values.

[miraculon]

Firmware 6.1 is just out. It has adaptive threshold/gain based on noise floor. This is not the anticipated "Automatic" mode.

I had some initial problems with AS3935 initialization and the GPS had trouble getting a fix. I never had GPS issues before this. I misread and thought that this was the "Auto" support feature. (need to improve the old "reading comprehension skills"  )

It is automatic, but not the server driven full auto mode yet.

It is interesting watching the gain/thresholds adapt.

Greg

[saratogaWX]

I applied 6.1 and had the 'smoothed' longitude become 0.0000000 (so 'invalid GPS fix').

I tried sending an Initialize to the GPS .. no change.

I waited about 10 minutes to see if the GPS issue would resolve (it didn't) so I reloaded 6.0 firmware and all is well again.

Think I'll wait for 6.2 update

[miraculon]

I applied 6.1 and had the 'smoothed' longitude become 0.0000000 (so 'invalid GPS fix').

I tried sending an Initialize to the GPS .. no change.

I waited about 10 minutes to see if the GPS issue would resolve (it didn't) so I reloaded 6.0 firmware and all is well again.

Think I'll wait for 6.2 update

I didn't have any luck with "initialize" either, but the "warm start" did seem to fix it after a while.
The adaptive gain/threshold is really cool and once the GPS gets going, it works.
It took a really long time after the warm start to sort out the 0.000000 Longitude and get a fix. Definitely a bug, I have never seen anything like this since I built up the RED.

Greg


Greg

[W3DRM]

I applied 6.1 and had the 'smoothed' longitude become 0.0000000 (so 'invalid GPS fix').

I tried sending an Initialize to the GPS .. no change.

I waited about 10 minutes to see if the GPS issue would resolve (it didn't) so I reloaded 6.0 firmware and all is well again.

Think I'll wait for 6.2 update

I didn't have any luck with "initialize" either, but the "warm start" did seem to fix it after a while.
The adaptive gain/threshold is really cool and once the GPS gets going, it works.
It took a really long time after the warm start to sort out the 0.000000 Longitude and get a fix. Definitely a bug, I have never seen anything like this since I built up the RED.

Greg


Greg

My installation of 6.1 went smoothly except that it took a little over 300 seconds for the GPS to get a fix. I did not have any problems with the smoothing though. That worked as it should have.

The new auto gain feature is working great here on my system. Prior to 6.1, I found myself chasing a happy setting. It seems to be quite a bit different at night with lower settings necessary probably due to everyone having their lights on.

Looks like 6.2 should be out soon, according to Tobi's posts on the Blitzortung forum.

[flc85]

I applied 6.1 and had the 'smoothed' longitude become 0.0000000 (so 'invalid GPS fix').

I tried sending an Initialize to the GPS .. no change.

I waited about 10 minutes to see if the GPS issue would resolve (it didn't) so I reloaded 6.0 firmware and all is well again.

Think I'll wait for 6.2 update

I didn't have any luck with "initialize" either, but the "warm start" did seem to fix it after a while.
The adaptive gain/threshold is really cool and once the GPS gets going, it works.
It took a really long time after the warm start to sort out the 0.000000 Longitude and get a fix. Definitely a bug, I have never seen anything like this since I built up the RED.

Greg


Greg

You must reboot and wait several minutes

[saratogaWX]

Updated to 6.1.  Did a warm-start on the GPS.  Rebooted and waited.  About 4 minutes later, the GPS position (smoothed) finally corrected itself, so I'm up on 6.1.

Odd that the update didn't handle the smoothed GPS longitude

[W3DRM]

Updated to 6.1.  Did a warm-start on the GPS.  Rebooted and waited.  About 4 minutes later, the GPS position (smoothed) finally corrected itself, so I'm up on 6.1.

Odd that the update didn't handle the smoothed GPS longitude

I think that is something Tobi is working on for the next firmware release. Glad to see you got 6.1 working with the reload. I had a similar problem with 5.0 even though the indications were a good upgrade, I had to do it again to get everything running correctly. As they say, "stuff happens"...

[Cutty Sark Sailor]

http://tracker.blitzortung.org/red/Firmware_6.2.bin

[Jumpin Joe]

http://tracker.blitzortung.org/red/Firmware_6.2.bin

Thanks Mike.... updated successfully.

Joe

[saratogaWX]

Did the update 6.1->6.2 -- same GPS issue (longitude 0.000000 smoothed) that worked itself out over 5 minutes.
Other than that, no issues

[Jumpin Joe]

Did the update 6.1->6.2 -- same GPS issue (longitude 0.000000 smoothed) that worked itself out over 5 minutes.
Other than that, no issues

Mine did the same Ken.

Joe

[Cutty Sark Sailor]

WEB Firmware update is broken with 6.2
Tobi to release fix ASAP

So if you haven't updated, might hold off till 6.3!!!
Otherwise will have to revert to ST-Link update utility ... remember that???

[Jumpin Joe]

WEB Firmware update is broken with 6.2
Tobi to release fix ASAP

So if you haven't updated, might hold off till 6.3!!!
Otherwise will have to revert to ST-Link update utility ... remember that???

All i do is run into problems..... 

[miraculon]

From what was posted on the Blitzortung forum, it looks like if you attempt to web reflash with 6.2, you will "brick" the unit.
I already loaded 6.2. Time to drag out the laptop again...

Greg