Other working project, the adc-exp same code working fine. I don't have to do the sleep file link, the file is there.
The adc works, the sensors work and turn off and on relays depending on the sensor logic. if I run the adc-exp # I get
root@Omega-B437:~/projects# adc-exp 0
A0 Voltage: 0 V
root@Omega-B437:~/projects# adc-exp 1
A1 Voltage: 0.79 V
root@Omega-B437:~/projects# adc-exp 2
A2 Voltage: 0.58 V
root@Omega-B437:~/projects# adc-exp 3
A3 Voltage: 0.76 V
I had three sensors connected on ports 0, 1, and 3. port 2 has nothing on the adc.
I have a motion sensor, temp sensor, and photo resistor. They all work and toggle the correct relays on my main project where I am not using a dash.
Then I power down and change the header plug to the dash, and we get what I have described.
I also did the sleep link like you mentioned, and now I can call time.sleep(2) so that works now. Thanks.
Another project is rust-embedded..
The goal is to support mips, risc-v & arm (cortex-A/M and may be R?).
BTW, rpi3/4 supported, but w/o wifi ..!.
Full Error Message
"This device cannot start. Try upgrading the device drivers for this device. (Code 10)"
Typically, the device's hardware key contains a "FailReasonString" value, and the value string is displays an error message defined by the hardware manufacturer. If the hardware key does not contain a “FailReasonString” value the message above is displayed.
According to another article:
You can probably get over using "Method 2: Enable Safe Mode with Networking".
I do not use windows from Vista days.
Using OTG in your mobile-phone is another way to access the dock/Omega2. A few mobile apps such as Serial USB Terminal (Android) that have CP210X drivers built-in.
As you have tried 3 PCs already, it may be that the CP2102 itself is damaged.
You can use NCM to upgrade the firmware on many devices in one operation. Because security fixes are distributed as new firmware revisions, upgrading firmware helps network administrators correct security vulnerabilities.
@Crazi-Tane I did respond to this, but seems I did not hit submit. Sorry.
Yes you can run python on Omega2, also micropython may be more appropriate due to its smaller footprint.
Edit /etc/opkg/distfeeds.conf, uncomment lines 2 and 5, then run opkg update.
opkg install micropython will install micropython
opkg install python will install python 2.7.x (light)
opkg install python3 will install python 3.3.x
Python is very popular on Omega devices, so many users can advise you on this. Personally I use C/C++ so I am not the best resource to assist you with python.
Not sure why you bump a 4 year old topic.
Python 2 officially hit the End of Life (EOL) deadline on Jan 1 2020. As of this date, no new bug reports, fixes or changes will be made to Python 2 making the whole above discussion an obsolete topic; there is no other choice left than Python 3.
@Suman-kumar-Jha said in VPN working good on Omega2S+, how to make it working on Omega2S ?:
Sorry @crispyoz for not providing you basic details.
And thanks i had solved the issue.
My firmware version was b232, then upgraded manually to b242.
This solved my issue. I am able to install openvpn-openssl package with out any error.
Very Helpful Post .......!! thanks for sharing with us.
@Dennis-German If you have an out of date distfeeds.conf is may point to invalid hosts. When you update your firmware to the current release it will update your distfeeds.conf to point to the updated hosts.
want to be able to read the WiFi signal to noise ratio to determine if I have a bad WiFi environment.
It would be better off with something like kismet https://www.kismetwireless.net running in a workstation.
May be, you are looking for a representation like this:
Kismet has listed the supported wifi hardware in the above site.
The typical capture is in the order of megabytes every second or even more, depending on the environment.
Omega2+ has 802.11 b/g/n, (5 GHz support is optional in "n") up to 150Mbps as per specs, where as n itself is 54-600Mbps.
Also, there are hardware analyzers that meets the needs of a CWAP.
Looks like your connection to Community was lost, please wait while we try to reconnect.