No the drivers remain installed without any issues.

Has he tried the "factory restore" under settings yet? My Linux guy said that 'should' remove the files... I'm however a little dubious that it removes all the hidden files.

....the plot thickens! Don't you just love technology!!

I've had the same issue with my Canmore(Blue One)
I managed to overcome the problem by -
On Mac
Copy the two files "GP-102 & No Name" to the desktop
Using Disk utility select the Canmore flash drive and erase all the data
Once the drive has been formatted re-install the two files it should show the capacity is back to 3.1 MB
I have taken it out for a number of times since and all appears normal

Now if only i can get it to crack 40knts !

works now - on off button isn't real great - even the importer said it was crap.

It has come to our attention that some (or all?) Canmore devices are occasionally randomly missing data points during runs. Usually from what we have seen it is missing one second (making a 2 second data point) but sometimes it misses 2 seconds. There may be instances where more are missed.

This is a big problem because you can't really span missed points in Doppler data because of the potential aliasing errors it can introduce. (Not such an issue with Track Points, but they have accuracy issues of a different kind)

At the moment, KA72 speed checker incorrectly allows these points to be spanned. If you post to GPS-Speedsurfing or use GPS-Results you will notice that it invalidates any run with these missed points and they don't show up in the results.

I would be interested to hear from Canmore users if they have noticed this with their device. It may only happen if the device is worn so it has poor reception, or it may only affect some individual devices, but we need more info on this.

sailquik said..


I would be interested to hear from Canmore users if they have noticed this with their device. It may only happen if the device is worn so it has poor reception, or it may only affect some individual devices, but we need more info on this.

Andrew,
We have noticed lately some spikes or longer points in the tracks, up to 9 seconds and just random.
I might have a look & se if they are at a particular time span & or regular.
This has been happening even when not moving.
Initially I though it could have been shadowing as it usually happens when facing a particular direction.

We haven't bothered about it too much as the the wearer is not getting any where near PBs or world records

Luckily we look at tracks in Realspeed and can easily see any errors, KA72 seems to be giving the same results so that would indicate that the errors are getting through.

decrepit said..
I spoke to yoyo today, he thinks it's a write speed problem, something to do with the memory being organised in blocks, when one block is full another has to be started, this too long for the next second to get written to memory.

Yoyo also says, that if he converts the canmore file to .sbp with realspeed, GPSResults then recognises a result with a gap in it.

Is it able to be minimised in some circumstances like clearing the memory completely and having it empty to start?

What is the frequency observed Yoyo and is their any pattern to it?

If that theory is correct, a firmware update from Canmore might fix it.

Is there a firmware up date available? Mine doesnt seen to show or indicate the firmware version installed.

Skylander,
Pros, cheap, good satellite sensitivity, and seems reasonably accurate. reasonable battery and memory life
Cons, very small screen extremely hard to read on the water! No accuracy info is stored so speeds can't be verified. Only reads in km/hr. Every so often it skips a second, this trips the filters in some analysing software.

skylander said..

There also seems to be a rumour/myth going around that the yellow units are more prone to the "memory full" issue. Is this true? Or is this attributable to the corrupted file system which is amenable by a disk format?

I think this rumour is attributable to corrupted smart asses (incl me )

They all work the same, whatever the colour, just make sure you empty the memory every now and then.

decrepit said..
Yes, if the memory block theory is correct, you'd expect the gaps at a regular interval

I've just checked one of Stretch's old files, and it's certainly not all that regular and the missing bits come in clumps, here's the times a 2s gap appears.

1244.11, 1247.10, 1248.05, 1248.08, 1248.14, 1248.16, 1248.19, 1248.21, 1248.37, 1255.39. 1255.45, 1255.47, 1255.50, 1255.57, 1300.52, 1302.16, 1303.21
1303.26, 1303.29, 1303.31, 1303.38, 1303.41, 1303.48, 1303.51, 1303.58, 1304.01, 1304.08, 1304.10, 1310.18, 1310.23, 1310.26, 1310.28, 1310.31, 1310.50

Does that blow the memory theory?

No, it is the memory thing.
Tested a yellow unit myself, but it died pretty quickly due to several design flaws.

There are dozens of websites about this: en.wikipedia.org/wiki/Write_amplification
The chip is just not fast enough and the memory is very cheap.
Due to the memory housekeeping the error shows at random moments.
I've seen million dollar systems on there knees due to a cheap SSD...

In the Netherlands we have a topic about the Suunto and Garmin watches.
forum.windsurfing.nl/viewtopic.php?f=65&t=13885643

sorted ….. just plug it to the mac directly…. …no USB hub, even powered...

Well I don't seem to be having any luck at all with my Canmore. New problem is works fine while on the water, however when I get home to download the file it just reads all zeros. I have done a factory reset and went for a bike ride and still the same. I have no idea what to do except buy something that will be more reliable.

I had an issue with my canmore watch, did just like you Gustenzo, worked a treat.

Main thing is to think of clearing the memory regularly.

No problem Tinlyds, although I can't claim credit. I have pretty reposted what others have already written . Glad it worked for you