I have charged up the GW-60 and set the settings as suggested in the quick start guide of a non window computer however, my mac does not recognise the device. It will charge, but it will not recognise the device and any stored files.
Help!
Bart
There may be others more familiar with this. I have a MacBook Pro, but I actually download using windows in emulation.
I just connected it though, and here is the method I used:
Go to settings. (Adjust button)
Scroll down to the 'usb class COM' item. (Start button = Up Reset button = down)
Press Adjust and Change it to 'USB class UMS'
Scroll down one place to 'USB MSC'
Connect cable
Press Adjust again and it should show that it is connected in the watch.
Wait a minute or so for the drive to appear on the desktop.
Double click on it to open.
Drag GPSLOG.SBP in it onto your desktop.
One more vital step: click in the GPSLOG.SBP file and 'get info'
Now untick the 'locked' box so you can open the file and save it.
Give the file a date and save it.
Analyse in you favourite program. Done. ![]()
Hope this helps.
So do you see the connect to computer icon on the GPS display, when you press, "TO USB MSC"
Yes I get a message on the screen to connect the USB cable.
I have connected the USB cable from watch to MacBook, however the mac does not show it as a drive........
Press adjust again. ![]()
still no go, I wonder if the cable is shot? however it does charge the watch??? Just can't get the mac to recognise the device at all.
It's more likely to be dirty contacts on the watch, give them a good wipe with a clean damp cloth.
still no go, will take it back to Simon (board crazy) and see if he has a theory. Might be a good thing, I think my top speed today was embarrassing!
Same problem here.... You just have to wait LOOOONG enough - it may take upto 1 hour before it appears on the Mac?s screen - but it will be there. And when it appears there you?d better act fast as it?s gonna disconnect very soon by itself but it will be back again if you just keep waiting.... You dont need to touch the cable nor GW60 as it will not help at all. YOU JUST KEEP ON WAITING. I accidently found this as I left the GW60 connected to my Mac Book Pro while I was surfing on the net and suddenly pop-up came on the Mac?s screen saying "Your devise was not properly disconnected..." Then I knew it has been connected into it while I was surfing....so then I just kept watching and tadaa the GW60 was on the Mac?s screen. Yes - it?s really annoying - feel to hammer this Mac. I have been asking Locosys to make a Utility for the Mac for nearly 2 years ago but haven?t seen it yet - and they just told me (I told them about this problem too) that they haven?t started it yet....
Before my GW60 worked well with this Mac, but the problem started to happen about few months ago. I dont know if it?s because of iOS update or GW60 update, but that I know that this issue makes me really pssd off.
If you have a chance - try to connect your GW60 to a windows laptop - if it works just like that then you can be sure that the problem is the Mac... I don?t have a windows laptop (as I hate windows) so I cant try...
Thanks and cheers
Same problem here.... You just have to wait LOOOONG enough - it may take upto 1 hour before it appears on the Mac?s screen - but it will be there. And when it appears there you?d better act fast as it?s gonna disconnect very soon by itself but it will be back again if you just keep waiting.... You dont need to touch the cable nor GW60 as it will not help at all. YOU JUST KEEP ON WAITING. I accidently found this as I left the GW60 connected to my Mac Book Pro while I was surfing on the net and suddenly pop-up came on the Mac?s screen saying "Your devise was not properly disconnected..." Then I knew it has been connected into it while I was surfing....so then I just kept watching and tadaa the GW60 was on the Mac?s screen. Yes - it?s really annoying - feel to hammer this Mac. I have been asking Locosys to make a Utility for the Mac for nearly 2 years ago but haven?t seen it yet - and they just told me (I told them about this problem too) that they haven?t started it yet....
Before my GW60 worked well with this Mac, but the problem started to happen about few months ago. I dont know if it?s because of iOS update or GW60 update, but that I know that this issue makes me really pssd off.
If you have a chance - try to connect your GW60 to a windows laptop - if it works just like that then you can be sure that the problem is the Mac... I don?t have a windows laptop (as I hate windows) so I cant try...
Thanks and cheers
Right, tried a friends PC and we are in business! Now I know that it is the mac. thanks for the help.
So you changed it to "com" mode and used the utility, or did you stay in "MSC" mode and connect as USB storage?
I'd try doing that before condemning the Mac, there may be something else going on here.
So you changed it to "com" mode and used the utility, or did you stay in "MSC" mode and connect as USB storage?
I'd try doing that before condemning the Mac, there may be something else going on here.
Yes, changed to com mode. It appears macs and the GW-60 are not compatible. Would be happy to be proven wrong.
Well in general you are definitely wrong, there's quite a few people using GW60s with Mac's quite happily.
That's why it would be instructive to try you're GW60 on a PC in MSC mode.
And also if you have another mate with a GW60 does that talk to your Mac.
It'll be a bugger if you have to download at a mate's place all the time!
If there's something wrong with your GW60 in MSC mode, it should be replaced under warranty.
If there's something strange going on with your Mac, that can probably be sorted as well, (not by me though)
I'm using a pretty cheap Windows tablet. Maybe worth buying one for the GW-60, I reckon the watch cost more than the tablet.
Yes, changed to com mode. It appears macs and the GW-60 are not compatible. Would be happy to be proven wrong.
Definitely NOT. That is wrong. Mine works fine on the Mac as does a lot of others I know.
And to troublemaker, That is not normal behaviour on any Mac. It is probably a bad connection on the watch cable clamp.
Santa got me a GW60 and I connect to a MacBook Air, I don't find it that reliable, it sometimes doesn't show up straight away. Once I have copied the log file I was deleting it via Mac File Manager but last time I did it said the GW60 was corrupt and I could not. Since then I have been deleting the log file via the GW60. I am running Yosemite on the Mac at the moment but will upgrade when I have some free time.
And to troublemaker, That is not normal behaviour on any Mac. It is probably a bad connection on the watch cable clamp. Well, why does it work if I wait long enough? I did not touch the cable nor GW60 - they were all still. I would understand if the cable is bad or connection if I could make a connection by touching those but I didn?t touch them. No one moving them so if there is no connection it cannot have a connection itself, so it must be programme issue. Mac doesn?t want to communicate with GW60 or GW60 doesn?t want to communicate with Mac...It is no matter how much I tried to touch/press those things - it didn make connection. Just wait long enough and it works...It does not send a signal or it doesn?t want to receive the signal...it does it whenever it likes. I use High Sierra iOS in my Mac and V1.2a0314B in my GW60.
So you changed it to "com" mode and used the utility, or did you stay in "MSC" mode and connect as USB storage?
I'd try doing that before condemning the Mac, there may be something else going on here.
Yes, changed to com mode. It appears macs and the GW-60 are not compatible. Would be happy to be proven wrong.
Make sure you upgrade to the most recent firmware using a windows machine. Should work fine with a Mac after that.
Make sure you upgrade to the most recent firmware using a windows machine. Should work fine with a Mac after that.
Thanks Andrew, I forgot about the "Mac" firmware update.
Right, tried a friends PC and we are in business! Now I know that it is the mac. thanks for the help.
I'd phrase it a bit different - it's poorly implemented support for the Mac. I often get the error message "The disk cannot be repaired" when connecting a GW-60. That's a clear indication that Locosys implemented the "UMS file system" in a non-standard way. Since the "disk" is write-protected, forgetting to eject the disk before disconnecting cannot be the cause (and definitely is not, since I often see the message pop up after ejecting the disk properly before).
But this error message is just a small annoyance, others are worse. Every now and then, a watch will simply not mount on the Mac. That's rare, but happened to me just yesterday. This is with the newest firmware versions installed, and otherwise completely random. So far, switching to COM mode and downloading from a Windows virtual machine instead has worked (although that download often stalls, and requires multiple attempts). At other times, I have had problems with the GW-60 in COM mode not being recognized by Windows running as a virtual machine on a Mac, or data downloads timing out every single time in many repeated attempts. So far, switching back to UMS mode has usually worked in these situations, although I have at times also resorted to using a Windows computer for the downloads.
Just tested my GW60 with my wife?s company Windows laptop... It was connected instantly, but NOT IN COM mode!!! In COM MODE it did not work. When I selected MCS MODE and pressed TO USB MCS it worked every time - I saw even my track file :-) SO THE CABLE IS OK! But the GW60 has some firmware problem as it should not work in MSC mode with Windows, right???
It should also work in MSC mode in Windows. You just can't do stuff like deleting the old data in MSC mode, and the file on the device will always have the same name, instead of a name with the download date etc. if you use the utility program.
Good to know that it is to work in MSC mode with Windows. At least the cable is not faulty nor the connection pins of the GW60 so not to suspect those anymore...So left MAC and software of GW60...
Good to know that it is to work in MSC mode with Windows. At least the cable is not faulty nor the connection pins of the GW60 so not to suspect those anymore...So left MAC and software of GW60...
Correct.
So did you update the GW60 firmware? And have you tried another GW60 on your MAC
Just updated my GW60 - now I have the firmware V1.3A0926B installed in it and NOW, IT WORKS WITH MAC
. So it was that old firmware V1.2A0314B that caused people like me very very very angry
...
Just updated my GW60 - now I have the firmware V1.3A0926B installed in it and NOW, IT WORKS WITH MAC
. So it was that old firmware V1.2A0314B that caused people like me very very very angry
...
Yep, sorry about that, it should have been my first suggestion!
But that's what comes with being an old fart, important stuff, just slips away---------------
Guess what....it was just an accident that it worked immediately after connecting the cable..so now it is back to the normal that it does not work immediately...so, again I have to wait for long long time that my Mac finds my GW60. Anyways, with Windows laptops it works well...I think I will buy a Windows lap top for my GW60.
Here is what I think is going on:
When mounting a USB drive (including the GW-60 in UMS/MSC mode), the Mac OS always checks the file system, and tries to correct any problems it finds. For the GW-60, it sometimes shows an error message "Cannot fix errors", but copying the data works just fine. At other times, the watch mounts right away without problems. But sometimes, the watch does not show up for a very long time, and no error message is shown. Apparently, the OS keeps trying to repair the disk, even though it really can't since the disk is write-protected.
This problem does not occur on Windows, since Windows does not automatically check USB file systems when mounted (or if it does, it gives up quickly).
There is a potential workaround for this problem described at apple.stackexchange.com/questions/230698/disable-the-disk-check-when-reconnecting-an-improperly-disconnected-disk-to-os-x . The first suggestion in the post will not work, since the watch does not seem to have a UUID. However, renaming /sbin/fsck_msdos should work if the analysis above is correct. The side effect would be that no MS-DOS (FAT) formatted drives can be checked or repaired; that would affect most (or perhaps all) USB sticks.
I tried to verify that renaming the /sbin/fsck_msdos file would work, but right now, my ac sees all my three GW-60s without any problems. Which suggests another way that might get the watch to mount: turn it on, an let it record for a few more seconds, stop the GPS, and try again.