yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV General] Blaustein:
Hi Fabrizio,

it's quite a big deal to make such a functionality.

And I think noone else but you is using this feature - at least if you must place a wired coil direct on the hr belt.

BTW: I am working on a simple and small amplifier to catch the signals from 1m distance.

On my phone it's no problem to double click the hr before answering an incoming call. Therefore I see no necessity for such a functionality.

A really practicable solution will be by using a bluetooth hr belt.

Zephyr offers a bluetooth hr belt with software developer kit:

http://www.zephyr-technology.com/store/9600.0169.html

If someone likes to by this and make it work with a C# application I will include the code in GCC.

Klaus
[Touch Diamond, MDA Compact IV General] fabrylama:
Hi Klaus,

I understand, thanks anyway.

Fabrizio
[Touch Diamond, MDA Compact IV General] Blaustein:
new beta version 4.9beta9

Hi,

attached the new beta 4.9beta9.

new features in advance of beta8:

- new Format for csv-export in log1.csv

- greatly improved sensitivity of heart rate detection due to digital filtering

Additional suggestion of preamplifier in preamp.png. The amplifier draws his power (max. 0.5mA) form the microphone input if wave device is enabled.

With this amplifier and my air coil (50 turns, 36mm diameter) I can catch the signal from 1m distance. With a single wire loop as antenna with 15cm diameter, the max. distance is 60cm. Proper orientation assumed. Tests made om my desktop with device emulator using sound card. My mobile Asus P320 has a noticeable lesser sensitivity :-(.

With the improved sensitivity it is possible to get the signal with a simple wire loop of about 30mm, placed directly on (or around) the hr belt, without preamplifier.

Klaus
[Touch Diamond, MDA Compact IV General] giasone73:
Hi Klaus

I wrote some days ago to Polar to ask information about bluetooth belt. They are very kind and answered me very quickly with useful informations I think.

I write here the answer of Mr Christer of Polar Electro Europe.

I hope is useful for you.

Hello Alfredo,

and thank you for your additional informations.

Classical Bluetooth from Polar require license agreement, which would not be an option for your group / solution.

Looks like some open source / sw guys / group solving some own issues over internet ?

Do you have some company founded or is it just for fun ?

Well anyway, below more information about the Polar H7

***

There is nowadays a Polar H7 Bluetooth smart product available (since 2nd of April in Retail channel).

This unit works with all Bluetooth smart ready items.

http://developer.bluetooth.org/gatt/services/Pages/ServicesHome.aspx

As of 2nd of April we have started to selling new heart rate sensor H7 Bluetooth smart (Bluetooth v4.0) which is compatible with eg. iPhone 4S.

iPhone 4S is the first iphone which allows to use freely Bluetooth signal.

H7 Heart rate sensor is using standard services ( heart rate-, battery and device information services).

I am sure you should base your project on this.

More information about the Bluetooth services you can find from this link: http://developer.bluetooth.org/gatt/characteristics/Pages/CharacteristicsHome.aspx

***

Sincerely yours,¨

Christer

Alfredo
[Touch Diamond, MDA Compact IV General] CyberDemonVZ:
Hi guys.

Sorry for off topic.

It's time for me to say goodbye to GPS Cycle Computer because I am going to Android.

I wanted to ask, is someone working on transfering GCC to Android? Or is there aplication with similar possiblities for Android?

Thank you in advance :)
[Touch Diamond, MDA Compact IV General] Blaustein:
Hi Alfredo,

the mail from Polar sounds not bad. This guy thinks with his brand new belt it should be possible to make it work due to standardized and published bluetooth service. Nevertheless it needs big work to deal with all this bluetooth stuff. This new "Bluetooth smart" technology may require that your phone supports Bluetooth V4. Especially in case of my old P320 I'm not shure if I can get it work.

I find it a challenging task, but I'm not shure if it will work with my Phone and I don't want to spent 69EUR for a belt which I don't use. (I have a cheap 5kHz hr belt, but don't use it because I find it uncomfortable and hr is not that interesting to me.) Will you buy me a Polar H7 Wearlink? Or do you have any programming skills to make it by your own?

Klaus
[Touch Diamond, MDA Compact IV General] giasone73:
Hi klaus,

I tough about the utility of hr logging and is not so necessary for me but a good value for your gcc. Same of you I don't want spent money for a belt I than I'll use one time and then I put in a drawer :-)

I think you should activate hr logging (on main window) and ask if I want log hr when I start gcc logging only if this function is active from configuration menu whit an apposite checkbox.

In last version this is always active :(.

What about the track2follow altitude graph with my position on it? We spoke about some weeks ago.

Another question: when I load a track2follow can I set my actual gps position as start point? I ask this because some time I start from another position and the distance left to arrive is incorrect.

Tank you

Alfredo
[Touch Diamond, MDA Compact IV General] Blaustein:
Hi Alfredo,

you simply have to disable hr support. Context menu in speed field choose "from gps" (anything but hr).

t2f altitude and statistics did go under on the long list of todo, but now you reminded me.

The distance to destination should always be correct. From the "current position" the shortest distance to the t2f plus this point to the destination along the t2f. The current position is the current gps position if gps is valid or the last valid gps position. If you load a t2f the "current position" is set to the first point of the t2f. But if gps is ON, the "current position" will be overwritten the next second with the actual gps position.

You can also input the current position (and eventual one point t2f = destination) with the menu button "Input LatLon".

Klaus
[Touch Diamond, MDA Compact IV General] pecorone:
hi, I'm trying to use gcc on a navigator mio moov s500. I used NavmanUnlocked to unlock windows ce 5.0 but when I start gcc this message appears "Cannot dind 'GpsCycleComputer' (or one of its components). Make sure thee path and filename are correct and that all the required librarues are available.".

I think missing some dll.

how can I fix this?
[Touch Diamond, MDA Compact IV General] Blaustein:
Hi pecorone,

did you install gcc with the .cab file? Which version? In which directory?

Which exact version of operating system do you have (professional)?

Run Settings - System - Info.

what version of .NET compact framework is installed?

Run Windows\cgacutil.exe to display the version.

Maybe you need to install ".NET Compact Framework V2.0".

Klaus
[Touch Diamond, MDA Compact IV General] pecorone:
version of gcc is 4.9, i copied cab file in flash memory and installed in "My Flash Disk\Program"

OS is Windows CE 5.00 and .NET Compact Framework V2.0 is not installed.

for install .NET Compact Framework V2.0 i extract files from NETCFv2.wce5.armv4i.cab whit MSCEInfIt and i copied it in Windows folder.

now when i start gcc error message dont appears but nothing happens
[Touch Diamond, MDA Compact IV General] Blaustein:
Hi pecorone,

why didn't you install the .NETCF the normal way by simple click (execute the .cab)?

Klaus
[Touch Diamond, MDA Compact IV General] fabrylama:
Hi Klaus,

I did some more testing on the HR logging.. if the HR is disabled gcc works perfectly (as always), if the HR is enabled there are random problems: sometimes the phone soft reset itself, sometimes the signal quality drops to 0, and the only fix is the soft reset and one time the gps stopped reading (no data from gps) and the only fix was the soft reset.

These problems don't happen everyday, more like once every couple of rides, and after at least 30 min from the beginning of the log.

I tried changing ROM, and/or radio on the phone, but everything is the same.

Maybe the phone wasn't build to keep the mic-in open for so long and something overflows?:confused:

Anyway you said you could try to automatically close and reopen the wave device every x minutes, I think it's worth a try...

Thanks again

Fabrizio
[Touch Diamond, MDA Compact IV General] pecorone:
hi, for install .net framework 3.5 I have to reallocate memory but gcc works now. the problem is that when I turn off my navigator windows ce is reset and i have to reinstall .net framework every time.

is there any solution?
[Touch Diamond, MDA Compact IV General] Blaustein:
Hi pecorone,

I think this is a device specific issue, not related to gcc. Perhaps you can find help in any forum of your device.

Can you install .NETCF on the storage card?

Klaus
[Touch Diamond, MDA Compact IV General] Blaustein:
Hi Fabrizio,

I have analyzed the code and found no error, but there is one thing which is not documented how it works in detail. I have made a shortcut in code which is imaginable to cause the problems in some rare cases.

Please test the attached exe (without this shortcut) before I realize such a botch like regularly close and open the wave device.

Klaus
[Touch Diamond, MDA Compact IV General] fabrylama:
Hi, Klaus

I'll test it asap.

Thank you

Fabrizio
[Touch Diamond, MDA Compact IV General] Blaustein:
Hi Alfredo,

attached a new beta 4.10beta1 (only .exe)

New features:

- display statistics and altitude graph of T2F

- performance enhancement on display graph

You can show the statistics of t2f by context menu on button Track2Follow.

Klaus
[Touch Diamond, MDA Compact IV General] fabrylama:
Hi Klaus,

I tested the exe for 3 long rides and so far it worked perfectly.

Thank you very much!

Fabrizio

PS does the new beta with the new features you provided today also implement the HR fix?
[Touch Diamond, MDA Compact IV General] Blaustein:
Hi Fabrizio,

yes, the new beta also includes the HR fix.

Klaus
[Touch Diamond, MDA Compact IV General] petilar:
Is there a way to change Miles to Kilometers?
[Touch Diamond, MDA Compact IV General] Blaustein:
In "Options - Main Screen" right at the top you can select the Units.

Klaus
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello Blaustein / Klaus,

I am running GCC 4.10beta 1. Other than the abnormal termination functionality, I have not encountered any issues with the functionality I have used. Overall the software is excellent and I thank you for it's continued development.

I had an incident whilst cycling recently. The seperate GPS receiver remained on the bike however the Pocket PC detached from the bike and hit the ground quite severely. The impact caused the battery cover to come away and the battery itself to come out of the Pocket PC. Fortunately, there was no real damage done. After reasembling everything and restarting GCC, it asked if I wished to resume logging, I selected yes. Upon doing so, I then noticed the Distance increased immediately out of all proportion. The bike and GPS receiver had not moved significantly at all from the position where I had crashed, so this was unexpected.

I have confirmed this behavior is consistent by cycling a short distance, and then stopping stationary and pulling the battery on the Pocket PC. Even though remaining stationary throughout, the effect was the same. From memory, I think distance was 0.45 miles aproximately at the point of pulling the battery, immediately increasing to 0.78 miles approximately upon resuming despite having remained stationary.

Unless whatever causes this is equipment specific, it should be easy for you to replicate as above. It might be worth some attention before the next beta release.

Let me know if you need any further information or testing.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello low.flying.pigs,

I am out for the weekend so be patient. Can you do another test: Do the same, but choose not to continue and switch gps on (if it is not on) and check that the position on map is stable and at the right place. Then choose continue from the menu page.

Check the track on the map (also for the first test) if there are some irregular points , which can produce this increase in distance.

Have a nice weekend

Klaus
[Touch Diamond, MDA Compact IV General] womisa:
Herzfrequenz mit Sportstracker?

Hi Blaustein/Klaus

is it possible to support the heartrate belt "Sports Tracker" in your program?

've since moved on Android and had long ceased in this forum. But now I have my "OLD" and my bike made ​​696 OLD Asus rolling again and I have a Bluetooth Sports Tracker chest gained the interesiert ....... but no one!

Now to my question:

Is it possible that this is supported by the GPS cycle computer and logged with the GPS log data in conjunction with the heart rate?

Maybe I can contribute to the realization and info since the beta test,

(sorry ich versuche es in Deutsch),

ich habe inzwischen auf Android gewechselt und war lange nicht mehr in diesem Forum. Aber jetzt habe ich mein "ALTES" Fahrrad und mein ALTEN Asus 696 wieder flott gemacht und habe mir einen Bluetooth Sportstracker Brustgurt zugelegt .......das interesiert aber wohl niemand!

Nun zu meiner Frage:

Ist es möglich, dass dieser vom GPS Cycle Computer unterstützt wird und Logdaten mit den GPS-Daten in Verbindung mit der Herzfrequenz loggt?

Eventuell kann ich da infos zur Realisierung und zum BetaTest beitragen,

MfG

Achim
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello Achim,

I suppose you need Bluetooth V4.0 on your phone to support this belt. This also applies to the Polar H7 belt (Bluetooth smart).

Did you try the Sports Tracker application for Windows Phone? Maybe it doesn't work on your Windows Mobile phone at all.

On the support site of Sports Tracker there is the following FAQ:

So I guess it will be impossible or at least very hard to support this HR belt in GCC too.

Klaus
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello Blaustein / Klaus,

Thank you for your reply.

A cursory inspection of the maps reveals no obvious irregular points.

Choosing continue from the menu page also results in distance increasing abnormally.

On the main screen, nothing else seems to change apart from average speed and the odometer.

The effect on average speed seems to be because upon resuming by either method, the time since abnormal termination is added and included to the elapsed time within the 'stop time'. That I presume is by design, and for an abnormal termination event, is probably desireable. If resuming logging of a 'session' however in another circumstance as one would by selecting continue from the menu page, for example resuming ''yesterdays' log for 'todays' leg of a cycle tour, the overnight elapsed time seriously scews the readings. An option whether to include the elapsed time from the end of the log, to the current time when resuming would resolve the issue. Ordinarily I log rides individually. However, if doing a cycle tour or an extended length route / ride over a period of days as I hope to begin in the near furutre, I think I would prefer to record the route as a whole. I don't know however if there are any limitations on log sizes etc.

The odometer has reset, when it had been up to around 800 miles. From observation, it seems it might be becuase the file is written / updated when GCC is terminated, and when termination is abnormal, the odometer distance is lost. Unfortunately, I did not think to check the odometer file before restarting GCC after the first incident. I notice it records some information about the 'exit', usually being 'normalExit'.

There is no particular hurry to any of this from my point of view, I just thought it better to bring to your attention. Let me know if you need any further information or testing. GCC is an excellent peice of software in my opinion, it would be great to see development continue as and when circumstances allow.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello low.flying.pigs;

there was a bug: when restartig GCC, load a track and continue, then immediately the shortest distance between start of track and current position was added to the distance. It should now be fixed but I haven't tested it in real - I think you will do it.

In Versions prior 4.9 tracks was limited to 18 hours but since 4.9 the limit is 68 years, which should be enough.

The odometer should never reset. GccState (with current odo) is written on all major actions (switch on, off GPS; start, stop, pause, continue of tracks; load files and exit GCC. One possibility is a problem with reading the file. Do you have a "LoadState" error in GpsCycleComputer.log? If GCC crashes you should only loose the km since last save of GccState, unless it crashes right in the moment of saving and the file is corrupt.

Attached is version 4.10 beta 2

Klaus
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello Blaustein / Klaus,

Thank you for the information regarding track limits.

I can confirm GCC 4.10beta 2 resolves the resumed session distance error issue, by whatever method the session is resumed. Excellent work.

What are your thoughts regarding an option to include / exclude the elapsed time since the end of the session being resumed within the 'stop time'? If resuming after a few moments due to an abnormal termination for example, it may be desireable. If resuming after an overnight stop for example, it may well not be.

Regarding the resetting odometer, there were a number of errors in my GpsCycleComputer.log file, including load state errors. I renamed the existing file so GCC would start afresh with a new log file and will carry out some further testing. As far as I can tell so far, something causes the gccstate.txt file to be unreadable / corrupted and it is then overwritten by GCC starting again from zero, there being no other storage of the previous odometer value to restore from. I will let you know any findings. If it just happening when an abnormal termination occurs, that is not to much of issue as that should be rare. If not, it may be more significant. Time will tell.

Something that is perhaps more of an issue are the 'pause', 'stop', 'gps off', and 'X close program' buttons. All work as intended and that is the problem, although no fault of GCC, more the practicalities of cycling and the equipment. I wasn't going to bother mentioning this but since it keeeps happening occasionally, this evening being the latest incident, I thought it better to bring it to your attention.

Occasionally, logging gets interupted unintentionally and goes unnoticed resulting in lost logging. It seems to me a 'press and hold' instead of just 'press' for these functions would largely eliminate the issue (perhaps with the exception 'X close program, it not being part of GCC), at least in most situations I suffer. It is probly more elegant than a popup 'do you really want to' type message.

Incidentally, the 'X close program' button for me if pressed whilst logging, shows a breif message 'GPS is logging do you want to exit stop logging' with a yes or no option. It then promply closes itself without waiting for an answer ending logging regardless.

Again there is no particular hurry to any of this from my point of view, have a good weekend.

Let me know if you need any further information or testing.

low.flying.pigs
[Touch Diamond, MDA Compact IV General] Blaustein:
Hello low.flying.pigs,

Thank you for testing. :)

>>option to include / exclude the elapsed time since the end of the session being resumed within the 'stop time'

There are no plans to do anything like this. I think it will be too difficult to manage and it is only useful for a (hopefully) very seldom malfunction or accident.

>> odometer

V4.10beta2 includes a slight change in reading GccState.txt file so that odo is read (and used) even if the file is corrupt afterwards (odo is the first line). This hopefully reduces the cases where odo is lost. You should never have GccState.txt opened in an editor while using GCC, as this could generate access failures.

>>'pause', 'stop', 'gps off' 'press and hold'

I will think about, but it was relatively complex to implement such a function on the left button. And next time the users complain that the button doesn't work reliably. I think I leave it as it is.

>> 'X close program' button ... promply closes itself without waiting for an answer

I cannot reproduce this issue. Which device and Windows version do you use? On my device and emulator it works as intended.

But I have discovered a bug when using Exit button from menu and then choose 'no' to cancel exiting (it exits anyway).

Klaus
[Touch Diamond, MDA Compact IV General] low.flying.pigs:
Hello Blaustein / Klaus

My Pocket PC runs Windows Mobile 2003 SE and GCC 4.10 beta 2.

I can confirm as you noticed that if logging, when selecting exit from the menu, it will await a response, but it will close anyway even if 'no' is selected.

To add to my earlier report, pressing the 'X close program' button on the top right of the main main screen will promptly exit without waiting for an answer, but if you are quick, it will also exit even if 'no' is selected.

Both exit issues seem related, and it seems may therefore actually be the same and have the same solution.

Regarding the odometer, just to confirm I did not have any files open when running / testing GCC.

I will keep observing the odometer for any further problems.

Regarding an option to include as currently is the case, or exclude the elapsed time since the end of the session being resumed within the 'stop time', with respect I disagree about it being only useful for a seldom malfunction or accident. I had already provided examples where both options are preferable, dependent on circumstances. I think, and I may be wrong, that most users on extended rides or tours would want to record only time when 'out and about on the bike', and not 8 hours or whatever of sleep within thier stop time. In the absence of any other solution at the moment, I will just work around this by simply not using the resume functionality at all in this instance, instead logging each day individually, converting the resultant .gcc files to .gpx and then combining all the .gpx files together as a single .gpx for the total route. I will then try to import the combined .gpx into GCC and then save as a .gcc file.

Regarding the press and hold, it is just to stop accidental touches causing unwanted commands, that stop the logging. It could be made an option to choose a 'safety' or not so users have the choice and no reason to complain. Alternatively, a 'do you want to' confirmation request similar to that when exiting would achive the same, avoiding any difficulties implementing press and hold. In the absense of any other solution at the moment, I will either tolerate it or work around this also somehow.

I appreciate the difficulites with software development. If you are willing to provide the current beta sourcecode, I am willing to have an attempt at these matters myself and share any success.

low.flying.pigs