@crispyoz:
Thanks for the short story.
I was on cellphone browser (still am).
When a company of the size of mediatek is unable to support Linkit boards, we must appreciate onion; for onion supports the current boards plus running a forum that we can meet.
I have the same level of respect for you today, as I was reading ur first help msg months back.
Thanks..
@LightSwitch :
I do not have Dash nor ADC Exp. Still, going though various docs makes me believe that ADC Exp should work with Dash. As per:
https://onion.io/omega2-dash-guide/
"The Omega2 Dash is compatible with the existing ecosystem of plug-and-play Omega2 expansions."
Please verify that i2c pins are configured for i2c (not for gpio), in the dash.
root@Omega-745F:/tmp# omega2-ctrl gpiomux get
Group i2c - [i2c] gpio (configured for i2c)
Group i2c - i2c [gpio] (configured for gpio)
If is is configure for gpio , change to i2c
root@Omega-745F:/tmp# omega2-ctrl gpiomux set i2c i2c
As per the docs:
https://docs.onion.io/omega2-docs/using-adc-expansion.htm, ADC exp can have 0x48 or 0x49 addresses(settable).
Please see if the i2cdetect reports ADC exp at either 0x48 or 0x49:
root@Omega-745F:/tmp# i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n] Y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- 27 -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Since Omega2 has only one I2C, trying to access a bus other than 0 fails.
root@Omega-745F:/tmp# i2cdetect 1
Error: Could not open file /dev/i2c-1' or /dev/i2c/1': No such file or directory
I have connected a device with address 0x27 to the I2C bus. But any compatible I2C device shall respond to the i2cdetect.
From the opkg file listing adc-exp and python3-adc-exp install different files:
root@Omega-745F:/tmp# opkg files adc-exp
Package adc-exp (0.3-2) is installed on root and has the following files:
/usr/bin/adc-exp
root@Omega-745F:/tmp# opkg files python3-adc-exp
Package python3-adc-exp (0.3-2) is installed on root and has the following files:
/usr/lib/python3.6/OmegaExpansion/AdcExp.py
/usr/bin/adc-exp is a script that makes use of the various programs installed by i2c-tools. adc-exp can be tried as the next step.
root@Omega-745F:/tmp# adc-exp -h shall provide various options.
Thanks ..
Hi all,
This is a continuation of sharing of ideas with @crispyoz under the topic:
https://community.onion.io/topic/4266/editing-updating-the-distfeeds-conf-file-through-terminal/24.
3xOmega2 (of which 2 are 2+ models) were used to test the WiFi hanging problem while booting.
3xOmega2/2+ as above with docks
All three were configured as STA, another AP providing gateway service.
USB powered hub that can take the 5V supply from an external power supply. These devices have built-in power socket and the usual USB cable that goes to the computer for data exchange. The hub is powered using a 3A PS initially, that was later changed to 1A. All the Omegas were connected to the hub and booted and then powered-down using the "poweroff" command, keeping the dock's power on/off switch in ON position. This was to power all the Omegas at the same time by pulling out/re-inserting the USB power cable from/to the PS.
The CP2102s used in the dock would still be registered as ttyUSBx in the Linux system, even after issuing the poweroff command.
minicom running in a Linux station was used for the UART0 connectivity; any similar program can be used.
Pull the USB power cable from the PS (keeping the PS hot) and re-insert after a few seconds.
All the omegas are expected to complete the boot process as seen in this video:
https://drive.google.com/file/d/1nrGuAQSY1XoJC86iTrtRMzCxPhrsQop3/view
After booting, outbound connectivity is checked and then poweroff command was issued. The USB power cable was pulled out and re-inserted on the PS end to repeat the cycle.
Try as many times until we get a WiFi initialization problem. WiFi initialization draws considerable amount of power and it can fail, if power supply is not able to provide enough power.
10.Finally, I "overloaded" the PS by connecting USB Drives(they do draw power,right?)to the dock. This gave a boot failure for one Omega2+, which is uploaded here: https://drive.google.com/file/d/12udCFFuTlSrgCTRREVB2k_jU-_pr9Ms8/view
Bottom line is, use a good PS that can stand load. I have done many many reboots with different PS (3.0, 1.5, 1.0 A) and
the boot failure for Omega (ttyUSB2) occurred when the supply voltage dropped below 4.8 volt.
If you want to interface a lot of devices, you would typically adopt mux/demux technique, with a middle-level "device aggregator".
See this: https://www.instructables.com/id/Tims-PCA9685-Controller
One side (the micro-controller -uC- facing side) is I2C, while the "physical device" facing side is PWM. The micro-controller talks to 9685 (device aggregator), which in turn would talk to the devices connected to its 16 channels.
Note that the above URL has Atmel 8-bit uC/Arduino as the "controlling platform". The point is that, we are making use of the I2C interface which is present in almost any uC .
Further, the data sheet of the 9685 provided in the above link:
https://cdn-shop.adafruit.com/datasheets/PCA9685.pdf says that, "The
PCA9685 operates with a supply voltage range of 2.3 V to 5.5 V and the inputs and outputs are 5.5 V tolerant". So, you can drive it using 3.3v.
Picking the the right hardware to meet a "specific requirement" is an art, that takes time to get anywhere near the mastery. Getting used to the "datasheet" is the basic requirement. Luckily, the Internet has tons of resources providing implementation details of various project.
crispyoz :
300 baud and then 1200 baud..? So lucky..
Read somewhere, it was the time Kevin Mitnick was doing his research .!
I was dialing into a terminal/access server situated in a data center with 256kbps backbone over G.703 copper. The days of redhat 5 (not RHEL)..
@kottes
Looks like os.system() is not passing the result of cmd to w.
Try this:
import subprocess
cmd = "cat /sys/class/leds/input3::numlock/brightness"
ret = subprocess.check_output(cmd, shell = True).strip()
if ret == b'1':
print("NumLock ON")
Thanks.
@jimbo8098
https://archive.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/
has the onion-omega images released on Tue Mar 15 18:48:22 2016
https://downloads.openwrt.org/releases/19.07.8/targets/ar71xx/generic/
has the onion-omega images realeased on Mon Aug 2 02:29:04 2021
The 18.06.x version is available from:
https://downloads.openwrt.org/releases/18.06.9/targets/ar71xx/generic/
Thanks.
@optech
Happy to know that the intial phase is over.
So, what is next?
https://github.com/OnionIoT/omega2-lmic-lorawan
-interfacing to Omega2 through SPI-I2C bridge,library supports SX1276/8)
https://www.seeedstudio.com/LoRa-E5-Wireless-Module-p-4745.html
-Cortex-M4+SX126X(ST Micro), Comes with factory loaded AT command fw,
supports ClassA/B/C, has built-in UART/ADC/I2C/GPIO.. & programmamable using ST CubeMX)
Or any other? Curious to know which is your pick..
(I was not aware of that this chirpy thing existed .. !!)
Thanks
@victoriano :
<<
prefer mainline distros over very specialised ones.
<<
Very true, and I totally agree..
At the same time, we have to look at the value a specific implementation brings into the table. If we consider, I2C is an abstraction of 2 GPIO pins (two pins are configured to work together, either at s/w level or h/w level) to from an I2C bus, that does indeed brings in some value.
ESPs do I2C at s/w level and their I2C is limited to 100kHz max from a core running at 160MHz, while the h/w implementation of AVR 328P can support 400kHz bus @16MHz.
To my knowledge, OpenWRT is focusing on WiFi routers while Omega2 is focusing on IoT and peripheral connectivity.
Thanks..
@evelina :
This was already reported here?:
https://community.onion.io/topic/4279/onion-2s-does-not-save-any-data?_=1601466555447&lang=en-GB
I guess you have followed @crispyoz 's recommendation to check custom pcb's circuit with the reference available at:
https://github.com/OnionIoT/Omega2/blob/master/Schematics/Omega2S-Reference-Schematic.pdf
There was another problem reported in the above thread, that files that you created were vanishing after reboot. Were you able to save your files properly after following @György-Farkas 's advice?
Pls post the outcome..
Coming back to this thread, "the inserted sd card is not recognized", I have TWO images for you.
As you can see, there are 8 wires required
Please get an adapter, solder the wires and connect your custom pcb, making sure that you follow connection provided in the above PDF. This would simplify the debugging.
Thanks..
According to:
https://support.microsoft.com/en-us/help/310123/error-codes-in-device-manager-in-windows
<<
Full Error Message
"This device cannot start. Try upgrading the device drivers for this device. (Code 10)"
Cause
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:
https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware-winpc/error-the-device-cannot-start-code-10-on-windows/0010e6d7-bebc-40b9-9914-98f00518256a
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.
Thanks..
@ckielstra :
I would add that an IP table rule be declared. For example:
iptables -I INPUT 1 -i br-wlan -m mac ! --mac-source <br-wlan MAC>
-j DROP or similar.
For two nodes to communicate, the MAC must be different. The above would block any MAC that is not <br-wlan MAC> on interface br-wlan which is effectively any wireless node.
Thanks..
@evelina :
Are you using your in-house designed board or an onion board ?
What is the firmware version ?
Can you check if the documents and folders that are created under /root persist the reboot ?
While booting it says similar to the following, I guess ?
[ 5.983254] mmc0: new high speed SDHC card at address 0001
[ 5.998223] mmcblk0: mmc0:0001 SD 7.44 GiB
If you run:
:/# fdisk -l /dev/mmcblk0 what does it report ?
<<
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:
https://en.wikipedia.org/wiki/Kismet_(software)#/media/File:Kismet-2.7.1-screenshot.gif
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.
Thanks..
@crispyoz :
This is my observation :
Had he completed Harward, world wouldn't have had broken windows..
The MRE in sgi mips architecture was a break through(the entire hardware works like a pointer), supported by 80Gbps interconnect let the world watch general pupose processor generated animations, 30 yrs back. Though I am junior by all means, I too feel, innovations were sacked.
After reading your post, I switched to Omega2+ to provide gateway service to my primary workstation. The Omega is using a Linksys WiFi as its gateway, and is powered with an expansion dock.
The connectivity is:
WS (WiFi) => Omega2+ (AP+STA) => Linksys => Internet.
It is more than 5 days since my experiment started; and the workstation was never shutdown. Here is the last dmesg line from the workstation:
[502020.417869] usb 2-1.6: USB disconnect, device number 89.
When I check the logs, I don't see any WiFi related problems. Needless to say,I never had any connectivity problems while using the workstation.
I can access the Omega2+ (and the Linksys as well), using my cellphone from about 100 feet away, two dry walls in the middle.
I use an apple A1400 power supply (5V, 1A) using the expansion dock, to power the Omega. I also used the power supply that came with a Xperia without any problems. When I used another power supply, that came with another cellphone, I had problems.
Bottom line is, Omega is stable wrt WiFi, as long as you feed it with a reputed power supply.
I would advise you to carry out the following.
1.Download the "omega2p-v0.3.2-b233.bin" from http://repo.onioniot.com/omega2/images/
It is the b233 release of the firmware for Omega2+ into your workstation.
So you have a backup for future use.
2.scp or use a sd card to transfer the fw to Omega's /tmp directory
3.Execute:
:tmp# sysupgrade -n omega2p-v0.3.2-b233.bin
from the UART0 connection. This will upgrade and reboot the omega.
4.Execute:
:/# wifisetup
and select "1) Scan for Wifi networks". It will give the list of available WiFi APs, as below:
Selection: 1
Scanning for wifi networks...
Select Wifi network:
1.D-Link
2.linksys
5.Pick your choice and provide the key, as below:
Selection: 2
Network: linksys
Encryption type: psk2
Enter password:
That is all about the wifi setup. Once you get the prompt back, you can check the Internet connectivity by ping'ing some hosts in the Internet.
It is advisable to change the default AP key of the Omega2+. For that execute:
:/# uci set wireless.ap.key='your_new_key'
:/# uci commit
:/# /etc/init.d/network restart
If you executed, the "uci set.." command before #4, the other two commands would have been automatically executed by the wifisetup.
Let us know how it goes..
Thanks..
@William Scott :
<<
Good work!
<<
I guess that is for missing one zero each, in everyplace ..!
For a working Omega, the easiest way would be using the sysupgrade.Download the onion fw(2p image)from http://repo.onioniot.com/omega2/images/ ,
(I used the b233 to upgrade mine) to the workstation, copy the same to /tmp of Omega. A USB drive/scp can be used. Now, the fw is in /tmp.
/tmp# sysupgrade -n <[fw]>
would do the job. Omega will auto-reboot after the upgrade.
Thanks..
Using the Expansion Dock with Omega2, running FW, 0.3.2 b233.
Please see the image that shows the termination of pins. Let us choose PWM CH1, marked as pin 19. Let us check the current GPIO configuration.
root@Omega-CCC9:/# omega2-ctrl gpiomux get
Group i2c - [i2c] gpio
Group uart0 - [uart] gpio
Group uart1 - [uart] gpio pwm01
Group uart2 - [uart] gpio pwm23
Group pwm0 - [pwm] gpio
Group pwm1 - [pwm] gpio
Group refclk - refclk [gpio]
Group spi_s - spi_s [gpio] pwm01_uart2
Group spi_cs1 - [spi_cs1] gpio refclk
Group i2s - i2s [gpio] pcm
Group ephy - [ephy] gpio
Group wled - wled [gpio]
=>pwm1 is configured for pwm
root@Omega-CCC9:/# dht-sensor 19 DHT11
humidity: -255.000000
temperature: -255.000000
=>We get the wrong readings. Let us reconfigure pwm1..
root@Omega-CCC9:/# omega2-ctrl gpiomux set pwm1 gpio
set gpiomux pwm1 -> gpio
=>And verify pwm1 has changed to gpio.
root@Omega-CCC9:/# omega2-ctrl gpiomux get
Group i2c - [i2c] gpio
Group uart0 - [uart] gpio
Group uart1 - [uart] gpio pwm01
Group uart2 - [uart] gpio pwm23
Group pwm0 - [pwm] gpio
Group pwm1 - pwm [gpio]
Group refclk - refclk [gpio]
Group spi_s - spi_s [gpio] pwm01_uart2
Group spi_cs1 - [spi_cs1] gpio refclk
Group i2s - i2s [gpio] pcm
Group ephy - [ephy] gpio
Group wled - wled [gpio]
=>Let us try again..
root@Omega-CCC9:/# dht-sensor 19 DHT11
humidity: 87.000000
temperature: 28.000000
=> Put the pwm1 back to pwm
root@Omega-CCC9:/# omega2-ctrl gpiomux set pwm1 pwm
set gpiomux pwm1 -> pwm
=> And try..
root@Omega-CCC9:/# dht-sensor 19 DHT11
humidity: -255.000000
temperature: -255.000000
=>Once again, put pwm1 to gpio.
root@Omega-CCC9:/# omega2-ctrl gpiomux set pwm1 gpio
set gpiomux pwm1 -> gpio
root@Omega-CCC9:/# dht-sensor 19 DHT11
humidity: 87.000000
temperature: 28.000000
=> Try DHT22
root@Omega-CCC9:/# dht-sensor 19 DHT22
humidity: -255.000000
temperature: -255.000000
The DHT11 usually have 3v-5v operating range, with 5v5 specified as the max voltage. I used 3v3, not 5v; using 5v would probably damage the 3v3 inputs of Omega2. Also, the DHT11 I have already has the pull-up built onto the assy.
Note: I have only 3 days hands-on with Omega. I could be wrong in the commands and config above.
#/media/File:Kismet-2.7.1-screenshot.gif){kind=link}