(07-Jun-2021, 04:41 AM)Rick h Wrote: Cool. i try to revert also. I also noticed the rssi drop after my last fw upgrade(?). I just dismissed it and haven't thought about it much until you guys mentioned it in this thread. I wasen't scrolling just the intermittant complete blackout. Whats weird, is that the dvr doesn't show the blackout in my case. solid video all the way to the crash site.

Lmk if it helped your issue or not... curious if it helped you or if it still continued.

Weird thing is that although the rapidFIRE updater showes v1.2.8 in the list of available firmware, there is no firmware change log mentioning the specific version and/or changes/fixes:

Source: https://www.immersionrc.com/fpv-products/rapidfire/

I have tried looking at the IRC RapidFire Group on Facebook (you do not need to browse but need one to share or post), and it seems Tony Cake is active on there: https://www.facebook.com/groups/294092717795488/

I did see a conversation about horizontal lines in the video feed but no one seems to have confirmed which version of the firmware fixed it for them.

Tony Cake has hinted some form of a firmware update for RapidFire and Ghost which will stitch the two systems and make an ecosystem similar to TBS Crossfire with Fusion.


I am still wondering how they will do it without modifying existing RF modules to be connected with a Ghost module (probably a mounting board of sorts with RF module and a Ghost rx) unlike how TBS did it using wifi modules built in the modules.

Maybe its a good time to get on there and make some noise

(07-Jun-2021, 07:01 AM)kafie1980 Wrote: Weird thing is that although the rapidFIRE updater showes v1.2.8 in the list of available firmware, there is no firmware change log mentioning the specific version and/or changes/fixes:

Source: https://www.immersionrc.com/fpv-products/rapidfire/

Code:

v1.0.7
Improve calibration accuracy

v1.0.9
Work on low power issue, delay low power check code to skip startup voltage drops with certain battery packs.
Add rapidFIRE #2 mode to support cameras and other hardware that violates PAL/NTSC specs.

v1.1.0  + v1.0.2
More work on low power issue
Module calibration improvements

v1.1.1
More work on low power issue, enable live voltage readout in the status menu

v1.1.3 + v1.0.4
Add PAL/NTSC osd mode to support events/leagues who need to know which mode a camera is in. Wider tolerance for cameras with unstable quartz oscillators

v1.1.4
Improved joystick code

v1.1.6
Add band scanner
Add RSSI Lite mode, with optional OSD readout position (incl. optimized HDO, HD2 modes)
Add basic model finder

v1.1.7
Refine model finder, add audible feedback

v1.1.8
Add in-goggle OSD with current band/channel, frequency, and RSSI during channel changes.

v1.2.4
Fixed mismatch between actual frequency, and OSD frequency.
Add presets for favorites for IMD6, etc.

v1.2.5
Slight tweak in sync timing.
Add support for SPI mode for integration of rapidFIRE into groundstations.

v1.2.6
Mirror the OLED menu into in-goggle OSD.
Fix occasional video issues in upper-rx only mode.
Fixed in-OSD RSSI bar for lower-rx only mode.

v1.2.7
Fix missing lock/unlock tones.
Add channel lock feature.
Add ability to change sync-lock time.

v1.2.9
Added long range OSD mode and audible feedback for twin high gain antenna use.
Added ‘yaw stuff’ unique ID to OSD modes.

v1.3.0
Very minor changes to the SPI interface for system integrators (ORQA, Groundstation Support, etc).
(no need to upgrade unless you are using the SPI interface).

v1.3.1
Added HDO2 setting to the OSD position control to correctly align with the top of the display.
(credits to Lee Schofield for finding this)

v1.3.2
Removed Sync Lock setting, defaults to short, eliminating rolling even with marginal systems

Yah I noticed that last night as well... possible typo?

This is interesting, I was getting very bad signal flying at an extremely sketchy waterfall spot this weekend, so I've been troubleshooting the issue this morning.
- I did a test using two different VTXs, but the same antennas
- Then I did a calibration on the RapidFire
- Then tested signal on the two VTXs again

Initial findings:
- Before the calibration, both my Signal Bars were around 80%, (of course I assumed this was 100%)
- After the calibration, my top signal bar shows more signal, but my lower bar is the same as before (Same as your guys are saying)

Another weird thing is the differences between the two VTXs themselves (TBS Unify HV and Matek Mini, both at 800mw)
- TBS signal goes up and down like hard movements
- Matek signal makes like huge rapid movements
- I'll post a video of all this later because it will probably be more interesting and helpful. But let's keep troubleshooting this, lame if the newest firmwares are causing issues instead of fixing them...

Cheers all!

So I did some tests and let me be clear that I am no RF engineer nor do I have the specialist tools or antennas to do very conclusive tests.

The antennas I used (not my favourite) were Foxeer Lolipop v3's and these were the only matching pair I had from the same manufacturer. I had to put some connectors on which I am sure introduced some signal losses to better position them on RapidFire module.



Checked I had the latest firmware:



I switched off my wifi, laptop, TV, unplugged all power and put my phone on airplane mode but that's all I can do living in an apartment unit with lots of RF interference around me.

Ran the calibration, first with VTX off and no antennas on Band/channel F4:



Next turned on the vtx at 25 mW and finalized the calibration procedure (without antennas):




First test performed with antennas positions as shown:



Result of first test in DVR:




Second test swapping antennas:



Result of second test in DVR:



The quad in all tests is a little over 2 meters away from my table and the vtx is set to 25 mW.

My conclusion seems to be that based on my testes swapping the antennas between the upper or lower connectors gives me different RSSI bars.

Further more, in none of these tests at 25 mW and 2 meters distance can I manage to get 100% RSSI from any combination. Probably the quality of the antennas and/or connectors could be the cause of this.

Perhaps, in previous versions the RSSI bars were not accurate enough and usually showed 100% RSSI at a short distance. Similar to how Crossfire folks would brag about 99% RSSI all the time  . 

Using my favourite set of Omni and Patch antenna's I do get close to 90% RSSI signal in real flights but never 100% on the same module. Some DVR I had from my last flight on my Source One:



Again the above image does not do justice since its not two omni's or two patches but I am flying towards myself. And yes the lower RSSI bar is clearly showing less signal strength and it had a patch on it which may have not been positioned well as I was seated under the trees to the left of this image.

But I am not ruling out any possibilities that the firmware version has anything to do with this (for better or for worse). 

The cold spell these coming weeks in the Southern hemisphere will hamper me from doing any decent outdoor tests.

(07-Jun-2021, 06:38 AM)AtomicAJ26 Wrote: Lmk if it helped your issue or not... curious if it helped you or if it still continued.

It’s gonna be next weekend before I can try this.

(07-Jun-2021, 04:52 AM)kafie1980 Wrote: Did you power your goggles through the PowerPlay DVR when the blackout happened in the goggles? What Cells are you running in them?

No I am not powering the goggles via the powerplay. I run a separate 2000mah 7.4 Lipo for the goggles

(07-Jun-2021, 06:38 AM)AtomicAJ26 Wrote: Lmk if it helped your issue or not... curious if it helped you or if it still continued.

I just reverted back to 1.2.8 also. I did not calibrate at all after reverting. RSSI bars are showing 100% and did fluctuate while flying as expected, when I went around the house or behind the buildings. I flew 2 packs with the rapidfire in my attitude v4s. It is definitely the best video i have had in a while. They also blacked out this morning on ver 1.3.2. On the second battery, I did loose the rssi bar graph twice, heard the beeps both times (desync notification?) but I never lost video and it did not even break up. I will calibrate, and do some more testing when I can. I also put the attitude v4 rx module in the HDO2s to see how that works. Its only a single antenna rx but it should tell me if it is the goggles if it blacks out.

I was reading the facebook page and it looks like you brought this up? I also saw that a few others seemed to be bringing this up also. Tony might want to resolve long standing issues with the module before trying to integrate this with his new products. Just my 2 cents.

Calibrate with antennas off like Oscar says, or with them on like painless 360 says? Rapidfire also seems to say off also (well they don't say to put them on anyways).

(13-Jun-2021, 05:14 AM)Rick h Wrote: Calibrate with antennas off like Oscar says, or with them on like painless 360 says? Rapidfire also seems to say off also (well they don't say to put them on anyways).

Calibrate with antennas off. Not just RapidFire manual recommends this but the TBS Fusion manual suggests the same.

Also set channel and band to F4 with power set to 25mw during second stage of calibration.

(13-Jun-2021, 04:18 AM)Rick h Wrote: I just reverted back to 1.2.8 also. I did not calibrate at all after reverting. RSSI bars are showing 100% and did fluctuate while flying as expected, when I went around the house or behind the buildings. I flew 2 packs with the rapidfire in my attitude v4s. It is definitely the best video i have had in a while. They also blacked out this morning on ver 1.3.2. On the second battery, I did loose the rssi bar graph twice, heard the beeps both times (desync notification?) but I never lost video and it did not even break up. I will calibrate, and do some more testing when I can. I also put the attitude v4 rx module in the HDO2s to see how that works. Its only a single antenna rx but it should tell me if it is the goggles if it blacks out.

I was reading the facebook page and it looks like you brought this up? I also saw that a few others seemed to be bringing this up also. Tony might want to resolve long standing issues with the module before trying to integrate this with his new products. Just my 2 cents.

Yah I posted in the fatshark FB page but don't see it anymore?

Glad 1.2.8 seems to have fixed our problem for the most part. I haven't had any of the problems since reverting back to 1.2.8 so im curious to see what IRC RF says though it seems like it was deleted.

(13-Jun-2021, 09:51 PM)AtomicAJ26 Wrote: Yah I posted in the fatshark FB page but don't see it anymore?

Glad 1.2.8 seems to have fixed our problem for the most part. I haven't had any of the problems since reverting back to 1.2.8 so im curious to see what FS says though it seems like it was deleted.

Your concern being RapidFire firmware related should be posted in the IRC RapidFire facebook group : https://www.facebook.com/groups/294092717795488/

If you posted it in the Fatshark group it won’t get too far. Future focus for FS is digital video.

Lately IRC and FS do not seem to show the level of collaboration they showed in the past.

(14-Jun-2021, 12:22 AM)kafie1980 Wrote: Your concern being RapidFire firmware related should be posted in the IRC RapidFire facebook group : https://www.facebook.com/groups/294092717795488/

If you posted it in the Fatshark group it won’t get too far. Future focus for FS is digital video.

Lately IRC and FS do not seem to show the level of collaboration they showed in the past.

Whoops, ment IRC RF

I've found a Fusion in-stock so I've ordered it and will see about doing a side by side to see if it i.proves some of these issues noted in the rapidfire posts.