Video pixelated and delayed/missing

[EliotBR (Eliot)]

Hi @Cocis,

Apologies for the delay on getting to this.

@Cocis

as soon as you touch the joistick to move it left and right the response is very sudden and quick, not very gradual (pilot gain 25%), while watching the other videos in the forum i didn’t noticed it so if you could help me or direct me to dome other topic that would be great.

I brought this up internally and it was suggested that it may help to reduce the ACRO_YAW_P parameter, although that generally shouldn’t be necessary. Maybe try updating to the ArduSub 4.1.1 beta firmware first, and resetting your parameters, and if that doesn’t help then try adjusting ACRO_YAW_P

@Cocis

I ask for some help for a video problem. As you can see in the link below at 10sec and 20sec (but also further on and in most videos) there is a pixelation and sort of lost of imaging. I was wondering if there is anything we can do to fix it.

It doesn’t look to be a continuous issue, which means there’s likely something going on in software or hardware that’s causing reduced video communication bandwidth. Potential causes for that would be

• a faulty/degraded connection (as @mjr suggested)
  • it may help to check your connections
  • it may be worth running a network test to see your general bandwidth availability
  • maybe try a different tether pair (if you have one)
  • maybe try bypassing the Fathom-X boards and tether entirely, with a direct ethernet connection from the onboard computer (Raspberry Pi) to your control station (topside) computer / to the ethernet-USB converter in the FXTI
• excessive use of resources elsewhere on the onboard computer
  • I’d be interested to know whether you have the same issues using BlueOS instead of Companion
• power supply issues
  • the camera and/or onboard computer may have issues when several thrusters are on strongly, especially if they turn on suddenly
    • visually that doesn’t seem to be what’s happening here, but if you’re concerned it could be helpful to limit maximum thrust
• strong electrical noise
  • could cause communication signal issues when thrusters turn on, although that’s unexpected for differential signals like used by the Fathom-X
• electronics overheating
  • the camera or onboard computer could be throttling or having occasional failures due to high temperatures
  • especially relevant if you have an acrylic enclosure and are operating in warm water

There could also be decoding issues at the surface (as @Jotakajota discussed), but I’d expect them to be more consistent, rather than decent performance for a while that momentarily goes bad from time to time.

If those suggestions don’t prove fruitful, feel free to reach out to our support email (support@bluerobotics.com), to let them know what’s going on, what you’ve tried so far, and how the vehicle has been used and stored. If possible it’s best to also specify your order number (or rough order date), so we can add the issue to our internal tracking and try to prevent similar issues happening in future (by quality testing, or by revised designs). If it turns out something is defective then you may be able to get a replacement or refund of the relevant part(s).