Best posts made by Costas Costas

@administrators can you please enable /dev/mem and rebuild the firmware to fix the broken Fast-gpio ?

I'm terrible with a soldering iron and I'm waiting until the basic docks are a dollar a piece before I buy any.

Step 1 expose the 5V and Gnd from that old blue USB cable you got with all those Nano, next to no memory, clones.

Step 2 dig out the "Grove" connector you bought for supporting the WioLink Kickstarter. The 4 pin female plug end fits quite snuggly across GND, 3.3V, USB D+ and USB- pins on the Omega 2/2+. Use all 4 pins even though we only need Gnd and 3.3V as it keeps it more stable on the Omega.

Step 3 dig out that voltage regulator from the time you wasted on the ESP-01's.

Step 4 tie it altogether with the PCB terminal block. It's a tight fit but you can get 3 connections in the Gnd terminal. Gnd leg of the voltage reg, Gnd from "Nano" USB cable and Gnd to Omega. Centre pin of the terminal block has 2 connections. Leg of the 3.3V out of voltage reg and 3.3V to Omega. Last terminal just has the 5V from the "Nano" cable.

Job done. I'll not include a photo of my end product but it's working just great including the addition of the obligatory blu-tack to hold the "Grove" plug onto the Omega.

and if you have a second partition it will be mounted at /tmp/mounts/SD-P2 etc

@Shanan-Clark type df -h in the console.

@patrick-seb bonjour is only required to see the AP in a browser with the Omega-XXXX reference. Without bonjour just use 192.168.3.1 in a browser.

This is after the AP has appeared and you have connected to it.

Biggest reason the AP doesn't appear is normally inappropriate power supply. The Omega is very fussy. I would try as many different power supplies as you can.

@Greg-Lorincz I would say the Omega's are pretty well made and generally most work to specification. There are a small number that are faulty but it seems to be quite a small proportion.

Omega's are VERY particular about the power they need. I have many power units and most don't work with the Omega. For most people if they find the correct power supply all will be fine.

Same for me with a different node.js.

@WereCatf yes it is ra0 and details can be seen with:

cat /etc/config/wireless

@Koos-du-Preez bit of documentation on the GitHub at https://github.com/OnionIoT/onion-ubus#gpio

@Manuel-Godinez I know many people start with controlling the onboard LED's but I'm guessing that ultimately you will want to control the GPIO pins. Also the LED was a bit flakey for me when I tried but it works up to a point and certainly works with console commands. With the GPIO details below and the syntax from the url you can check out LED's if you want to try.

If you are connected to the Device Explorer via the cloud and enter the correct commands and parameters you can control the pins from the web interface.

So command get and params {"gpio":"0"} will return:

    "success": true,
    "pin": "0",
    "value": "0"
}

Command set and params {"gpio":"1","value":"1"} will return the following and can be checked with a follow up get

{
    "success": true,
    "pin": "1",
    "value": "1"
}

Ultimately some users will want to control the pins via their own web interface or application. So if you obtain an API key and click the Generate Code button it will give you curl, C, Python and NodeJS versions of the required code.

The Device Explorer is considered to be a bit buggy by some people as you have to ensure the data in the fields is not "cached" but if you retype the data in the fields and move to another field it works as expected.

@Don-DeGregori

1. Yes the documentation would be better if you didn't have to skip about, poor design in my book (no pun intended).

2. Noticed the almost invisible grey commands hidden within the text. +1 for new line in red.

3. Looks like fast-gpio doesn't work as documented, comes back with:

segmentation error

1. Could the Onion doc person confirm they are watching this thread or advise how they want to be informed of the errors and omissions?

@Daniel-Andrade any news on your boards?

@Steven-Brent you can run your Omega from a USB drive, see https://wiki.onion.io/Tutorials/Using-USB-Storage-as-Rootfs for details.

I guess it was left off to achieve the $5 price tag.

@Manuel-Godinez

In the cron aren't you missing the python call?
So change to something like this, depending where test2.py is located

12 6 * * * python /test2.py > /tmp/test.log 2>&1

When will something like this be available at a sensible price?

@Luciano-S. said in Where do Omega's get their time from on bootup:

Reboot Omega and if you have network it will actualize your location/date/time.

I have everything set as per your post but the point is when you force a reboot by killing /etc/rc.local it brings up a fixed time, not a network time. With this extra line in /etc/rc.local it obtains the network time on reboot.

ntpd -q -p ptbtime1.ptb.de

Onion issued a post on GitHub that they are planning to look at 1-wire this week.

@Leo-de-Blaauw I would concur but the ticket is far from clear.

I'm gobsmacked that a supplier even suggests such a fix without first acknowledging they are financially liable for a replacement if the end user is unable to do the suppliers remedial work for them. This includes messing around with the wrong resistor because their instructions are ambiguous.

WeMos D1 Mini Pro and Pi variants (Official charitable Foundation for me).
Pi Zero starts at $5 plus a few bits but can be as little as $2 for WiFi adaptor (plus PSU and SD card).

AFAIK the Omega will not provide data from any sensors and we are waiting for a response from @Lazar-Demin to indicate when it will be fixed.

So we have not been able to use the SD card for the first 2 months. Been unable to reboot the Omega and struggled with the very specific power requirements of the device.

We are also waiting for the GPIO fix. Look forward to reading your comments @Lazar-Demin