Kiteforum.com

Thanks very much for all the help...always thought it a shame that a mature product did not emerge between you and Trace....you both got it pretty right.....and a combo deal with best of both of you would be very attractive...maybe one day....

anyways, hope u keep the website going....

I can confirm the replacement battery thing is relatively easy (I've done it on two devices) so long as you're careful when you reattach/solder the battery leads to the printed circuit board.....but its doable and a battery costs all of $3!

Thx again

ps my.xensr.com seems frozen on the log in screen....can't get past it

might be our crappy internet.....

will keep trying

BrinM wrote: ↑

Thu Jun 11, 2020 2:32 am

ps my.xensr.com seems frozen on the log in screen....can't get past it

might be our crappy internet.....

will keep trying

Should be better now.

Yay, seems back to normal

many thanks

ps small g.earth shots in list view don't always show, no biggie as all data is there it seems.....

again, thx

Hi, every time I try to upload a new session to my.xensr.com, I get an error message, @SessionsApp , can you fix it please?

Many thanks to joriws for posting the python code above. The MyXensr site seems to be down now. So I was determined to find a way to read the Xenrs SESH.DAT files.

I spent some time (quite a lot of time!) trying to decode the Xensr files, using joriws's code. There is now a working version that will generate a GPX file from a Xensr DAT file. Unfortunately I have not yet been able to make complete sense of the data recording jumps, but the GPS part works. The code is free to download from GitHub: https://github.com/science4performance/ ... ENSR-files

gavinf wrote: ↑

Wed Jul 28, 2021 8:14 am

Many thanks to joriws for posting the python code above. The MyXensr site seems to be down now. So I was determined to find a way to read the Xenrs SESH.DAT files.

I spent some time (quite a lot of time!) trying to decode the Xensr files, using joriws's code. There is now a working version that will generate a GPX file from a Xensr DAT file. Unfortunately I have not yet been able to make complete sense of the data recording jumps, but the GPS part works. The code is free to download from GitHub: https://github.com/science4performance/ ... ENSR-files

Thanks for continueing the project. Event-data with jumps are basically quite simple and I've decoded it, and data should be quite ok as there was access to my.xensr.com to compare output. I attach screenshot of event data, maybe it is self-explanatory?

* 2 event types recognized by kite data, "eventJump" 0x01 and "eventEnd" 0x02.
* So decoding of event data is based on this value.
* I am not sure if "Airtime" and "ImpactG" are totally correct in my Hexinator view but I believe it is.
* but in GPX file you could write way points with this data decoded.

Be nice if someone came up with both the hardware and software to give us gps + jumps in a single, easy package

I used both Trace and Xensr, neither perfect, seldom agreed but kinda fun to see where u ride + speed, jumps etc....and pretty well sorted technically apart from leaks!

Now use a Navi GT31, gps tracks and speeds only, can be overlaid on G Earth

But does seem a pity that those relatively mature products aren't made any more...maybe someone will take it up again.....be great if it happens

Latest update....
Many thanks again to joriws. I have further upgraded the Python code and added jump data to the GPX file generated directly from the SESH.DAT recorded on my XENSR device. You can download the code from my GitHub repository https://github.com/science4performance/ ... ENSR-files.
Here are some screenshots

Seems to work ok. Some console deprecated warnings are coming but does not prevent software from running (yet). Great work!

I never really understood IMU data section.
- structure len = 36
- first 4 bytes = timestamp (in tens of microseconds, divide by 100'000 to get seconds)
- not sure if after that is following data (typical or potentional data of IMU devices, also checked from IMU chip datasheet)
* accelerometer raw values: ax, ay, az
* gyroscope raw values: rx, ry,rz
* magnetometer raw values: mx, my, mz
* euler: alfa, beta, gamma
* quaternions: x,y,z,w

But for GPX file output IMU-data details does not really matter.