I was trying to use my sensor today and it seems like it went through some firmware download last night. V 3.13. Tried using it today and it had difficulty connecting and when it did, it did not register anything. I was playing with it in my house for a while and it rewrote the firmware just now. I was surprised by this firmware update so I went on to Flightscope.com to see what was updated and surprisingly, we get the "Low Point" measurement just like TrackMan now!!!!! I believe the software update should be coming soon that will add that parameter. I have not tried it yet, but hopefully I can at least use it. Short indoor mode improvement is made too.
-
-
I don't know if this is a coincidence, but I was having issues with the VX app picking up short shots the other night indoors.
I have an x2 and been mainly using it indoors to work on pitching, wedges and punch shots up to 9i since I have a low ceiling. Never really had issues with it registering shots with either the VX or Skills app. I was hitting 9i 3/4 punch type shots that should have carried around 100. None were registering in VX. Double checked and was set to indoor and all distances were correct. Wasn't even giving me a contact point in the impact radius setup screen.
Started up the Skills app and it was reading shots fine. Back to VX and no go. Then took some full swings and it picked them up.
I didn't update FW since the short indoor stuff was released a month or so ago. I gave up for the night and haven't had a chance to try since.
Sent from my iPhone using Tapatalk -
Is your X2 on v9.18 or v7.17? I tried today and it's not working whatsoever. I know there were few new features like retracting tilt when the sensor is turned off, so it has something to do with the new firmware.Originally posted by Wundej View PostComment
-
I'm on 9.17.Originally posted by CaddyDaddy
When I tried the other day, I had the last version of the Skills app, but whatever the latest version of the VX app was. I wonder if it is a mismatch in app/FW versions. It doesn't seem right, but could be a part of it.
I am probably not updating to 9.18 until I get around to being on a support contract. It is really annoying how unorganized these updates can be. There are things they could do to make the updates less of a risk, and easier to roll back if needed. It saves them $ in development to not do it, but is a nightmare for users when stuff like this happens.
I'll have to give it a try again if I get a chance today.Comment
-
Anyone update their xi/xi+ yet? Want to know what happens. Going on a trip in a few days and bringing the unit so realy want it to work :-)Comment
-
Ok, so long story short, after struggling until 4:30am, I was able to get it working again. I know for sure that my firmware package that was recently downloaded was corrupted during the download or rewrite process. I was hoping that my iPad would automatically fix the corrupted firmware, but it didn't do so because it was indeed, recognized as latest firmware. I guess it was missing some file, so after doing some research, I found out that you can download free PC software trial that included firmware package. Using a firmware writer, I tried rewriting different files through my desktop. I know... This was very risky on my end.
I first tried rewriting the whole v3.13 package, but USB port didn't recognize my sensor connection so it was unsuccessful. Then, I tried rewriting hex files and that was recognized, but during the rewrite process, it failed due to lack of AVR file or sonething. Soon after that, even my iPad didn't recognize the sensor anymore.
For a moment, I wanted to shoot myself because I messed it up so bad that not just my sensor not registering shots, but it wouldn't even connect anymore. This was 4am and I had to work the next day too. I tried connecting with my iPad again and found out that the firmware on my sensor was restored to v1.8 or something. Maybe that was the default firmware. I knew at that time that if I uninstall and reinstall VX app again, it will immediately download the newest firmware, which will be ready to rewrite on the flightscope if it detects older firmware in the sensor. Luckily, my iPad updated my corrupted firmware in my Flightscope to v3.13. It is all good now. I was not able to do this earlier because my iPad recognized the firmware as being the latest, so it will not rewrite it again. I got lucky because somehow, I was able to reverse the firmware on my sensor to something very old.
My take on this mess was due to unstable firmware writing process through WiFi. Next time when you open a Flightscope app and if it says that newest firmware is downloaded on to your iPad, it will rewrite the firmware when it connects with your Flightscope. No choice. At that time, it is important that you keep it close to your sensor and not interrupt the rewrite process in any way.
Can't wait for the next software update that will add lowest point measurement.Last edited by CaddyDaddy; 04-10-2016, 11:22 AM.Comment
-
Ok. Now I'm somewhat concerned. Been a busy weekend and didn't have a chance to check again.
Are you 100% sure it will write the FW when you connect the iOS app after it downloaded the FW to the app? The reason I ask, is that the other night when you asked what FW I had on the sensor I checked via the skills app on my iPhone. When I opened the app it downloaded the new FW to the app, when I connected I got the normal "do up want to update the firmware, Now, remind me tomorrow, or remind me in a week".
I really hate the way the iOS FW update works. They need to use a 2 stage firmware process.
1. First should load the FW from the iOS device onto dedicated solid state memory on the sensor. Once on the sensor, validate the FW checksum and validate compatibility with the sensor.
2. Once it is deemed ready to write, the user should be prompted by the iOS app that FW is on the sensor and would you like to update from V1.xx to V1.19 etc.
from this point the sensor has all the data onboard for the update and you take away any risk of USB, Windows, iOS or wifi issues that could brick the unit.
They should be writing into a memory space that doesn't impede the capability of reverting back to old FW. The way some vendors handle this stuff is just scary. It saves a little bit of dev time, but is so much more of a risk.
On a side note, where did you get the trial desktop software from? I only saw a place to contact support and enter my contact info. I was on my phone though so may have not been shown all the nav details.
Sent from my iPhone using TapatalkComment
-
First of all, what a Masters finish....
Wundej,
I just asked my daughter who was using it when it first started not working. After the first three registered shots, it asked her if she wanted to update the sensor firmware. She said she chose remind me next week. If that was true, it shouldn't have stopped working. But on the contrary when I was trying to fix it that night, it did go through the firmware update. I didn't remember being asked now tomorrow or next week, but it did update. It took a pretty long time too. Either way, that didn't help and that's when I tried searching online to download the PC software that include firmware package and the writer.
Either way, if it did ask you, I might've not remembered correctly. After all, it was 4am and was working on the fix for several hours.
As far as the PC trial goes, you can go onto Flightscope.com and go to PC software under product. Click on Demo and 10 Day free trial is there. I played with the software for a while without actually connecting to the sensor, but it seems like a completely different animal.Last edited by CaddyDaddy; 04-11-2016, 01:10 AM.Comment
-
Does anyone have problem with shots stop registering? Ever since the update, it's been very buggy and unstable.Comment
-
I'm still on 9.17 with the latest updated apps. I wish I had a great place to set this up to test but I'm using it mostly outside into a cage now and it's near impossible to get it perfectly level with my hilly yard. Distances seem a bit off but I think that is mainly due to issues of the radar not being level with my mat. I tried the best I could with a water/tube style level but I am probably off a half to 1 inch. The basement isn't working out because of low ceiling.
I don't think I'm updating again until I get it under contract.
Have you talked to FS? I think they can help downgrade you.
Sent from my iPhone using TapatalkComment
-
Wundej,
Have you tried using your Flightscope since? I'm still having issues, but not as bad where o can use it for a while and it suddenly stops registering. I thought it was my WiFi that's having a problem since the iOS or firmware update. Thinking of trying it out on an Android tablet to see if the problem persists. Funny thing is that when I try to go into settings during the session or relevel, it connects to the sensor again. So far, going into setting and switching back between short indoor to outdoor, back to short indoor seems to do the trick.Comment
-
Last time I used it was about a week ago. It was outside with Indoor Mode into a net 15' away with radar 11' behind (set correctly in the software).
I didn't have issues with it not registering shots. Swing and ball speed looked ok but I think the radar may be a half inch or so too low. Crappy yard makes it tough to get it on the same plane as my mat. Put it on some boards and had to raise it at least 8" to get the water level to be close to level. Carry distances may have been of a bit as well as LA. I'm not extremely consistent with my swing yet so who knows.
Are you under contract? Have you contacted FS?
Sent from my iPhone using TapatalkComment
-
Unfortunately, I am not under any kind of warranty. I did get in contact with techs at Flightscope and they helped me out as much as they could within their limits. They are really helpful and just awsome guys. Initially, I had problems with WiFi authentication issues where I had to constantly put in password as it was like a first time connecting. I don't have that issue anymore, but it sometimes stop registering after half hour or so. I'll just keep messing with it and hopefully by next firmware or software update, it will be fixed. It might be iOS, who knows.Comment
-
I have a flightscope Xi. I am never able to set "Show Measured Data" option to ON. Whenever I set it to ON and go back to the session, it automatically switches to OFF whenever I come back to settings again. As a result my tracer is always yellow line and not red line. However, in the Skills app, I can set the "Show Measured Data" option to ON and it keeps ON and my tracer shows last part of the flight as red.
Has anyone come across this issue before? Running the latest app and FW on FlightscopeComment
-
Why don't you try reinstalling the app if you don't mind losing previous session data. If not, find another iPad if you own one under same account and install it there to see if problem persists. Mine has been working great since.Originally posted by hbfa16 View PostComment
Comment