edit your /etc/opkg/distfeeds.conf and uncomment lines 2 and 5 then run
opkg install socat
There is also netcat and ncat if you prefer.
It looks like it is set to target-mipsel_24kc_musl-1.1.16 which won't exist so your include of ugpio/ugpio.h will not resolve.
@James-Solderitsch the reset button on the pro works the same as the reset on the dock. Hold down the reset while switching on, make sure you have the usb cable connected so you can connect to the serial console.
If you are recovering from a USB stick, make sure you have correctly named the firmware file or it won't be found. If all else fails the web recovery option seems to be the best as a last resort, but you will need an ethernet expansion.
I trashed 8 Omega2 pro in a row while building some custom firmware, if you follow these points you can fix them.
@Suman-kumar-Jha My sense is you are quite inexperienced in this field so I will give you advice and some guidance.
If you always ask someone else to give you a solution, then you might solve your problem more quickly but you'll always have a lot of problems. If you ask for guidance on how to come to a solution then your solution will be arrived at with a whole lot of learning along the way.
When an interface comes up or goes down, this hotplug script is executed:
Spend some time reading up on the hotplug infrastructure and you can find your solution. It's just a scripting system that is triggered whenever an interface (or other device) comes up of goes down (or other relevant action). So think of it as a see-saw, if if1 comes up, execute if2 down, if if2 comes up execute if1 down.
Don't be daunted by the fact that someone more experienced wrote the exiting script, it was designed to be generic. You need something a bit different, so just write it.
@Suman-kumar-Jha As with any issue it is best to break it down into small parts:
Step 1, if you disable wifi, does the ethernet device reliably connect, remain connected and function correctly.
Step 2) if you enable wifi does this have an impact upon the functionalty of the ethernet.
Depending on the answer to these two questions you will decide how best to proceed.
a) I have no idea but it has a nice colour.
b) Take a look at these articles they explain how to use PWM
c) Take a look at /etc/rc.button you will see some scripts that demonstrate how you use the button.
@Stephen-Tunney I think you need to cool down. I have about 80 Omega2+ based IoT devices spread across APAC in both Home and office environments, all of which are connected to whatever WiFi their location provides. I have millions of JSON requests processed. WiFi connectivity is not even in my top 50 list of potential improvements.
Since your thread is old and very long maybe it would be better to create a new thread with a new specific set of details of your problem so the onion community can try to assist you.
Developing any device or software is a long series of disappointments and frustrations, it is better to channel your energy into engaging with the community in order to seek help to resolve your issues than it is to attack the guys who worked so hard to provide a device that we have all benefitted from.
@frederic-bouchar we classify this as a dummy spit :)
Software development is a series of frustrations and if you spit the dummy every time things get frustrating, you better get a job driving a school bus.
A better approach is to post some sample code and provide details of your firmware version and any other relevent information and the onion community are here to help you.
Your reported error is not unique to Onion, just google it.
@Nathan-Guyette it will depend on which firmware version you are on and which python version you need, but the most recent is here:
You can see all the packages here:
@peter-garner-0 the first line in the C code of oledDriverInit is:
onionPrint(ONION_SEVERITY_INFO, "> Initializing display\n");
So you need vernbosity set to < INFO before calling init.
@peter-garner-0 I think you need move oled.setVerbosity to the top of your code, it seems to default to debug verbosity so it is reporting all of your actions prior to you setting verbosity to Info level. The C library calls OnionPrint inside the OledExp code and this relies upon the verbosity setting.
I haven't tested this on Python but this is the case in C.
35 years ago when I was sitting in a practical class in college, our lecturer boreded me to death demonstrating the various tools for chip extraction. At the time I was a skinny teen with a sugar addiction which could only be satified with a constant supply of ice popsicles. These popsicles have wooden sticks, so I had a lot of these wooden sticks and realised they were a perfect chip extraction tool. I demonstracted their worth to my lecturer during one of his practical sessions. I never had to sit through his boring chip extraction talks ever again.
Buy a lillipop and extract your chips with the stick. It's a win win!
@György-Farkas I would disagree regarding hiding SSID. Hiding an SSID and adding complex password is the solution, not just a complex password. Most users do not know how to connect to a hidden SSID and my users repeatedly asked me about what the "network" was. If you hide the SSID you no longer have to deal with the issue.
I would also add that you need to ensure you have correctly configured your local timezone or ntp will mess up your time:
uci set system.@system.timezone='UTC'
uci commit system
If you're outside the US as I am the timezone is a little more complex:
uci set system.@system.timezone='AEST-10AEDT,M10.1.0,M4.1.0/3'
uci set system.@system.zonename='Canberra, Melbourne, Sydney'
I use remote logging extensively, you just need to configure it in your /etc/config/system:
uci set system.@system.log_ip=$HOST
uci set system.@system.log_port='514'
uci set system.@system.log_proto='udp'
uci commit system
Make sure you have the firewall configured on your remote logging host to allow the incoming logging.
Looks like your connection to Community was lost, please wait while we try to reconnect.