I reflashed my device with standard OpenWrt 18.06 and it works great.
Procedure and experience on my blog:
Connect smart phone to the Omega’s WiFi Network and try to use IP address http://192.168.3.1.
Updated to 0.3.2 b218 two hours ago (Omega 2+). Problem remains. Additionally static ip network setup fails now. Worked with the delivery version.
Yes, static IP setup fail from old versions, I need to setup gateway manually for internet access, see this post:
I'm using firmware 0.3.2 b217 (Omega2+).
This problem only occurs if the ethernet is plugged during the boot-up and is removed later. The wireless connection connection stops working at this moment.
If the ethernet cable is plugged after boot-up and is then removed, the wireless connection remains totally correct.
This seems to be a FIRMWARE-BUG.
Hi, which firmware version are you using ? (just for information).
Well, I think is a problem of routing tables:
route -n command with DHCP (default device config):
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 apcli0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 apcli0 192.168.1.1 0.0.0.0 255.255.255.255 UH 0 0 0 apcli0 192.168.3.0 0.0.0.0 255.255.255.0 U 0 0 0 br-wlan
With STATIC IP config:
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 apcli0 192.168.3.0 0.0.0.0 255.255.255.0 U 0 0 0 br-wlan
So, I route manually with command:
# route add default gw 192.168.1.1
ping google.com works...
Device IP address 192.168.1.95 and router/gateway in 192.168.1.1.
Modify interface 'wwan' in file
/etc/config/network as follow:
config interface 'wwan' option ifname 'apcli0' option proto 'static' option hostname 'Omega-XXXX' option ipaddr '192.168.1.95' option netmask '255.255.255.0' option gateway '192.168.1.1' option dns '22.214.171.124'
If you use the Access Point (example a phone connected to Omega as Wi-Fi client) add DNS servers to
# Use public DNS servers for Access Point when # static IP is used for 'wwan' interface. server=126.96.36.199 server=188.8.131.52
Add these commands to
/etc/rc.local to update config on next boot:
# ---------------------------------------------------------- # COMMANDS FOR STATIC IP CONFIG # ---------------------------------------------------------- # Add routing table (need it for STATIC IP config) route add default gw 192.168.1.1 # Restart Dnsmasq for update DNS servers (only Access Point) /etc/init.d/dnsmasq restart
Check if the
route -n has a similar output:
Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 apcli0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 apcli0 192.168.3.0 0.0.0.0 255.255.255.0 U 0 0 0 br-wlan
And ofcourse, try
ping google.com command.
In my humilde opinion there are a config bug for static IP, maybe Onion would fix it.
dnsmasqprogram interferes? What does
Maybe... I try all configurations in
/etc/config/dhcp, but it doesn't work.
/etc/resolv.conf is modified by
dnsmasq after boot.
i work in DHCP but with a static lease with the MAC Address of apcli0 (xxxxx0E for you but not the MAC Address of the Omega Label )
my router is a Mikrotik and this system work for all IOT (ESP 8266 / ESP 32 / 4Duino ...)
Hi, It's no apply in this case, because I'm finding a solution without modify router setup.
I'm trying to use static IP for the Omega2, last firmware 0.2.0 (b194).
All works fine, except DNS setting.
This is my
/etc/config/network file config:
config interface 'wwan' option ifname 'apcli0' option proto 'static' option hostname 'Omega' option ipaddr '192.168.1.95' option netmask '255.255.255.0' option gateway '192.168.1.1' option dns '184.108.40.206'
After network config restart with command
/etc/init.d/network restart, I try to ping to google with:
root@Omega # ping google.com ping: bad address 'google.com'
It can't resolve hostnames with static IP configuration. If I use DHCP config, no problem.
apcli0 Link encap:Ethernet HWaddr 40:A3:6B:C1:44:0E inet addr:192.168.1.95 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::42a3:6bff:fec1:440e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Anybody use static IP? Can share configuration files?.
Thanks in advance!
According to https://community.onion.io/post/15771 the GPIO pins support four ports but they don't come preinstalled or free! Likewise the Pi Zero has 17 spare pins. Pi Zero W for $10 has Wi-Fi and Bluetooth.
Pi Zero don't have Ethernet and Flash memory. Flash memory is better to avoid data corruption on systems with unstable power supplies.
BTW, in some environments Wi-Fi is not a option.
IMHO, Omega is better for migrate from advanced MCU applications than Pi Zero.
Another point is that Omega have a metal shield for radiated EMI, Pi Zero don't have.
If you want a full computer with monitor, sound, keyboard, use Raspberry or a PC.
@Oximoron I think that's done on the expansion board. Like I said I have used external power to the expansion instead of from the Omegas power supply. The documentation says they are isolated so I am assuming so.
Are you using this board?
I can't see any opto-coupler. Just a PCA9685 (I2C bus), two 2N7002 and two diodes, resistors, caps...
You have two power supplies, but GND is the same for servo electronics and Omega CPU.
I think that you have to isolate I2C port signals in this case (expensive solution, depends of your final application).
Other option is try to put fast-diodes near to servos, power supplies, add filters, capacitors...but definitive and reliable solution is isolate control signals.
Hi any help appreciated. I have been trying to use a sail winch servo that can spin 360 degree. I have also tried regular servos. The problem happens when I send a PWM signal using the web console app. The device crashes the dock and the onion based on certain values. Is this normal. I use external power supply but same results either way. I know I can send the servo past its edge and it will chatter, but thats not when it crashes. Once it crashes it will reset consistently until you unplug the servo. Then the device resets but the port on the PWM board no longer works. You have to then reset the whole board. So it sounds like the chip on the expansion crashes but doesn't get reset. So does anyone else see the same thing or is it just my expansion board.
Has anyone used a sail winch servo or hacked a regular servo to spin 360.
That sound like a EMI (Electromagnetic interference) becouse you're controlling inductive loads. No software solution is possible.
Try to isolate Omega power supply from Servo power supply. That is, ground and supply line can't be the same. You need two power supplies.
You can do this by using fast-optocouplers for PWM signal.
Omega PWM -> Fast-Opto -> PWM Servo
Pay attention in optocoupler speed.
Looks like your connection to Community was lost, please wait while we try to reconnect.