Suunto T3D, Moveslink and Mac

These days I got an Suunto Movestick aka. PC-Pod. This combination is one of the possibilities to get the data of your Heartratemonitor on your Pc. I tried to connect my T3d with Movescount via the Movestick and a Macbook Pro (latest model) with OSX 10.6.6. The T3d shows “PC Transfer” on the clock for a while but nothing happens with the Movescount Software on my Mac…
First I installed the Software in my Bootcamp Windows 7 Prof. and checked this out. This wasn’t working either, so I changed the Batteries of the Watch and then it worked under Win. Anyway the OS X Version of Moveslink was not willing to work.
I found some entries in the Suunto and other forums regarding this issue but no solution was provided. So I started my own investigations and found out that the driver for the Movestick chipset should be the problem. In the Mac console a logentry indicates that the Movestick is recognized, it also can be seen under /Dev/tty.SLAB_USBtoUART, but Moveslink seems not to catch the “connected” event or rather listen to the information provided by the driver. The stick is shown as modem in my Network-connections.
Therefore I tried to install a newer driver, (should be a SiliconLabs CP2102 chip) from the SiliconLabs Website. This driver showed no reaction while trying to connect the Watch with the stick.

After spending an evening I decided to delete all drivers and Software and using VMWare and Windows… I informed the Suunto support – but didn’t get an answer yet.
It would have been too good to be true….

Marmeladenorgie

Durch Zufall habe ich 6 Kg Bitterorangen geschenkt bekommen. Sie sind nur zu dieser Jahreszeit reif und man kann aus Ihnen Marmelade machen die nicht jedermann schmeck. Dafür macht sie alle Glücklich, die BitterLemon und Co. mögen. Da ich schon mehrfach versucht habe bittere Orangenmarmelade zu kochen und sie nie so richtig nach meinen Vorstellungen gelungen ist, habe ich diesmal eine Versuchsreihe gestartet. Hier gehts zu den Rezepten >>

log4j doesn’t refresh Loglevels correctly

I don’t know whether it is a log4j (JBoss 1.2.14) problem or a bug in the Jboss Log4jService URLWatchTimerTask (from JBoss 4.3.0.GA) which i use on my server to refresh the log4j configuration automatically after a change. When I try to  set a higher log level by a base package name, it doesn’t work if formerly a lower log level was set explicit for a class.

Here is an example:

First my machine is configured like this (snip of log4j.xml):

<!-- limit my code-->
<category name="de.koelnerwasser">
 <priority value="INFO" />
</category>
<!-- log a class explicit -->
<category name="de.koelnerwasser.testclass">
 <priority value="DEBUG" />
</category>

Until now everything is fine – all info messages and the debug messages of testclass are logged.  When i change the log4j.xml like this:

<!-- limit my code-->
<category name="de.koelnerwasser">
 <priority value="ERROR" />
</category>

.. and deploy the file to my server, the log4j framework will be reconfigured by the URLWatchTimerTask.

Now only error will be logged and – this is curious: Debug Messages of my testclass . The old loglevel DEBUG will not be overwritten by the ERROR level.  I think this is a little bug of log4j or the Jboss URLWatchTimerTask, i will analyse the code and add a defect to Jboss or Apache.