GS-911 and ezCAN User Forum
General Category => GS-911 => Topic started by: NH1200c on February 19, 2023, 09:37:07 PM
-
I have updated my WiFiUSB GS-911 today and Autoscan on my 2020 R1250RT fails after 27~30%. (I have run Autoscan numerous times since my purchase of the GS-911 in 2020 and this is the first time it has failed.)
I have tried Autoscan via USB (my preferred connection type) but it also fails using WiFi.
Thank you for any advice you can offer -
Larry
-
With the issue you encountered lodge a support ticket with help desk https://www.hexcode.co.za/contact-us-1
-
Thank you Wayne, I will do so.
(I was hoping this was a known issue caused by the user! ;D)
Ride safe -
Larry
-
Hi NH1200C
Something to add here, please upload your logs as well when reporting it to our helpdesk, we'll need to have a close comb over on this:
https://www.hexgs911.com/faq/how-do-i-send-my-debug-log-files/
Run a couple of autoscans, but also scan controllers - available from the detected vehicle option > scan controllers.
Check whether all controllers are identified there as well or if not, run a couple of scan controllers and then upload your logs please.
Kind regards
Ruan
-
I have updated my WiFiUSB GS-911 today and Autoscan on my 2020 R1250RT fails after 27~30%. (I have run Autoscan numerous times since my purchase of the GS-911 in 2020 and this is the first time it has failed.)
I have tried Autoscan via USB (how to screenshot on windows (https://howtoscreenshot.co/how-to-take-a-screenshot-on-windows/)) but it also fails using WiFi.
Thank you for any advice you can offer -
Larry
Thanks! Update to the new version 2023 will bring you a better experience
-
Thank you to Ruan and rest of the GS911 team - using Beta software everything completes. Now back to regular winter maintenance of the bike and getting ready for the riding season!
Ride safe -
Larry
-
there should be a new release out soon with lots of tweaks - I've been supporting developers with similar autoscan failures - I'm running a beta release that's fixed theses oddities on two bikes I own...
its to do with comms around the bike - if the bike gets the info later than the tool expected to see it some odd stuff turned up and threw a few spanners in the works... took me a while to realise - do another scan - never clear and you'll likely notice a different result....
next release should rock up really soon