New SWIFT™ AI TRANSMITTER and New Firmware Release

Please register or login

Welcome to ScubaBoard, the world's largest scuba diving community. Registration is not required to read the forums, but we encourage you to join. Joining has its benefits and enables you to participate in the discussions.

Benefits of registering include

  • Ability to post and comment on topics and discussions.
  • A Free photo gallery to share your dive photos with the world.
  • You can make this box go away

Joining is quick and easy. Log in or Register now!

Did the v19 upgrade for my Teric yesterday and the screen keeps shutting off after a minute or so. Any ideas?

I did my Perdix first using a Windows laptop; worked fine. The Perdix is "classic" bluetooth.

I got the same problem you did with my Teric from the Windows Shearwater Cloud Desktop and Windows 10 BLE (Bluetooth Low Energy). It's a long story, but Windows machines seems to be twitchy with BLE, something I routinely experience trying to upload dives from my Teric.

I switched to the Android Shearwater app (and Android/cellphone BLE) and the Teric update completed there the first time. Took a lot longer to update the Teric using BLE than it did to update the Perdix using classic Bluetooth. That's an expected outcome.
 
I know @DiveClimbRide said "no rush", but this is done now for Android. iOS will likely take another day or so. This morning my android phone told me there was a Shearwater update in the Google Play Store. After updating, I connected it to my Perdix AI and successfully changed the startup image.





rsingler is correct. You can mix and match. We made all our firmware updates backwards compatible so that we could keep on using PPS transmitters. That said, we recommend that you use no more than 2 PPS transmitters on a single diver with one being grey and the other being yellow. This is to reduce likelihood of lost comms due to signal collision. You could expand to using 3 PPS transmitters if you have access to the rare green PPS. In other words, all PPS transmitters should have different colors in order to reduce collision likelihood.

That is awesome!!! You are lauded for quick customer service, and deservedly so. But, that turnaround to get the mobile app updated is over the top!

On the transmitters, it is my understanding that (for example) all the grey ones have the same transmit frequency. So, if you turn multiple of them on and they are not interfering with each other before you start a dive, then they will continue to not interfere with each other during the dive.

Is that correct?

Also, while I'm asking, can you tell us the total time a single transmission takes? It transmits every 5 seconds. Does that transmission take 1.0 seconds? 0.1 seconds?

Thanks!

I was very lucky to scoop up a new green transmitter a few years ago. I have a grey and the green on my rEvo. Works flawlessly with my NERD2. I sure hope the green one never dies!
 
Is anyone else experiencing a degradation of the start-up image quality when uploading it?
 
That is awesome!!! You are lauded for quick customer service, and deservedly so. But, that turnaround to get the mobile app updated is over the top!

On the transmitters, it is my understanding that (for example) all the grey ones have the same transmit frequency. So, if you turn multiple of them on and they are not interfering with each other before you start a dive, then they will continue to not interfere with each other during the dive.

Is that correct?
Theoretically, that sounds correct. In the real world, each of those components has a tolerance range, so some may be slightly faster than others. So while they might not interfere at the start of the dive, they could creep up on each other after some time. That could take a while to clear depending on the duration of the transmission and the timing differences between the two.

Having two very different timings means that at some point, they will probably interfere, but by the next transmit cycle, all should be clear again.
 
I did my Perdix first using a Windows laptop; worked fine. The Perdix is "classic" bluetooth.

I got the same problem you did with my Teric from the Windows Shearwater Cloud Desktop and Windows 10 BLE (Bluetooth Low Energy). It's a long story, but Windows machines seems to be twitchy with BLE, something I routinely experience trying to upload dives from my Teric.

I switched to the Android Shearwater app (and Android/cellphone BLE) and the Teric update completed there the first time. Took a lot longer to update the Teric using BLE than it did to update the Perdix using classic Bluetooth. That's an expected outcome.
When I first downloaded the Shearwater Cloud Decktop to my Windows computer, it downloaded all my dives fine. When I tried to update my Teric firmware, it failed. The update worked fine on my Android phone. I continue to load new dives using the Cloud Decktop, now running 2.7.1. I recently updated the firmware on my Teric to v19 using my phone. Next update, will try the Desktop again to see if it works.
 
...it is my understanding that (for example) all the grey ones have the same transmit frequency. So, if you turn multiple of them on and they are not interfering with each other before you start a dive, then they will continue to not interfere with each other during the dive.

Is that correct?
Theoretically, that sounds correct. In the real world, each of those components has a tolerance range, so some may be slightly faster than others. So while they might not interfere at the start of the dive, they could creep up on each other after some time. That could take a while to clear depending on the duration of the transmission and the timing differences between the two.

Having two very different timings means that at some point, they will probably interfere, but by the next transmit cycle, all should be clear again.
Hi Stuart and thank you for the kind words. Brian is correct in his response.

Frequency vs Interval
I just wanted to clarify some semantics that might bring confusion. While you are technically correct when you use the word "frequency" (because it can be measured in cycles over time) we try to use the word "interval" when referring to what you are referring in your question. This is to differentiate from the wireless radio frequency that is used to transmit the information.

All the transmitters in this discussion are fixed at a frequency of 38 kHz. The transmission interval varies to avoid interference. Average transmit interval is 5.0 seconds, and the Swift can vary its interval randomly between 4.8 and 5.2 seconds to help avoid interference. Additionally, the Swift contains a receiver to help avoid interfering with other nearby transmitters, delaying transmission if other activity is detected.

Contrast this with fixed-interval transmitters that lack receivers and cannot dynamically listen or avoid collisions from nearby transmitters. Fixed interval transmitters can interfere even if they start at different times due to clock drift. When the drift is slow, they can stay in interfering timing for several minutes or more.

FCC ID
Please note that the FCC ID of the Swift is NOT MH8A for these transmitters, but 2AO24-17001. The FCC ID is different since the Swift is our own design (does not use anyone else's chip or code) and we must apply for our own FCC ID. However, the Swift is compatible with our legacy and future AI computers and our new computer firmware retains compatibility with transmitters with the FCC ID of MH8A.

Also, while I'm asking, can you tell us the total time a single transmission takes? It transmits every 5 seconds. Does that transmission take 1.0 seconds? 0.1 seconds?
Transmit time is roughly 0.15 seconds. This corresponds to around 3% of available bandwidth.

Chance of Collision between Fixed-Interval Transmitters
The random turn-on chance of two fixed-interval transmitters interfering is very roughly 3%, however, this chance increases substantially if more fixed-interval transmitters are added. Using Swift transmitters, the interference chance is greatly reduced (but not completely eliminated). Interference likelihood will be higher with a mix of fixed-interval and Swift transmitters since the fixed-interval units do not avoid collisions.

I was very lucky to scoop up a new green transmitter a few years ago. I have a grey and the green on my rEvo. Works flawlessly with my NERD2. I sure hope the green one never dies!
Excellent. These are hard to find. I believe their interval is fixed at 4.8 seconds. I currently have a yellow and a Swift in the rEvo I dive. I've setup my son with a fixed grey (he's on OC single tank) and monitor his pressure on my computers. I have this combination on purpose trying to see if things break (dropped comms). We have a robust battery of lab tests done at the factory, but we also do a good amount of formal and informal tests under real life conditions. So far I have not experience drops that I can attribute to collisions.

Using 38 kHz transmitters for Buddy Checks
While I just confessed that I monitor my son's pressure on my computer, I have to clarify that these transmitters are not meant for buddy checking. Until last Sunday, my son was not aware that I was monitoring his transmitter on my computer and he was very diligent monitoring his own pressure, responding to my tank pressure queries and signaling for turnarounds at the appropriate pressures in accordance to his gas planning. His own responsibility for managing his own gas was never relinquished away.

These transmitters were not designed for buddy checking because of the limited range the 38 kHz frequency has underwater. I do get frequent dropped comms from my son's transmitter when we separate for more than approx 5ft.

Is anyone else experiencing a degradation of the start-up image quality when uploading it?
Hi Mark. Please keep in mind that the screen resolution of the Perdix AI is 320 x 240 pixels. Most cameras these days take images at a much higher resolution. Displaying a high resolution image in a Perdix screen requires resizing of the image. Before uploading your images to the Perdix you can try using an image editor to resize it to 320 x 240 to see if your choice of image has an acceptable appearance at the lower resolution of 320 x 240.
 
Hi Stuart and thank you for the kind words. Brian is correct in his response.

Frequency vs Interval
I just wanted to clarify some semantics that might bring confusion. While you are technically correct when you use the word "frequency" (because it can be measured in cycles over time) we try to use the word "interval" when referring to what you are referring in your question. This is to differentiate from the wireless radio frequency that is used to transmit the information.

All the transmitters in this discussion are fixed at a frequency of 38 kHz. The transmission interval varies to avoid interference. Average transmit interval is 5.0 seconds, and the Swift can vary its interval randomly between 4.8 and 5.2 seconds to help avoid interference. Additionally, the Swift contains a receiver to help avoid interfering with other nearby transmitters, delaying transmission if other activity is detected.

Contrast this with fixed-interval transmitters that lack receivers and cannot dynamically listen or avoid collisions from nearby transmitters. Fixed interval transmitters can interfere even if they start at different times due to clock drift. When the drift is slow, they can stay in interfering timing for several minutes or more.

FCC ID
Please note that the FCC ID of the Swift is NOT MH8A for these transmitters, but 2AO24-17001. The FCC ID is different since the Swift is our own design (does not use anyone else's chip or code) and we must apply for our own FCC ID. However, the Swift is compatible with our legacy and future AI computers and our new computer firmware retains compatibility with transmitters with the FCC ID of MH8A.


Transmit time is roughly 0.15 seconds. This corresponds to around 3% of available bandwidth.

Chance of Collision between Fixed-Interval Transmitters
The random turn-on chance of two fixed-interval transmitters interfering is very roughly 3%, however, this chance increases substantially if more fixed-interval transmitters are added. Using Swift transmitters, the interference chance is greatly reduced (but not completely eliminated). Interference likelihood will be higher with a mix of fixed-interval and Swift transmitters since the fixed-interval units do not avoid collisions.

Excellent. These are hard to find. I believe their interval is fixed at 4.8 seconds. I currently have a yellow and a Swift in the rEvo I dive. I've setup my son with a fixed grey (he's on OC single tank) and monitor his pressure on my computers. I have this combination on purpose trying to see if things break (dropped comms). We have a robust battery of lab tests done at the factory, but we also do a good amount of formal and informal tests under real life conditions. So far I have not experience drops that I can attribute to collisions.

Using 38 kHz transmitters for Buddy Checks
While I just confessed that I monitor my son's pressure on my computer, I have to clarify that these transmitters are not meant for buddy checking. Until last Sunday, my son was not aware that I was monitoring his transmitter on my computer and he was very diligent monitoring his own pressure, responding to my tank pressure queries and signaling for turnarounds at the appropriate pressures in accordance to his gas planning. His own responsibility for managing his own gas was never relinquished away.

These transmitters were not designed for buddy checking because of the limited range the 38 kHz frequency has underwater. I do get frequent dropped comms from my son's transmitter when we separate for more than approx 5ft.

Hi Mark. Please keep in mind that the screen resolution of the Perdix AI is 320 x 240 pixels. Most cameras these days take images at a much higher resolution. Displaying a high resolution image in a Perdix screen requires resizing of the image. Before uploading your images to the Perdix you can try using an image editor to resize it to 320 x 240 to see if your choice of image has an acceptable appearance at the lower resolution of 320 x 240.

Thank you for the info on the 0.15 second transmission time.

On the FCC ID, just an FYI, I said that it was MH8A because I read on the Dive Gear Express website this:

The Shearwater SWIFT transmitter is backwards compatible with all pre-existing Shearwater air-integrated computers ..., and likely to work with those specific models ... with transmitters having the same FCC ID = MH-8A number.

Shearwater Research SWIFT Transmitter

Screenshot 2021-07-28 173235.png
 
@Shearwater - what is the interval on the current Yellow and Grey transmitters?

Great work BTW. Good to see an 'Ethernet’ type backoff protocol.
 
So I installed #84 last night and afterwards I had a few dives to download. I always backup to both SW and Subsurface. SW worked fine but SS downloaded a lot more than just my previous dives and labeled them all #0. They were duplicates of other dives.

I know this is a SW thread but figured I'd chime in with an issue that I found. Maybe @dirkhh can take a look?

I did the update and the downloads through an Android phone, I'll try a PC at work later today and see what it does.

Between @Shearwater @dirkhh Subsurface and my Perdix AI I'm not sure what else I'd really need in a dive computer. It's all just neatly tied together. You guys both rock.
 
https://www.shearwater.com/products/perdix-ai/

Back
Top Bottom