Hi, i followed the instructions to update the Zed module. The program ran, and update completed, but in the restar receivers shows 0000 in the mac adres, and while i can enter config mode via wifi, can’t do anythiing. I followed the guide exactly, any helP?
Unit is totally dead. Also im having issues with the other one, it doesnt hold charge state via config ublox conector, onlu config 32.
Update: I was able to revive it, pressing several times power. Later i updated choosing override, program ran, like nothing happened, and later after a restar unit was update to HPG 1.30, now the unit sees fewers satellites.
I was able to update to 1.32 following PualZ advices, overriden and erasing but the unit is acting weird. I notice, that when i coonect the antenna the unit starts acting, only power ups with usb cable connected. Also display freezes, shows rare or deformed icons, battery goes to empty to ful bars, that things was doing wit factory firmware. Right now the unit only powers up ocassionally, with usb attached, can’t use normally, is dead. A put the links below of the videos in youtube, since i can’t upload them here…
Just to sumarize. I have two units. The first one, i update because i was having issues with screen freezing, battery going to zero and going back to full, precision numbers freezing, hats why i opted to update first the esp 32, and later the ZED chipset, i thats when i ran into the issues described. At the mommento, the unit is at 1.32 in zed chipset, and esp 32 in 3.2. The unit is able to get RTK fix, even tho the freezing continues, i don’t know if this is normal. Also i have had bad RTK fix near a wall, I measured 2 times with rover and 2 times with long tape measure and the error was around 8 cm. YEs it has a wall, but it is has a very clear view of the sky sinceim in the roof, hopefully someone can confirm this is normal.
The other unit, that i use a base, is working normaly, updated to 1.32 in the ZED chipset, and 3.1 in the esp 32, the issue whit this one is the charging state not maintaing when doinf throu config ublox connector, im hoping someone reach to me.
Thanks for reading me.
Please consider returning the units for inspection: https://www.sparkfun.com/returns
Also display freezes, shows rare or deformed icons, battery goes to empty to ful bars,
This seems to indicate a problem with the I2C bus. The display, battery fuel gauge, and accelerometer are all on the same bus. If the accelerometer becomes defective it can cause problems with the all the other I2C devices.
Also i have had bad RTK fix near a wall, I measured 2 times with rover and 2 times with long tape measure and the error was around 8 cm. YEs it has a wall, but it is has a very clear view of the sky sinceim in the roof, hopefully someone can confirm this is normal.
Be sure you are converting between correct reference frames. See https://docs.sparkfun.com/SparkFun_RTK_ … rification
That sounds great, but are you going to send me a prepaid guide or how u manage refunds. Also please let me know how you are going to send thetas (invoice) because i already país 300 dollars from taxes , and i dont pretend to Pay again from something that came without Quality control and Its not my fault.
sparky:
Please consider returning the units for inspection: https://www.sparkfun.com/returnsAlso display freezes, shows rare or deformed icons, battery goes to empty to ful bars,
This seems to indicate a problem with the I2C bus. The display, battery fuel gauge, and accelerometer are all on the same bus. If the accelerometer becomes defective it can cause problems with the all the other I2C devices.
Also i have had bad RTK fix near a wall, I measured 2 times with rover and 2 times with long tape measure and the error was around 8 cm. YEs it has a wall, but it is has a very clear view of the sky sinceim in the roof, hopefully someone can confirm this is normal.
Be sure you are converting between correct reference frames. See https://docs.sparkfun.com/SparkFun_RTK_ … rification
This seems to indicate a problem with the I2C bus. The display, battery fuel gauge, and accelerometer are all on the same bus. If the accelerometer becomes defective it can cause problems with the all the other I2C devices.
Sparky, this issue with the I2C bus can affect chipset performance? im getting good rtk data, in general, but i had shot some points that differs 5-9cm, i know what im’ doing in terms of survey, i know my datums, transformations, factors scales etc, i actually work with globbal mapper where u can treat the data very well, but it was strange. In my tests at 50 meters im around 1-1.5 cm off compared to tota station , and i agree because im withing specs, but using the equipment around 30 minutes later i start to get reading off like i said by 5-8 cm.
I’m gonna need the unit for a real project tomorrow, and actually thats why i was desperate and i need to say angry, hopefully i can be abble to get the job done.
Be sure you are converting between correct reference frames. See https://docs.sparkfun.com/SparkFun_RTK_ … rification
[/quote]
Thanks, i’m aware of this, i assume it was multipath even tho the enviroment did not appeared challenging.
Thanks, i’m aware of this, i assume it was multipath even tho the enviroment did not appeared challenging.
You are likely correct. Doing RTK in any environment other than clear sky will degrade performance. 5-9cm of error next to a wall is likely the issue.