I have just updated from 005 and it only updated to 006. So tried running oupgrade again and I keep getting "Could not connect to Onion Firmware server -------etc etc.

I looked at script oupgrade and can see it uses a different server. I tried to connect my PC browser to that site and is comes back with a security block due to the SSL certificate expiring yesterday. So I bypass that and I then cannot connect as it says it needs a handshake.

My wifi is up and I can ping sites ok from Omega terminal session.

If I look at the old oupgrade file and go to that location I can see all the versions.

I have 3 omega's and have updated 2 to 0.0.6.b266 and other is still on 0.0.5

? why did it not update to 0.0.7 from 0.0.5 has 0.0.7 been taken down?

thanks Tony

@Kit-Bishop Thanks very much for that, I am getting slower as I age being retired my codeing skills are ok for higher levels but biased to wards Delphi for Windows. Linux is hard work although Unix a long time ago I was just ok. I think the Raspberry Pi has spoilt me so much info available makes it easy.

Tony

@Boken-Lin sorry for long delay in responding have been away.
Yes understand a webserver is required but not being a linux guru is there a Onion library that I can use to talk to the IC2 I know the Arduino has same. All I need to do is send an ASCII string in both directions any maybe use Python on the Omega.
If someone has example I2C code would much appreciate it being posted along with library download details.

Thanks Tony

Hi just received my Proto Expansion Boards. I wrongly assumed that the socket pins would be tracked to a row of the proto pads without the tracks we will have to wire wrap or solder to the pins to get signals to the pads. Can I suggest that this can be added for future boards.

Tony

You can use:- expled 0xFFFFFF to turn it back on full white or any colour by varying each colour but I expect you knew this but expled 0x0 does not turn it fully off just very low level.
Thanks so I must remember this.

FYI I just checked my dock
5v = 4.9v
3.3v = 3.34v
2.5v = 2.7v
2.0v = 2.17v
Austin, Lucky it does not seem to have zapped your Omega (yet)!

Another Question. I want to be able to send and receive data from my Arduino project a DDS (Direct Digital Synthesizer) for my Ham Radio project, to the Omega then by using my Browser connected to the Omega see the data or send new data. Basically Send a Frequency or Receive the Frequency back from the DDS by WiFi.

Now I understand the I2C is used to communicate. I am sure I can probably work out how to send and receive ASCII data on the Arduino but have little idea how I can do same on Omega then Display it on Browser and likewise send the contents of a webpage entry box back via I2C to the Android.

I think this will be a typical requirement for many projects?

The DDS will retain the Rotary encoder and the 2x16 LCD display on my current Arduino only project and will test to see if an Omega is connected if so will also accept Rx/ Tx Data from the Omega via WiFi.

Thanks for anyone's help.

Ok I have set up my Arduino dock (wired up and programmed the new bootloader) and set up Arduino programming on my PC and successfully been able to send and execute the example 'Blink2' via WiFi. Its great being able to access the Omega / Arduino Dock via WiFi I can now program from my Laptop and my Win7 Pc via WiFi.
NOTE: It did not work at first I have to update my Arduino Platform on the PC to Version 1.6.6 (I had V1.6.5) and then I updated all the Boards using the Board Manager & same for Libraries, Edit the Boards file (I backed up the old one 1st in another directory away from the Arduino location). Add the line found it this setup guide [https://wiki.onion.io/tutorials/Arduino-Dock/Using-the-Arduino-Dock](link url).
? I am not sure if the Boards file will be overwritten next time I update the Arduino Dev environment on PC?

When I received my Omega I could not connect it to my WiFi network. However I could with my Android phone see Omega-1D1D as a hotspot access point so I connected to it , noted the IP address then used the browser on my Android to connect (can't remember if I had to login) then it offered the setup wizard and updated the firmware. Sorry can not remember the full sequence but a bit hassled at the time trying to get it to go. My private WiFi network was on 10.0.x.x once the wizard had finished and I had added my network Omega was given a new IP in the 10.x.x.x range and now connects OK every time.