<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Thanx guys,<br>
for all the comments.<br>
<br>
@Linus<br>
We are using the USB-CDC package from ST for our STM32F4. It comes
with a driver for the PC that make a COM port, for linux it should
work the standard linux kernel !? At the moment it is ok for us,
but I am looking for a way to have the USB also work with PCs
standard driver config.<br>
<br>
@Robert<br>
My kids are studying in Munich, may be we can meet in the next
weeks. The housing of oDiCo is made from plexiglas version 0.1 and
filled with silicon oel. The next housing 0.2 will be milled from
POM and the electronic will be an industry factored PCB. Awating
to have it in the lake in June ...<br>
<br>
@Davide<br>
@Dirk<br>
I had also the idea to implement the dive computer as USB mass
storage, but there a some more things to consider. In the moment
we are looking for a straight forward way. Because serial is
running already we prefer to use a already available protocol like
the "SeaBear", you've mentioned. We use the STM32F$ USB port
without additional electronic, so we are open for further
improvements.<br>
<br>
Any idea were I can find that SeaBear-spec in the mailing list, or
just ask Miika ?<br>
<br>
Thomas<br>
<br>
<br>
Am 12.03.2015 um 19:41 schrieb Gabriel Rossetti:<br>
</div>
<blockquote
cite="mid:CAA5x6WxcM2NDBy0wEvZtNzFmmGc8xMFT8aJhSpcHjFDatQqz6A@mail.gmail.com"
type="cite">
<p dir="ltr">This is interesting, I was starting to research on
how to do that, what kind of board, sensors, screen, etc. I
wanted one that vibrates, wireless charging, nfc or bluetooth
and has a rechargable battery (for freediving). I will look at
you link later.</p>
<p dir="ltr">Good luck, I will follow your advances.<br>
Gabriel</p>
<div class="gmail_quote">On 12 Mar 2015 18:46, "Thomas Schrein"
<<a moz-do-not-send="true" href="mailto:thomas@schrein.com">thomas@schrein.com</a>>
wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi list,<br>
<br>
me and some friends are developing a DIY diving computer at
the moment.<br>
<br>
See link (only in German at the moment):<br>
<a moz-do-not-send="true"
href="http://www.skin-diver.org/sdiv/bastelecke/odico/"
target="_blank">http://www.skin-diver.org/sdiv/bastelecke/odico/</a><br>
<br>
We intent to have it as a hardware platform for open source
diving software development. We are thinking to have it
available as a kit in a few month.<br>
The software is in a alpha status, using Bühlmann ZHL16 Deco.<br>
Odico uses a CORTEX M4 processor and can be
programmed/debugged from outside with CooCox.<br>
We have made about 10 dives with hardware release OH0.1,
deepest 47m/150ft. It's works fine, very reliable :-)<br>
<br>
USB virtual com port is used for the communication with a PC.<br>
"subsurface-divelog" seems to be good software/project for a
Pc front end and we would like to use it for odico.<br>
So next is to implement a protocol into odico, compatible with
"subsurface-divelog".<br>
<br>
So we have some questions:<br>
Which protocol do you recommend us to implement into odico ?<br>
One idea is UDDF/UDCF, is this a good approach ?<br>
I also found some specs for the Suunto protocol and OSTC; is
it better to implement this ?<br>
Other suggestions ?<br>
<br>
I am very keen about your comments.<br>
<br>
Thanx<br>
Thomas Schrein<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
subsurface mailing list<br>
<a moz-do-not-send="true"
href="mailto:subsurface@subsurface-divelog.org"
target="_blank">subsurface@subsurface-divelog.org</a><br>
<a moz-do-not-send="true"
href="http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface"
target="_blank">http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface</a><br>
</blockquote>
</div>
</blockquote>
<br>
</body>
</html>