Hi,
thanks a lot for this really great piece of software! I've been using it for nearly 10 years now, converting tracks from more than 400 trips.
About two months back my iBlue 747 A+ started to show the wrong timestamp in the logged data, Sep 1999 instead of Apr 2019. After reading up I found the information about the gps week rollover, so I assume this behaviour has to do with it. Is there anything I can do about it? I tried to run other versions of the software than the one listed below, but couldn't get them to work on the Mac. I saw in the java code that you have a fix for this problem in place (adding 1024*7*24*3600 seconds for certain timestamps) but I can't get this version to work on my Mac.
My current version:
2413 - BT747 2.X.2029 Build:BT747_mdeweerd.2029.20180805010821116
2414 - Initial: 1092x581 Screen: 1920x1080 Final: 1092x581
2414 - Mac OS X
2414 - x86_64
2415 - 10.14.5
2415 - 1.8.0_211
2415 - 64
2415 - Fail com.apple.mrj.swing.MacLookAndFeel
Success apple.laf.AquaLookAndFeel
javax.swing.plaf.metal.MetalLookAndFeel
javax.swing.plaf.nimbus.NimbusLookAndFeel
com.sun.java.swing.plaf.motif.MotifLookAndFeel
com.apple.laf.AquaLookAndFeel
8523 - Classgps.connection.GPSRxTxPort
8551 - Port opened
8554 - Attempting saving settings to /Users/axel/BT747SettingsJ2SE.pdb
8555 - Writing settings success for /Users/axel/BT747SettingsJ2SE.pdb
Which version that contains the fix can I run on the Mac?
Thanks for your help!
Best regards
Axel
I recently released V2.2.1 which has a workaround for this GPS issue.
It will adjust the recorded date if it is earlier than 2009 or so.
If you have difficulties running this package on your mac, we have to find out what is missing versus the earlier packages. I've changed a few times my PC so there may still be some tunings to do to the build process.
Normally converting a downloaded file should work, I only expect issues with the USB setup.
You can also launch the SW from https://soft.bt747.org/ .
Mario
This is an old request, the notification possibly ended up in SPAM.
I checked the JNLP startup files and they refer to the same application files. There may be some kind of caching issue.