(05-Jan-2023, 02:28 PM)Rob Axel Wrote: … my vrx and system should be here soon.. thanks

When you go to update the firmware on the standalone vrx, make sure to use the GND file with the prefix SE. At the time of writing this is AvatarSE_Gnd_29.33.16.img

just adding my experience with WS and GPS. using avatar micro in a source one v5 with a bn220 mounted up front above camera. i used a sticky pad underneath the GPS module and shrink wrapped it to the frame to keep it there. zero issues, picks up satellites in seconds.

(24-Jan-2023, 09:36 PM)nobby Wrote: just adding my experience with WS and GPS. using avatar micro in a source one v5 with a bn220 mounted up front above camera. i used a sticky pad underneath the GPS module and shrink wrapped it to the frame to keep it there. zero issues, picks up satellites in seconds.

Is the location of the ws vtx at the rear of the frame?

(25-Jan-2023, 10:47 AM)ph2t Wrote: Is the location of the ws vtx at the rear of the frame?

sorry, yes it is. mounted on a tpu adaptor (for height to clear antenna arrangement) fixed to frame with a cable tie.

Updated original post to include usb breakout pads for 1s lite vtx pcb.

Looks like a newer firmware is now on the Caddx website, and official: 32.37.10

https://caddxfpv.com/pages/download

(26-Mar-2023, 12:52 AM)QuadFlyer68 Wrote: Looks like a newer firmware is now on the Caddx website, and official: 32.37.10

https://caddxfpv.com/pages/download

Heard that some users of this version were getting corrupted DVR files when exceeding 10 minutes where it breaks to a new file. Anyone know more about this bug?

(29-Mar-2023, 02:08 PM)Suros Wrote: Heard that some users of this version were getting corrupted DVR files when exceeding 10 minutes where it breaks to a new file. Anyone know more about this bug?

It was covered on JB's livestream yesterday at 9:36 into the stream. Click the link below to start watching that part of the stream...

https://youtu.be/MKSLBfSBkfE?t=576

(29-Mar-2023, 03:12 PM)SnowLeopardFPV Wrote: It was covered on JB's livestream yesterday at 9:36 into the stream. Click the link below to start watching that part of the stream...

https://youtu.be/MKSLBfSBkfE?t=576

This is actually where I got the info from, but nothing was really given about how to reproduce the bug, and weather has not been fitting for me to go do testing. Might just have to camp out on the previous version until more info comes out. I don't really use much for social media, so Facebook, Discord, and Twitter aren't really places I get any info from.

(29-Mar-2023, 03:33 PM)Suros Wrote: This is actually where I got the info from, but nothing was really given about how to reproduce the bug, and weather has not been fitting for me to go do testing. Might just have to camp out on the previous version until more info comes out. I don't really use much for social media, so Facebook, Discord, and Twitter aren't really places I get any info from.

It was publicised on Facebook before the FPV News so everything on there is all we know. As Caddx have confirmed the issue it's better to stay away from the 32.37.10 firmware if you are recording flights longer than 10 minutes each and you value your recorded footage. It doesn't always happen but there is a chance it might happen, and it only happens when a flight goes over 10 mins where the recording gets split into multiple files.

I posted some notes on the VRX, but seems the post was removed. Was it not appropriate for this thread?

(23-Apr-2023, 09:40 PM)mstc Wrote: I posted some notes on the VRX, but seems the post was removed. Was it not appropriate for this thread?

I've just checked the moderator logs for deleted posts and only one post has ever been deleted from this thread which was Rob3ddd who deleted one of his own posts on 25th January 2023.

Maybe you posted in another thread by accident or the post action of posting failed with an error without actually committing your post.

Odd it didn't save. Posting again, just testing some different display options for the VRX.

1) A small native 1080p budget screen for cameras. This one was 5.5" and a super bright 1000 nits. Latency was similar to the Cobra X V2, but image was sharp, vibrant, and bright. It was light enough and just the right size to fit into an old pair of HK DIY goggles.

2) Portable 15.6" display for laptops. This one had better latency, but colors were somewhat dull and not very bright so not for outdoor use. The screen is powered by USB.

This is just a rough relative latency comparison filmed at 240fps and comparing the timer difference shown on the display. VRX was set at 720p60.
- Headplay SE goggles = 0.05-0.06s
- Lepow Z1 15.6" Display = 0.06s
- Osee T5+ Display = 0.07-0.10s
- Cobra X V2 goggles = 0.08-0.10s

The 5.5" screen seen through the magnifying lens of the DIY goggles. The latency was quite flyable for a cruising quad, but maybe not ideal for aggressive flying. I wish I could use the Headplays, but too bad the aspect ratio distortion is too disturbing.

Anyone try the new 33.39.10 firmware? I installed it, but seems the high bit rate mode is no longer available, I only see the standard option in that setting. Also noticed the recorded file from both vtx/vrx are now marked as 60.01-60.02 fps instead of the previous clean 60, but probably of no consequence.

Edit: Hmm tried an older firmware and it was the same, so maybe I have some setting blocking the high bit rate mode? I tried changing 720 and 1080 but still high bit rate was not selectable, also not on the public channel either.

Maybe you have high frame rate selected? I think that blocks high bit rate ... (?)