Slight problem with V2

[nigel hewitt]

It's self inflicted I know but I've been running my own code in my OSTC2 and there was such good talk about V2 that I thought I'd try it.
It's good. I agree.
But how do I get it the right way up?

It must be some configuration bit that my code left set but I've dragged through the documentation and can't find it.
Yes, I know I could download the source and find it but I don't really have time.

[img]http://www.nigelhewitt.co.uk/stuff/invert_ostc.jpg[/img]

[JeanDo]

Hello Nigel,

Looks suspicious. Who did you bought this device from ?
How did you write or compile your own code ?

Regards,

[sailor]

Hi,

you might have a "flip-screen"-command in your code that survived from your own code.
"flip screen" was an option in one of an older MK1-code you migth have used for your own code.
Maybe reloading V2.0 will cure this.

For the CF12-warning set CF12 below 90%.

Reiner

[nigel hewitt]

Thanks,

I'm afraid I've already reloaded it and since the boot loader overwrites everything, my image is smaller than V2, it seems it can only be a bit left set in the EEROM or such.

My code is a different image so although I read quite a bit of the original I only used the constants et. al. I've been writing code for 40 years now and embedded CPUs for 30 so I hope I'm getting to know what I'm doing soon.

It's a lovely platform to write for and I only wish I had the time to do some more work on my version because I have ideas on user interfaces I want to explore but, sadly, I have less time than I hoped when I bought it.

So no bit to reset? I suppose I don't need to fix it but I'd like to.

[Dahab Boris]

Nigel,

Good skills for writing your own code. Love the fact it's upside down though

[nigel hewitt]

Thanks... It's been lots of fun but I just haven't time to do all the things I want at the moment so I thought I'd revert to the factory offering. I think the next trick is to do an eeprom flush to zeros. Then a reload.

This is my code by the way. It just needs the logging and the configuration screens sorting out:

[img]http://www.nigelhewitt.co.uk/stuff/ostc2nig001.jpg[/img]

[JeanDo]

Send me your email please.

[gorcio]

nigel hewitt Wrote:
>
> This is my code by the way. It just needs the
> logging and the configuration screens sorting
> out:
>
> http://www.nigelhewitt.co.uk/stuff/ostc2nig001.jpg

Very nice, clean and readable. I like it. Well done

[Simon A]

Nigel,
Looking back through the old documentation, a flip OLED display was introduced in V1.32 beta (was CF39, now used for something else)
Might be worth Emailing Matthias (I'll PM you his email address) and seeing if you can get a copy of V1.32 beta to load onto the OSTC Mk2, flip the screen and then upgrade to V2.0.
HTH
Simon A

[nigel hewitt]

Resolved by email.
Many thanks folks.

It was, as I suspected an overwrite, so I just had to overwrite it back with the right value and then adjust my code to not touch certain places. Done now.

[gorcio]

Are You planning to release Your code ? Is it screen display modifications, or did You go deeper and modified also algorithm routines ? Asking just out of curiosity ... I know, it killed a cat

[heinrichsweikamp]

nigel hewitt Wrote:
> It was, as I suspected an overwrite, so I just had
> to overwrite it back with the right value and then
> adjust my code to not touch certain places. Done

To whom it may concern: The OSTC 2N display is mounted 180° flipped compared to the MK.2. All OSTC with serial number > 2048 are 2N and the output is flipped in software. Messing around at the serial number locations (Which is possible when using a selfmade code) caused this effect.

Cheers,
Matthias

[nigel hewitt]

gorcio Wrote:
-------------------------------------------------------
> Are You planning to release Your code ? Is it
> screen display modifications, or did You go deeper
> and modified also algorithm routines ? Asking
> just out of curiosity ... I know, it killed a cat
>

Releasing it would suppose I ever finished it.
I'm not sure I'll ever stop changing things enough to call it 'stable'.

I had a VR3 and it worked but the interface annoyed me badly. I do this for a living so I bought the OSTC2 to try my ideas of user interfaces.
All the code is changed. It's not even the same linker model. Also it is all in assembler. Including the fonts and the gas model.

Rather than menus and a tree of options you just turn the pages until you see the things you want. Hit the other button to put the page into edit mode (if it has any options).

Also there is the point that I do conservatism not the computer. I want it to tell me what Prof. Bühlmann thinks about my dive so far. Then I will make the call how close to that line I go. I tend to dive very conservatively, I'm an old buffer with a heart condition so I don't want to face the annual medical and have to admit to a problem. However I make the decisions about conservatism because I know if there are other considerations (something broken, buddy going funny on me, weather getting bouncy, warm and happy so I'll stay down here)

I'm not sure my requirements in a computer match anybody else.

[Solodiver]

nigel hewitt Wrote:

> I'm not sure my requirements in a computer match
> anybody else.

I'm sure it would! So why not releasing the code and look what what others think about!? You may get some optimasation and extension of your software also...

Mind the Meaning of the tow letters OS in the Unit name