forum.heinrichsweikamp.com

Yes there was but I do not recall what it was. It made me think that the OSTC timed out right as the upgrade started.

Now it says:

Bootloader for HeinrichsWeikamp OSTC,
based on TinyBootLoader, v.1.9.5 written by claudiu.chiculita@ugal.ro
http://www.etc.ugal.ro/cchiculita/softw ... loader.htm
Support: info@heinrichsweikamp.com
--------------------------------------------------------------------------------------------------

Could not connect to COM3 at 19200
ERROR!

It used to be COM4 when using.

Okay, just tried using my netbook rather than my normal laptop. It's ALIVE!

Looks like my laptop was having problems deciding what COM port to use.

As to the original problem, is it possible that the upgrade can start and almost at the same time the OSTC times out and closes down. I really think this is what happened.

Once again, thanks for your help Matthias.

swissdiving Wrote:
-------------------------------------------------------
> But then other people are complaining about the OC
> Bühlmann algorithm...
> ...you just can't win.


A most peculiar thing happened recently: Shearwater released a new dive-computer with ZH-L16-C algorithm and GF's -D

Nothing wrong with Bühlmann so it seems, just with people's minds.... B)-

Hallo Leute

Der "Konfetti-Sturm" tritt bei mir auch auf. Allerings nur ein Bruchteil einer Sekunde, unmittelbar nach dem Wakeup... Und die Battery-Info zeigt auch unsinnige Werte an. Heute waren es zuerst -55°C, nach einer TG-Simulation hat er die Raumtemperatur, resp. meine Handtemperatur gespeichert...
[img]file.php?2,file=376,filename=batteryinfo.png[/img]

Snow happens as well to me but only for a split second.

Strange thing is that the computer screen is now upsidedown. I cannot find how to fix this. Any clues?

Also, the dive offset went from 3423 to 53 and the battery page shows I have done 17801 dives. It also says the serial number is 255 rather than 5044! However, Bootloader says it is 4685! Any suggestions about this?

I also notice that the battery symbol on the front page now shows a graphic representation of how much battery life is remaining. That is good.

Battery-Info is strange... It changes whenever i put the usb-cable into my OSTC for charging...

Will have a look, definitely some kind of issue with the battery history....

regards,
Matthias

Matthias, i would rather have an Logbook history than a battery history...

Matthias, also the screen is inverted and the OSTC serial number is wrong.

Michael,
Are you sure you are not holding the OSTC upside down!?
ONLY KIDDING!!
(:P)

I think that the change of the serial number has something to do with it. I found another post on this forum where it was mentioned that after a certain serial number there was the change from Mk2 to 2N and that the screen is inverted in 2N compared to Mk2.

Hi,

Can you send me a mail: info@heinrichsweikamp.com, please? I'll send you a HEX file reinstalling your old serial number... I can't see how this happened.

Cheers,
Matthias

Clownfish Wrote:
-------------------------------------------------------
> I think that the change of the serial number has
> something to do with it. I found another post on
> this forum where it was mentioned that after a

Email sent. Very strange.

Edit:

Received the hex file and reflashed. Put it back to correct serial number and screen is back to correct way up.

Thanks Matthias.

I've just tried the 2.61 update and it seems to have broken my OSTC 2n It's gone completely black and I can't turn it on at all.

When I click "Check Connection" I just get:

Connected to \\.\COM6 at 115200
Searching for PIC ..., Not found
ERROR!

I've tried all of the USB ports but same message. I can't seem to find bootloader v1 for download so not sure if I can try the magnet option. Do Heinrichs Weikamp offer a service where you can send the unit back for a reset/re-install?

Thanks

Lee

Bootloader V1 is here http://www.heinrichsweikamp.com/#/en/os ... _software/

Clownfish Wrote:
-------------------------------------------------------
> Bootloader V1 is here
> http://www.heinrichsweikamp.com/#/en/ostc/ostc_2/p
> cmaclinux_software/


Thanks. Unfortunately still no joy, just totally blank and the computer can't even see it and still won't switch on. I'm not even getting the flashing red/blue/orange lights so it's as though the unit is completely dead. I've tried on another laptop as well to try and rule that out and it's just the same.

Any help/advice would be welcome. I've got a trip coming up in a few weeks and I really need it working by then!! :-/

aerobrain Wrote:
-------------------------------------------------------
> Clownfish Wrote:
> --------------------------------------------------
> -----
> > Bootloader V1 is here
> >
> http://www.heinrichsweikamp.com/#/en/ostc/ostc_2/p
>
> > cmaclinux_software/
>
>
> Thanks. Unfortunately still no joy, just totally
> blank and the computer can't even see it and still
> won't switch on. I'm not even getting the flashing
> red/blue/orange lights so it's as though the unit
> is completely dead. I've tried on another laptop
> as well to try and rule that out and it's just the
> same.
>
> Any help/advice would be welcome. I've got a trip
> coming up in a few weeks and I really need it
> working by then!! :-/


Quick update, it turns out the pins were damaged by the USB cap due to it being overtightened.

Any ideas when the latest beta cycle will be rolled into a stable release? I like some of the functions in 2.61 but thinking that when the season gets going in anger ideally I don't want to be diving in beta.

aerobrain Wrote:
-------------------------------------------------------
> Any ideas when the latest beta cycle will be
> rolled into a stable release? I like some of the
> functions in 2.61 but thinking that when the
> season gets going in anger ideally I don't want to
> be diving in beta.

You don't have any other dive computer as reference?
And as long as you plan your dive and as you use a runtime
table it doesn't matter if you have a beta or a stable
on your OSTC... Even better - if you dive with a beta release
and everything works fine, then you can post it here so that
Mathias & HW will know it.

scubatinoo Wrote:
-------------------------------------------------------
> aerobrain Wrote:
> --------------------------------------------------
> -----
> > Any ideas when the latest beta cycle will be
> > rolled into a stable release? I like some of
> the
> > functions in 2.61 but thinking that when the
> > season gets going in anger ideally I don't want
> to
> > be diving in beta.
>
> You don't have any other dive computer as
> reference?
> And as long as you plan your dive and as you use a
> runtime
> table it doesn't matter if you have a beta or a
> stable
> on your OSTC... Even better - if you dive with a
> beta release
> and everything works fine, then you can post it
> here so that
> Mathias & HW will know it.

I've done some diving with it in the local lake but I'm guessing that doesn't give much valuable feedback as the dives were 20m max and no deco. I'm quite new to gas switch diving so I was just thinking that I didn't want to add in a potential issue if I can help it just yet. Although, from the feedback on here it does seem like it's pretty reliable so I may decide to give it a go on our trip next week. I'll be diving with a buddy who's got 2.50 installed anyway so with that and my bottom timer I guess it shouldn't be too bad.

We'll probably not be racking up too much deco either. (This is me clearly talking myself into just updating it!! )

Hi there,

I have been doing some decotable diving and I brought the OSTC2n with me (bottom gas AIR: one dive 20'@40mt with EAN50 as deco and one dive 20'@47 and EAN50+OXY as DECO gas).
The dives had been planned with Vplanner and HLPlanner (both VPM) and I brought along the OSTC 2n with 2.61 Beta installed.

In my planning I use additional 5min at 21 on EAN50 to maximize off gassing at depth.

The OSTC performed as expected and its decoplan (GF set at 80/15) was within a minute or 2 (at the end) of my tables.

I'd say that the firmware passed with flying/diving colors
I might try a couple of trimix table dives tomorrow.

Mathias, if needed I can provide you with the downloaded profiles but not earlier than Wednesday night.

Fabio

Hi all, I'm new here, just bought a 2nd hand OSTC2n from my buddy... Yesterday I upgraded to beta fw 2,61 and did a test dive in a cold lake ..just to see the behaviour of beta fw against prepared tables.

I noticed few strange things both in real dives and in simulated dives on jdivelog, that I'm going to report here, with some "feature requests":

1 - The most important: during real dive I was on tx12/60, tx30/20, ean50 and oxygen,everything worked fine in bottom phase, coming up from 75 mt to 43mt i switched from Tx12/60 to tx30/20, all good, the deco plan was ok with first stop at 21 mt, changing to 18mt while i was coming up. At 22 mt i was changing to ean50, but unluckily maybe I double pressed the select switch after i went to gaslist menu, that means i selected again the Tx12/60 .. then I immediatly changed again to ean50, but at this point i was expecting a short stop to 18 mt and then climbing again to 15-12-9-6-3 ... BUT the OSTC gave me 22 mt 6 minutes ...I climbed a bit over the ceiling to see what's happening...the minutes counts still 6...5...4... but the ceiling after being a bit red (warned) went from 22 to ...21 ... to 20 ... to 19 .... to 18 ... until the 6 minutes countdown finished, then the OSTC realized that I can go directly to 6 meters on oxygen and finish my dive normally .... what's happened???? I downloaded the divelog, replayed it in jdivelog simulation and nothing strange happened without the wrong gas change mistake ... it happen again whit the gas change mistake during simulation...

2- Feature request: detect and eliminate false double switch pression ... to prevent wrong selection and wrong menu scrolling, expecially with thick dry gloves, is it possible to make a routine that detect 2 consecutives fast switch pression and discharge the second one, let's say if the 2 presses happen at less than 0,5 seconds...

3 - cns% calculation in onboard simulator - that seems not to account for gas changes .. it's way too low for 2 hrs dives with 1 hr oxygen on 6-3 mt ...

4 - lead tissue: even if i was diving on Tx 12/60 and the most ongassing gas was helium, the lead tissue function showed me oversatoìuration of N2 on the correct lead tissue.... so i tried to simulate one Heliox 10/90 dive (no N2 on bottom gas). After 30 minutes at 120mt in simulation, lead tissue showed me 80% saturation (sea level) of N2 on tissue 0 ... so there is a problem in Accounting for He tissues on the lead tissue display ... the graph tissues display was showing good saturation of he tissues, BUT still 80% saturation of N2 tissues, and this is wrong, because you are breathing no n2 so you are desaturating to less than ambient pressure the n2 from tissues. The right behaviour is to see the fast tisues N2 coming down to 70...60...50% saturation, until a gas chang with N2. That is valid also on final oxygen at 6-3 mt .... the fast tissues goes below 80% saturation and once you climb to surface they will ongassing till Equilibrium at 80%.

I hope that this could be halpfull to improove this fantastic piece of equipment, keep on going!!!

Attached file, jdivelog of this short test dive I made.

Bye, Ciro Osimo from ITA

For the 3rd point, cns%, i noticed that the problem is the 3rd digit, untill 99% cns is OK, for 120% cns it only show 20% an so on until >255%, when >255% it shows a warning message.

Bye, Ciro

Maybe thats not the right thread, but i'm backing Ciro's request about the "double click". With thick dry gloves, this is a problem for me as well, especially while gas switching.

thanks,
Steven

Hi,

Thanks a lot for the detailed report, do you have CF55 0? (There's a known bug in the latest beta with this CF).

> 2- Feature request: detect and eliminate false
> double switch pression ... to prevent wrong

Right now there is a delay of 32ms between the first and the second press. I have changed this here to 256ms. Maybe a try for the next beta... A delay too long will be annoying when setting up your gases.

> 3 - cns% calculation in onboard simulator - that
> seems not to account for gas changes .. it's way
> too low for 2 hrs dives with 1 hr oxygen on 6-3 mt
> ...

Hmm, works fine here. Shows every value between 0 and 250%.

Regards,
Matthias

Hi Matthias,

CF55 = 0

OK for the 256 ms delay, should be fine..!

About the CNS, this evening at home I will post you the screendump of my OSTC simulating 21 min at 120 mt, you'll se what i mean.

Try yourself to simulate 21 at 100mt with following gas:

10/70 first gas
16/40 @90mt
30/20 @43 mt
50 @22mt
100 @7mt

GF 15/95

Bye, Ciro.