App and website: Trips dates incorrect.

[Romkabouter]

Hi there,

During my latest trip I have tracked some runs. The app shows incorrect data. The trip was in Austria and on separate days. It also show 1 run, which is not correct.

The website shows the tracks in the correct position, but dates are incorrect.

When I use the RIB to gpx exporter, I can see a timestamp per trackpoint:

I think it is save to assume that the first trackpoint can be used to extract the location and date metadata.

Is the app a complete rewrite of the original Engage App?

[recom3]

Good day Let us check. Yes maybe the country is wrong as the main focus was to extract correct data of elevation, gps data, etc. The time we will check too. This Uplink Desktop is new. Regards.

[recom3]

Ok we will fix it and there will be also a mechanism to fix the already uploaded trips.

[recom3]

Working in the fix. We have to update a little the current api, but will be ready soon. We will use this time to update the Uplink Desktop feed-back too.

[recom3]

Fix deployed for Country to API

[recom3]

Fix deployed to Uplink Desktop app. For existing trips we will leave them as they are, possibly correcting country with one shot update. From now on should be correct.

[Romkabouter]

Fix deployed for Country to API

Should I redownload and install the app?

[recom3]

No the phone App is OK is taking data from the api, should be ok. You need to download the Uplink Desktop to be able to upload corrected data (new trips).

[Romkabouter]

OK, I'll check it!

[recom3]

We have included the country in the Web too.

[Romkabouter]

You need to download the Uplink Desktop to be able to upload corrected data (new trips).

I have downloaded a new version and then uploaded new tracks. Two issue

• tracks are double (1 with correct country Germany)
• Dates still incorrect, I have uploaded them today (13-03), but the trips were 11-03 and 12-03

[recom3]

Ok thx we will check

[recom3]

They are not repeated. Probably there is a small bug in Uplink Desktop that prevents obtaining the datetime from tracks format 1 (probably you have and updated Snow2, not the factory one, that uses format 2 - Transcend) Then when uploading the trip the program asigns: Trip yyyy-MM-dd HH:mm Should be maybe Trip yyyy-MM-dd HH:mm:ss, when is impossible to obtain the datetime from track. We will fix in any case. Many thx!

[Romkabouter]

robably you have and updated Snow2, not the factory one, that uses format 2 - Transcend

My Snow2 is on the latest ReconOS4.5, I believe the version before that was 3.2.1

[recom3]

Fixed with new version of Uplink Desktop. Now datetime should be correct. In any case, in future, in web site will be possible to edit trip names to put with more meaning for the user. Thx for the feed back.

[Romkabouter]

Ok, so this is for new track only right? If so, is it possible that you can delete my tracks so I can upload new ones?

[recom3]

I think that can be done. From which track/track id do you want to delete?

[Romkabouter]

You can delete all of them, wo whenI synch the Snow2 they should all popup again right?

[recom3]

Yes sure. When ready I will send a private msg to give further instructions.

[recom3]

Hi,

Done deleting your trips.

Look for this path:

C:\Users\\AppData\Local\Recon Instruments\recom_pref.json

Create a copy of the file (just in case anything fails).

Search for this in the file with text editor (I assume your unit id is 283332129):

..."Unit":[{"Id":"283332129","MaxRib":0}...

Set MaxRib to 0, this will force to upload all the trips again.

Regards

[Romkabouter]

Sorry guys, but this is not fixed. I did update the MaxRib with zero, but now the trips have several issues:

• dates are not from the trip, but the upload date
• all trips are the same on the map
• multiple duplicates

I have no issues with you deleting my data and to try it again if that helps.

Search for this in the file with text editor (I assume your unit id is 283332129):

This might be a cause: I actually have two devices {"Id":"283332129","MaxRib":352},{"Id":"291952246","MaxRib":0}]

[recom3]

This is normal you have two devices. Have you downloaded the last version of the Uplink Desktop? If not, we will delete the trips again no problem. You can download again de Uplink and re-try.

[recom3]

Trips deleted again.

[Romkabouter]

Thanks, I have used this version:

I have set the MaxRib to 0, but also deleted the RIB files (also ID.RIB) on AppData\Local\Recon Instruments\

Same result, the name is the upload date, while I expect the tripdate. Country is correct, but there are too many trips Also, all trips are the same track. The first track.

My expectations is 1 entry per day, which can be a combination of multible rib files. For the moment I a fine with 1 entry per RIB file, but this upload seems to have a lot of issues.

[recom3]

Ok we will double check. Maybe the release not correctly pushed to server and is old. In new version trips should be at least ...hh:mm:ss... Sorry for that

[Romkabouter]

No problems, happy to help :)

Just let me know what the date on the executable should be and delete my trips

[recom3]

We are going to double check the code and produce a new version in the exe so can be easily checked.

[recom3]

Maybe the RIB format in your version is somehow different. Could you please upload one.

[Romkabouter]

Sure, the are in https://romkabouter.stackstorage.com/s/lmwQDS1MpVZqp9eR (RIB folder) I have uploaded 3, also the generate gpx file from 300. When I check that, the data look find to me (lat/lon/speed/date etc) so I think the uplink is generating the gpx ok.

The graph looks good as well

Was there a good as to why this conversion is done locally and not on the server? The RIB files are much smaller to upload. I think the issue is on the server and not in the uplink

[Romkabouter]

I you can delete my data again, I will remove my local (test) track from the device and only upload the real trips. Also, it would be a good reference on the site of the RIB number was visible, that way I could check if it is correct

[Romkabouter]

Hmm. I see a lot of RIB files on there which is not a day. It looks like the device is also creating RIB files when not actually tracking (Start Day), but always when GPS is on. I am gonna look into that. That would be a reason for all the tracks in NL, because the device is sitting on my desk. Might be caused by the fact I have the setting GPS Always on to true.

[Romkabouter]

Might be caused by the fact I have the setting GPS Always on to true.

100% that is the issue here. When GPS is always on, the Snow2 generates RIB files even if there is no activity being tracked. When it is off, no RIB files are generated. So maybe there is some trick with EVENTxxx.RIB, cannot tell

[recom3]

I think a silly bug in in the code producing the trip name... We will produce the version 1.1 and be back.

[recom3]

Trips deleted and new version of Uplink uploaded again When you download, please click in the exe and check is 1.1 like this:

[Romkabouter]

Used this version:

Same issues, names are upload date and it looks like last trip is copied to all other trips.

[recom3]

Mm it is very strange. We have tested your RIBs and working fine, must something else. We will check other modules, maybe is not in the decoder. Be back soon.

[recom3]

Good day, Should be fixed. We have found another small bug in Uplink, so we have released the 1.1.0.1 (plz download it) and also we fixed the API.

[Romkabouter]

Thanks, dates are correct so that is a step forward, but it still looks like the last trip is duplicated to all tracks Below I have selected trip in Austria, but all the trips look the same (seems to be the first track but I cannot tell the upload order)

Also, on the folder there are 4 trips:

But after setting the MaxRib to 0 I would expect 10 because of the files on the devices are:

[recom3]

Sorry. We forgot to delete your tracks, shall we do it, so you can retry?

[recom3]

The device can store a lot of RIB's sometimes. You can check, if it anything meaningful with the file size. There is a cap in file size, below which trip is not uploaded.

[Romkabouter]

Sorry. We forgot to delete your tracks, shall we do it, so you can retry?

Yeah sure :)

The device can store a lot of RIB's sometimes. You can check, if it anything meaningful with the file size. There is a cap in file size, below which trip is not uploaded.

I have removed all nonsens trips. The filesize of DAY287 is 440kb and not uploaded. The filesize of DAY336 is 322KB and ís uploaded. So if there is a cap, which makes sense I guess, there is something out of order there.

My smallest file is DAY295.RIB, but still a valid track. A short one, probably the battery was dead

[recom3]

Deleted. The cap is small 10000 bytes. Let's see what happens this time.

[Romkabouter]

I have used 1.1.0.1 but that does not seems to have any effect? Should there have been a new version?

[recom3]

1.1.0.1 is the last version yes. There was an issue in the API with the naming that was corrected yesterday. How many Trips were uploaded? Was the naming OK?

[Romkabouter]

Ok good. The naming is ok, but the same 4 trips were uploaded so I am missing 6. Also all trips look the same on the website, see my previous screenshots

[recom3]

Was the maxrib updated in the prefs json file?

[Romkabouter]

Yes, otherwise the trips would not have been uploaded at all I assume

[recom3]

So only 4 trips appearing in the grid below the map right?

[Romkabouter]

Yup, and they look the same as well which is not the case. I cannot tell if that is a database problem or a rendering issue.

[recom3]

Ok we check. Click in the Track id to render, in the grid. We see an issue here.

[recom3]

We see in DB trips from 136 to 139 including both. Can be the other trips are uploaded with Recon Jet glasses or other unit?