Posts made by Jim W

You are right, not exact, but close enough.

THANK YOU !

I've ordered 400 (and a couple of other things from their cool site.

Does anyone know a source for the hair pin type connector pins (like on the OM2S-DK-SD development kit) ? I'd like to include them on a prototype board I'm working on.

@Lazar-Demin No promises expected.
But, can you put a no obligation bound on a 'few weeks' ?
If we are talking 2,3 or 4, I can wait. If we are talking 6, 8, or more I'll need to migrate my design to the SP. (FWIW, Mouser for example, projects 2+ stock in late April.)
Perhaps you could advise - for go forward, should we perhaps be migrating to the SP devices anyway ?

@crispyoz Thank you for the link to the schematics !
Unfortunately, I need additional storage so straight 2's won't work for this application.

With the Omega2+ becoming un-findable (at least right now) I'm considering moving to the 2s IF I can add an SD card to it. Based on visual review of the 2+, it does not look like a major project, but I cannot find any information or schematics on how to make the connections. (It could be my search-fu is weak.)
Can anyone direct me to any insight on doing this ?
Thanks !

December 14, 2022, Looks like everyone is out of stock on the 2+. Best I found on lead time was March 2023.

@crispyoz

Could not ping 192.168.1.1
However, found a solution in post Setting DNS with static IP config (not sure how I missed it in my initial search).

Changes wwan to

config interface 'wwan'
option ifname 'apcli0'
option proto 'static'
option hostname 'Omega-XXXX'
option ipaddr '192.168.1.202'
option netmask '255.255.255.0'
option gateway '192.168.1.1'
option dns '8.8.8.8'

and added a line to rc.local

route add default gw 192.168.1.1

That seemed to do the trick. I can ping the www (and more importantly the ntp server I needed to get the time from).

Thank you for your assistance

@crispyoz

root@Omega-5F4C:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
ping: sendto: Network unreachable
root@Omega-5F4C:~#

Strange. I edited the resolv.conf to be

nameserver 8.8.8.8
nameserver 8.8.4.4
search local domain

and saved it. Just to check I did a cat /etc/resolv.conf and is came back correctly.

I rebooted the machine. Still wont ping. Checked resolv.conf and is has been changed back to its original

search lan
nameserver 127.0.0.1

??
Still cannot ping 8.8.8.8
Looks like something is overwriting resolv.conf at reboot?

I set a static IP address for my Onion2+. Once I do that, I seem to no longer have internet access.
Local wireless router is 192.168.1.1
Static IP needed for the Onion is 192.168.1.202

Somehow, I seem to have set this up wrong. Any help appreciated !

ifconfig and /etc/config/network shown below

root@Omega-5F4C:~# ifconfig
apcli0 Link encap:Ethernet HWaddr 40:A3:6B:C9:5F:4E
inet addr:192.168.1.202 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::42a3:6bff:fec9:5f4e/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)

br-wlan Link encap:Ethernet HWaddr 40:A3:6B:C9:5F:4C
inet addr:192.168.3.1 Bcast:192.168.3.255 Mask:255.255.255.0
inet6 addr: fe80::42a3:6bff:fec9:5f4c/64 Scope:Link
inet6 addr: fd1d:48c4:7633::1/60 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:932 errors:0 dropped:0 overruns:0 frame:0
TX packets:587 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:134785 (131.6 KiB) TX bytes:57535 (56.1 KiB)

eth0 Link encap:Ethernet HWaddr 40:A3:6B:C9:5F:4D
inet6 addr: fe80::42a3:6bff:fec9:5f4d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:59 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:17583 (17.1 KiB)
Interrupt:5

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:640 (640.0 B) TX bytes:640 (640.0 B)

ra0 Link encap:Ethernet HWaddr 40:A3:6B:C9:5F:4C
inet6 addr: fe80::42a3:6bff:fec9:5f4c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1033 errors:0 dropped:0 overruns:0 frame:0
TX packets:576 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:169323 (165.3 KiB) TX bytes:47803 (46.6 KiB)
Interrupt:6

here is my /etc/config/network

config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

config globals 'globals'
option ula_prefix 'fd1d:48c4:7633::/48'

config interface 'wlan'
option type 'bridge'
option proto 'static'
option hostname'MSPPlaner'
option netmask '255.255.255.0'
option ip6assign '60'
option ipaddr '192.168.3.1'
option dns-nameservers '75.75.75.75'

config interface 'wwan'
option ifname 'apcli0'
option proto 'static'
option ipaddr '192.168.1.202'
option netmask '255.255.255.0'
option hostname 'PVPlaner

config interface 'wan'
option ifname 'eth0'
option proto 'dhcp'

YES ! EXCELLENT ! This worked.
Thank you Very Much !
(I did have to move my wlan section back to the original).

Thank you again !

Let me maybe make this simpler.
I need the 2+ to boot and attach to an existing wireless network with a static IP address. (Just as a device - not an access point.)

Can someone direct me to documentation ? (Everything I seem to be able to find is for the older OS.)

I don't really know how to explain this, but:
I changed my 2+ IP address to 10.1.10.202
I can connect to it and do the usual stuff wirelessly from my laptop by selecting its network.
My regular facility wireless network is 10.1.10.x
I'm not sure why they don't conflict.
I can ping 10.1.10.202 (the 2+) from the wired side of my facility network.
I cannot ping it from the wireless side of my facility network (i.e. from my phone connected to my facility wireless network).
If I change my phone to the 2+ network, I can ping it just fine.

I want to set up the Omega2+ as a controller on my regular facility wireless network. I will send it an http message and it will turn stuff on and off. (Program works fine if I put my phone (sending device) on the 2+ network.)
Program also works if I send it a message from the wired side of the facility network.
Does not work if the phone is on the facility wireless. Somehow, my facility wireless router makes the 2+ 'unreachable'

I am completely lost. Does this have something to do with the 2+ acting as an access point? Do I need to turn that off? Can I ?

Here is my /etc/config/network data

config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

config globals 'globals'
option ula_prefix 'fd1d:48c4:7633::/48'

config interface 'wlan'
option type 'bridge'
option proto 'static'
option hostname'MSPPlaner'
option netmask '255.255.255.0'
option ip6assign '60'
option ipaddr '10.1.10.202'
option dns-nameservers '75.75.75.75'

config interface 'wwan'
option ifname 'apcli0'
option proto 'dhcp'
option hostname 'Omega-6735'

config interface 'wan'
option ifname 'eth0'
option proto 'dhcp'

I just want to set up the 2+ as a device that I can send an http message to (using Python3 BaseHTTPRequestHandler and HTTPServer)

Any help for this poor lost duckling greatly appreciated !

Solved.

I found gpio-sysfs from https://pypi.org/project/onion-gpio-sysfs/ to work.

Ok, but Python3 I would not consider to be 'older code'.
I would think, with Pi's impossible to find, and otherwise the Omega2+ looking like a good alternative, that some emphasis might be placed on a Python3 GPIO library. I do not have any (of many) Pi programs running that don't use GPIO's in some fashion.

I'll try the Python2.x solution above (but I don't care for it much).

Really ? Kind of throws a wrench in the works.

Anyone know how to bit-bang the IO pins from within Python3 ?

Has no one else encountered this problem? Surely Python3 GPIO is supported on the Omega2+ ?

Thanks, I did not specify a channel - it's just the current channel of our 2.4 wifi.

opkg install python3
opkg install python3 pyOnionGpio
python3
.....

import onionGpio
ModuleNotFoundError: No module named 'onionGpio'

Is there something special to be done for Python 3 ?

Thanks,
Jim
(I've searched here but did not find anything - perhaps my search-fu is weak.)

Yes. 2.4GHz on channel 6. /etc/config/wireless is as above. Skipped the auto-discovery and used wifisetup. Selected a 2.4 option and connected. I do not know why this was not auto-discovered, but manual setup worked.
Thanks !