SKY9x Ver 3.0

[kaos]

I think sky9x board can do so much more than the stock. It is a good idea to separate ERSKY9x from er9x. Also, to fully utilize the sky9x board, any further revision board probably should focus on minor fix/improvement for the verB instead of coming out with a totally different board, other wise you are looking at writing codes for only 150 board owners.
Personally, I just don't see a Tx needs more than what the sky9x board is fully unleashed its power. If more is needed, that would be 12, 16 ch which is up to the module not the board.

one thing I, from the user's point, think can be greatly enhanced in the future is utilization of a pad (which is a common thing nowadays). some one can write a android app to use a pad as display/programming screen. then you can have large touch screen to do the programming and a lot easier navigation during programming. while in the field there is the existing small screen to do minor/critical adjustment, or if you want just take a 7" pad with you. so I think for the future board, the built in BT may be considered. Also, this will get rid of the limitation of the display screen issue. During fly, the built in screen can be used entirely for telemetry data display and critical minor adjustment of settings.

[SkyNorth]

Here is Rev 3 , The 7 way nav switch needs its own board , so putting the holes on the Sky9x made no since.
-Brent

[kone]

Looks and sounds very promising. Is there already an ETA and approx. price tag for the Rev3?

Thanks and greetings from vienna.
Christian

[bertrand35]

Brent, do we really need the EEPROM?
Bertrand.

[MikeB]

I would say YES. I assume you are think everything could be on a SD card. This is only plugged into a socket, and could work loose, perhaps even when flying. For reliability I would say the EEPROM should always be present.

Mike.

[bertrand35]

Yes, I thought that the models could be only stored on SD. The write method would have to be in another task than the mixer (as done in open9x) so that it is safe. And to modify your models through USB, no applet would be needed, you would open the models through the massstorage in the explorer, double click, it opens eePe / companion9x ...

I am ok with the EEPROM as well, it works, no problem!

Bertrand.

[Kilrah]

On model load the settings would be loaded form SD onto RAM anyway, so if handled correctly after that even if the SD was removed the only risk would be to lose changes if the model can't be written to card at power off...

[jhsa]

what would happen in case of a reboot?

[bertrand35]

The changes would be lost (EEPROM or SD, no difference in that case). Mike says that the EEPROM is more reliable. He is right, but if we don't write in the same task than the mixer, I see no real issue.

Bertrand.

[MikeB]

Currently, you don't need a SD card to be able to use the board. The EEPROM is only £0.50, while a SD card is significantly more. I definately feel keeping the on board EEPROM is cost effective.

Mike.

[bertrand35]

Right, having both is good. With a FW option we could even choose to use the SD in one or the other way. I think I will like using it the other way once implemented.
Bertrand.

[SkyNorth]

The price will be around $90- $95...I hope to use the SAM4s - it has a ARM Cortex M4 core , with a DSP and 512kb Eprom
I'm not sure what the DSP would be used for....but ...if you build it...they will code ......
I need to do a small proto type run...to prove the new layout....once that checks out then a production run..
I dont want any jumpers , or regulator mods ....they took to much time to do on Rev B
It will be the End of November , before any would be ready for sale.
-Brent

[bertrand35]

A DSP for sound mixing?
Bertrand.

[MikeB]

The '4S is pin, hardware and firmware compatible with the '3S, no firmware changes unless something like the DSP is needed. Oh, and it will run faster then the '3S.

Mike.

[Irish Steve]

Are there any significant issues down the road between the versions from an end user aspect, or are they basically compatible, just different

[SkyNorth]

The Rev B and Rev C ..3 ..PO , Are the Same from a software point of view , the only changes are to the board Layout.
There is a new constant current LED backlight driver, but the code does not change for it.

The New version has a standard 16 pin header for LCD / data buss expansion , you could also plug in the 7 way Nav switch here.
There is a second 3.3V regulator for the Bluetooth module , The SD card can be removed without removing the pcb , and a way of moving the SD
card to remote socket is provided.

I'm working on a adapter PCB for the 7 way NAV switch , and hope to be able to offer it as a option with Rev 3 SKY9x

-Brent

[kaos]

yeh, plug in 7 way Nav switch. definitely welcomed.
Looks like my other er9x is going to be replaced with its guts too.

hmm, ersky9x can have 60 model memory, two of them, that is 120 model. Needs to find a second job to fund these.

[Clivew]

Add me to the list please Brent!

Thanks,

Clive

[bertrand35]

Brent, would it be possible to have an RTC clock on Sky9x 3.0 (as on gruvin9x board).
Because I would really like that when I backup a model on SD, the date is right, today we write in the future ...
Bertrand.

[MikeB]

The theory is the co-processor does this. It has a 32.768 kHz crystal for the purpose, and also connections to allow battery backup to be supplied. Just needs some software writing to do the RTC bit. Mainly it needs to keep track of seconds, the ARM has RTC capability, just needs the number of elapsed seconds to synchronise it.

Mike.

[nsf]

I'm interested in the rev c board too. Is there any waiting list?

[minbari]

have been reading about this all morning. very cool sounding board. very interested in getting one once they come out.

[SkyNorth]

The RTC chips were to expensive for the real estate/function they took up.

The Tiny167 , is a Automotive chip , but is the only TINY AVR that can be clocked by the watch crystal in low power / sleep mode.
http://www.atmel.com/Images/doc7728.pdf

This approach , gives us a RTC and 12 more inputs /outputs .

I have seen a AVR used as OSD overlay ...so we could send telemetry data to the Tiny , and have it generate the video info.

The Sky3 is out for a proto-type run , to test the new board layout.
I will get the boards next week , I then have to hand build them up, and send them to the testers.

If all goes well, then I should be able to start shipping in November.

-Brent

[gohsthb]

If only I were on that list of testers. . .
-Gohst

[GTiDon]

Is this still unavailable for purchasing?

[Kilrah]

LOL, "still". The new design only got frozen a couple of days ago...

As Brent said 2 posts above, he just sent the order for the prototypes to be manufactured

[SkyNorth]

It will be November before they are ready to ship.

-Brent

[kaos]

do you have a preorder list or we have to get in line when it is out like those iphone5 maniacs?

[SkyNorth]

I have a email folder where I put requests for boards.
As I have boards ready , I send out Emails to those who asked....

-Brent

[bruce70]

Brent,

Please add me to your list of interested people.

Bruce