Re: XGPS160 issues
Posted: Tue May 23, 2017 10:21 am
Please check Known Issues for access to a Dual beta firmware which probably addresses the connection issues discussed.
- Harry
- Harry
It works perfectly for how long? When I had 2.4.1 firmware, the XGPS would connect and work fine for a few minutes. Then the update rate would go to zero.Sonertial wrote:For what it's worth, I just got a new XGPS160 yesterday, installed the Dual GPS Skypro app, Settings -> Check Update -> it updated the firmware from 3.4. to 3.4.1.
You say 2.4.1 above? Is that really the case? If so it'd possibly explain your issue.
The "Supporting an App with old Dual SDK" is set to "No" in my case. Harry's Laptimer works perfectly.
Code: Select all
The changes from the previous version of firmware (v.2.4.2, or v.3.4.2) is as follows:
Fixes SDK Session data stopping for XGPS160 with BC6 chipset when connected to iPad
Changes Bluetooth module Baud Rate from 2Mpbs to 921600bps
Improves iOS Bluetooth search and connectivity after iOS connection is terminated
Updated EIR information in Bluetooth Stack
Limited the number of devices automatically re-connect to one(1) when booting – this should fix/improve the Bluetooth connectivity in iOS/multiple devices
Update reconnect device list save routine
Improve iOS Apple certification process
Good question, well asked as it turns out.gplracerx wrote:
It works perfectly for how long? When I had 2.4.1 firmware, the XGPS would connect and work fine for a few minutes. Then the update rate would go to zero.
I installed the v3.4.5 firmware update, it seems to have fixed my issues.Bryant wrote: What should I try?
Not sure, but I don't think your driver has actually installed properly. Does it say COM 4 STMicroelect... in the dropdown menu? In the Device Manager you should see "STMicroelectronics Virtual COM Port (COM4)".However, now when I try running the firmware updater on my PC, it keeps reporting the following:
Entered COM PORT : COM3
No it was installed correctly. COM3 was what it used the last time the firmware update worked just fine.Sonertial wrote: Not sure, but I don't think your driver has actually installed properly. Does it say COM 4 STMicroelect... in the dropdown menu? In the Device Manager you should see "STMicroelectronics Virtual COM Port (COM4)".
I've done this on both windows 7 and 10, I did notice that when I installed it on Windows 10, there was a prompt that came up behind my active window, the driver did not install until I had found that, despite looking like it had at first, in terms of the notifications that Windows gives you when it's doing it's thing. I think I got a similar message to what you did until I sorted that.