Problem uploading big moves (4Mb)

[Jari09]

I have one 4Mb move in my Ambit and it does not upload to Movescount service. Anyone else having similar problems? The problem from the beginning of July was fixed with previous Moveslink2 update so I should have the latest sw. The move is still in my Ambit and I managed to make a backup of the xml file. Any idea on fixing this? "Upload now" does nothing and log file says just "...error code 3".

[bowesmana]

I don't think there's a size problem, I have several moves over 4MB, largest is 14MB from Jul10 and it's fine, so it's likely to be a data issue. Send Suunto the logs and the XML file giving the problem.

[martowl]

I have one 4Mb move in my Ambit and it does not upload to Movescount service. Anyone else having similar problems? The problem from the beginning of July was fixed with previous Moveslink2 update so I should have the latest sw. The move is still in my Ambit and I managed to make a backup of the xml file. Any idea on fixing this? "Upload now" does nothing and log file says just "...error code 3".

My largest is a bit over 30Mb so I do not think the file size is a problem. There is likely something wrong with the file. You can try to send it to Movescount, they have fixed files previously.

[Jari09]

[16:17:36] [INFO] SyncService: syncDevice Suunto Ambit (6914984618001E00, BluebirdDevice)...
[16:17:37] [INFO] PMemExerciseParser: Number of exercises: 10
[16:18:18] [INFO] BluebirdDevice: saveDevice: Not saving custom modes to device because they are not available (no changes in Movescount)
[16:18:27] [INFO] Arrest: got return code 400 (Bad request)
[16:18:27] [ERROR] SyncService: syncMove failed for move 2012-07-17T18:00:13: error code 3
[16:18:27] [INFO] SyncService::updateSGEE starting
[16:18:27] [INFO] SyncService::updateSGEE size: 74081 bytes, date: 2012-Jul-19
[16:18:27] [INFO] SyncService::updateSGEE found current sgee in device, skipping update
[16:18:27] [INFO] SyncService: syncDevice done (51.000000 seconds)

Above snip from log file. Error code seems to be 3 which sounds very informative :)

[AmbitUser]

[16:18:27] [ERROR] SyncService: syncMove failed for move 2012-07-17T18:00:13: error code 3

Same problem here, logfile contents are:

[19:08:10] [INFO] Komposti v1.2.41
[19:08:10] [INFO] Using config file (...)
[19:08:10] [INFO] SyncService: started
[19:08:10] [INFO] SyncService::downloadSGEE
[19:08:13] [INFO] SyncService::downloadSGEE done
[19:08:44] [INFO] Vendor name: Suunto
[19:08:44] [INFO] Product name: Ambit
[19:08:44] [INFO] Serial: (....)
[19:08:44] [INFO] SyncService: Setting device time to 2012-07-27T19:08:44
[19:08:44] [INFO] Device firmware version: 1.5.10
[19:08:44] [INFO] SyncService: checking for firmware update
[19:08:45] [INFO] SyncService: syncDevice Suunto Ambit ( (...), BluebirdDevice)...
[19:14:40] [INFO] PMemExerciseParser: Number of exercises: 19
[19:17:01] [INFO] BluebirdDevice: saveDevice: Not saving custom modes to device because they are not available (no changes in Movescount)
[19:17:17] [INFO] Arrest: got return code 400 (Bad request)
[19:17:17] [ERROR] SyncService: syncMove failed for move 2012-07-26T08:44:30: error code 3
[19:17:23] [INFO] Arrest: got return code 201 (Created)
[19:17:24] [INFO] Arrest: got return code 201 (Created)
[19:17:24] [INFO] SyncService::updateSGEE starting
[19:17:24] [INFO] SyncService::updateSGEE size: 74081 bytes, date: 2012-Jul-26
[19:17:24] [INFO] SyncService::updateSGEE found current sgee in device, skipping update
[19:17:25] [INFO] SyncService: syncDevice done (520.000000 seconds)

[or_watching]

Hi.
Last week I left my watch on for fun and it created a 16hr 32MB move before the battery died. It uploaded without an error.

Not that I particularly wanted it to upload... but AFAIK it can't be prevented without some fancy file trickery.