My HaLow signal while charging is usually -65.
SUDDENLY its -39.
I have changed nothing…
Is it a sign of my DC’s early demise?
Any advice is appreciated…
@Yarbo-Forum
1 Like
Nope it’s a sign that you have the same bug I’ve been seeing. Signal gets worse and then snaps back to normal. -39 is most likely your normal or round about. Mine is -5. Tell me why sometimes I have -43 while only 4 ft from the data center.
4 Likes
Snapped right back to -65 this morning. However I just checked it and it’s at -41. 
1 Like
We’re sorry to hear about this issue—it may require further investigation. Could you please submit a support ticket so our team can take a closer look?
We truly appreciate your patience and understanding!
2 Likes
I’ve seen similar behavior very close to DC. Radiant pattern low power zone near antenna?
Theory:
Not sure how HaLow controls its signal power. Maybe when rover is away it goes higher power making the dead low power zone near antenna larger. When the rover is back close to DC it switches to a lower power which has a smaller low power zone under the antenna which then sees a better signal?
Anyone with insight please correct.
2 Likes
I have wondered if they are supporting this but haven’t received confirmation that they are. All indications are that it is not doing this and there’s something else not quite right.
3 Likes
Let me start with I Love the idea of this system. It seems to more of a hobby than a product. I believe marketing got way out over their skis and made many promises that just aren’t reality.
- Most WIFI radios today which should include Halow, should be capable of supporting variable Tx (Transmit) power.
The yarbo is basically a multiband radio that uses RF frequency to control functions to achieve its goal. I have thousands of multiband radios in the air that receive firmware updates regularly either from us or from the manufacturer, it appears to me that yarbo is loading all of these machines individually one at a time and they never built a tool to be able to upload machine after machine from the cloud. With their Halow product it is simply a 900 MHz radio operating between 9.02 to 9.28 megahertz. I have asked whether or not it is spread Spectrum or if it is frequency hopping (they refused to answer) the good solution would be frequency hopping as it would be far more tolerant of RF noise being created in the air locally but I suspect they used spread Spectrum which is more in tune with maximum throughput for Wi-Fi seeing as they only have a maximum of 26Mhz in 902-928 if they are using max channel size (they could move all required data in 6mhz or less including smart vision ), if you’re Rover is a fixed distance from your data center you should be experiencing the same free space loss between the antenna of the DC and the antenna of the Rover pretty much at all times unless something is coming and going in between the two antennas so for the Diagnostics to report wide swings in signal strength that simply has to be firmware issues (DC or Rover) radio frequencies do not do that across so many devices unless there is a problem and then it would occur with a given device not half of the yarbos of people that are reporting the same problem. I’m of the opinion that yarbo is just not dedicating enough CPU Cycles to the RF environment to manage Halow and Wi-Fi and 4G Communications adequately, that’s why things get so weird and at times the Rover gets lost. It would also explain why at times the Rover won’t jump between WIFI and 4g and why support for AP Transition (802.11r) is so poorly implemented.
And with this firmware config, I’m having trouble clearing Map Drift.
1 Like
The rover has different modules and hardware dedicated to each radio as well as dedicated antennas. Cellular, Bluetooth, HaLow, etc all have their own modules and antennas. The computer board also seems to have dedicated inputs for each of those. I don’t think it’s a CPU thing but more of a software hold town timer or some other bug or intentional programming choice. At the end of the day most of the boards are all IOT type devices and IOT inherently doesn’t do 802.11r well or frequency hop between 2.4 and 5GHz well either.
1 Like
It’s a matter of resources.
All WiFi chips supporting the IEEE 802.11 standards since 2009, and 802.11n have the capability of supporting transition (802.11r amendment) including those in IoT, the question is whether of not the developer (Jarbo) has the strengths and budget to avail themselves of the all of the functionality. The alternative is to use a FPGA chip, which can be totally custom programmed, but at Yarbo’s limited volume the cost of using FPGA chips would raise the cost in excess of $1k+ per unit. WiMax 802.16 is still available even though Motorola’s bet on WiMax had a lot to due with their breakup in 2011. WiMax lost out to LTE. I’ve been doing this to long. Remembering this crap reminds me of just how old I am, holy cow.
1 Like