Manual setpoint change problem

Legacy OSTC's
Post Reply
Jonny H
Posts: 3
Joined: 26 Oct 2015, 19:17

Manual setpoint change problem

Post by Jonny H »

I have the OSTC Mk2; having just upgraded to latest stable v3.10 and setting auto set point change auto. When I manually change from set point 1 to set point 2 in the simulator then the diluent automatically changes to 32/0. I then have to change the diluent back to air throgh the menu page.

My set up is as follows, all diluents set to air. Diluent 1 set active.
Gas menu is gas 1,3,4 and 5 set to air; gas 2 set to 40/0. Gas 1 is first gas active, all other gasses set not active.

Is this a bug or intended operation and if intended why?

Thanks in advance

John
Jonny H
Posts: 3
Joined: 26 Oct 2015, 19:17

Re: Manual setpoint change problem

Post by Jonny H »

Additional info:

I re-flashed my OSTC with v3.02 software and the situation as desribed in post 1 does not happen; ie, when I manually change from set point 1 to 2 and 3 the diluent remains the same and does not auto change to 32/0.

Regards

John
heinrichsweikamp
Posts: 4464
Joined: 13 May 2007, 18:07

Re: Manual setpoint change problem

Post by heinrichsweikamp »

Hi John,

Thanks for reporting - I'll investigate this issue tomorrow.

Regards,
Matthias
heinrichsweikamp
Posts: 4464
Joined: 13 May 2007, 18:07

Re: Manual setpoint change problem

Post by heinrichsweikamp »

Hi,

I can confirm this bug. It's indeed a serious issue for CCR divers (Well, at least you can see that the wrong diluent is chosen).

Sorry for that.

I'll upload the 3.11 with this issue fixed today.

regards,
Matthias
heinrichsweikamp
Posts: 4464
Joined: 13 May 2007, 18:07

Re: Manual setpoint change problem

Post by heinrichsweikamp »

Hi,

Have some issues with our firmware section on the webpage currently, but here's the 3.11: read.php?2,15834 And it's also available via the "Web Download" in the Tinybootloader v2.

Regards,
Matthias
Jonny H
Posts: 3
Joined: 26 Oct 2015, 19:17

Re: Manual setpoint change problem

Post by Jonny H »

Matthias,

I can confirm that software v3.11 no longer has the issues described at post 1. Many thanks for the quick fix.

Regards

John
Post Reply