There is a burst of energy required when the WiFi transceiver begins operation. You, as many of us, discovered the magic moment that it happens.
Not knowing your circuit I can only speculate. As such, you may get past the burst point with a "large" amount of capacitance across the power input and ground. Using an expansion dock (which you are not) I'm using a 470uF cap just downstream of a 5V regulator just at the +5/gnd dock inputs (there's actually a small cap just upstream of the regulator as well). This has apparently "solved" my problem, however occasional brownouts occur putting the system in the dreaded 3 byte/4 byte reboot issue (another big topic on the forum).
Try a cap and see if it helps. Additionally reduce inductance (wire length) between the power supply and O2. If those don't help, you'll need a new power supply.
Thank you for the suggestion with the power supply.
This morning I have tried a number of different power supply units (including the official rPi3 plug and cable) and this allowed me to get the device setup and SD card expanded as per the guides.
Issue now is the wifi looses connection to my home internet? The AP is still up but the 'second connection' to the router fails?
If it helps, I use apple airport router and a number of AP. The wifi failed on both router/ap AND also failed when tethering to my mobile phone wifi hotspot?
Now if I boot the device up with the ethernet expansion board connected (I use the expansion dock with my Omega2+) I can get network address/connectivity from my router/network. But again, remove the ethernet module and I am back to only having the ability to SSH/WebConsole via the Omega AP.
Could this be power related?, The Omega is using the latest firmware available from the Onion repos and flashed using the onion guides.
I am glad that you liked it and sorry for the mashed up text and pictures, for the walkthrough of the methods provided by the REST API go through the README file of this git repo : https://github.com/ozgur/python-firebase.git
If it seems that your build system configuration isn't matching the firmware that we build, it might be because when ./scripts/feeds is run, it overwrites the .config file. To remedy this, you can just run git checkout .config (assuming you're using our github repo or docker image).
As for packages failing to build, we've seen this happen as well but only when running our Docker image on a windows machine. If the Docker image is running on Linux or Mac, there's no issues. (Haven't had the cycles to figure out why it doesn't play nice with Windows)
@Zheng-Tean i was thinking of placing the omega2 in the breadboard adapter and use wires to link all pins except the 2 i2c pins to the arduino dock. never got around to trying it or even if the idea is so stupid it's a waste of time.
I succed to put the exec and read permissions for files and folders with the line option in fstab
"option options 'rw,sync,uid=65534,gid=65534,umask=0000'"
but it's impossible to put write permissions make import the umask.
I use nobody user's and nothing changes.
FRDM KL-25Z is an awesome little board based on the MBED platform. And then, old school, home-brewed 8031/51 based boards, which, because of the ease with which you can access every part of the hardware, still kicks arse for some applications because there is no OS that gets in the way.
I also printed the Omega case by ElmoC. It is a great case, although there doesn't seem to be consideration for the MicroSD card. A small amount of fettling was required to make it all fit. I removed the small pillar between the microUSB and fullUSB ports and all is great.
In order to hold the 2 halves together, I clamped them together and then painted the side clips with acetone. Once dried it all stays together really well, If I want to remove the Omega2 from the case then it is easy enough to break the tabs off and then reprint. I am using mine for OctoPrint, I intend adding a camera from a laptop.
I will post a picture of my case later today.
@Joris-Mulliez I agree that PHP is of no use here, however I have plans to take this further, and wanted to start with the PHP base to work into. I am taking small steps into this whole new computing world for me. Yes, I could have just had the Python write out to "index.htm" and left it there, however what I am now doing is even beyond that. I want the initial page to allow for the selection of ZIP, City, PWS, Lat/Long and to set the refresh rate. This is only a backbone to grow from.
I use Zabbix for a lot of management purposes, and it has a discovery mode that you can customize. I used discovery in a large ISP environment to scan for new customer nodes coming online, scan the nodes for correct configuration, send alerts to techs when incorrectly configured systems or rogues were found, etc... The quality of the ISP's network went way up when we started detecting configuration issues BEFORE they caused problems.
The only downside is this is a rather application-specific service, so you have a challenge to make it application neutral. that probably means covering the basic common system settings, and making a API that is easy to integrate into the user's application. Being that these devices are great for swarm applications, your idea has a lot of merit. What would be better than a self-configuring swarm?
But I ageree this should be a generic Linux app, just keep it light weight so it works as well on small systems as large ones.
There are a lot of tools to look at that solve needs like this out there, in configuration management and system monitoring, so get some exposure to what others have done, might give you some good ideas.
rpc.nfsd: Unable to access /proc/fs/nfsd errno 2 (No such file or directory).
Please try, as root, 'mount -t nfsd nfsd /proc/fs/nfsd' and then restart rpc.nfsd to correct the problem
satisfy_dependencies_for: Cannot satisfy the following dependencies for nfs-kernel-server:
kmod-fs-nfsd * kmod-fs-nfs *
opkg_install_cmd: Cannot install package nfs-kernel-server.
root@Omega-8D69:~# uname -a
Linux Omega-8D69 4.4.46 #0 Thu Feb 2 23:46:03 2017 mips GNU/Linux
Looks like your connection to Community was lost, please wait while we try to reconnect.