Hi,

what kind of software are you using for an lte modem? Especially on the Omega2 LTE version? We tried Modemmanager and uqmi but didnt get a stable connection. We are using the omega2 pro as an travel router and sometimes its loosing its connection to the modem and never get connected again, than we have to restart the interface manually, most of the times this helps. And sometimes is completly lost an we have to restart the omega. Were using OpenWrt 22.03.05. Modem is a Quectel Ep06. So the question is what kind of software is used on the original omega2 lte?

Greetz Doc

@Lazar-Demin

Thats really great news! Will the new firmware (22.03.xx) also work with the omega2-lte? Or are there any restrictions because of the modem?

@Lazar-Demin perfect i will try this

Great work! Really love it
Now that hardware pwm is possible using command line, will there be an easy way to use pwm. Before it was possible to use

onion pwm <CHANNEL> <DUTY CYCLE> <FREQUENCY>

or should we write a python module which uses the documented command line methods?

Thx again for the great work

@Lazar-Demin
the main use is to communicate with an Analog digital converter. And many python libraries are using spidev so i think it makes sense to make this working again. Anyway if there is an alternative its also ok, but for now i didnt found a working solution in python3.

I also tried to use spi-tools for testing the spi connection and there also seems to be some errors. But i will do some further tests later and give some feedback.

Hi,

is there a way to use software emulated pwm in OpenWrt 22.03. with an Omega2+?
I know its possible in 18.06. but since 21.X OpenWrt removed the w1_gpio_custom package.

Any ideas?

@Lazar-Demin

I found this post https://community.onion.io/post/25025 and added these patches to your firmware builder for openwrt 22.03. Build and flashing was successful but not tested it yet.

Dont know but maybe it helps you in your open issues. Especially for gpio mapping.

@Lazar-Demin yes this helps thx. But we're thinking about using the USB2514B-I/M2 from Microchip do you think there will be problems with this chip and the omega?

And yes a new hardware guide would be really helpful.

Can you give more details? How did you connect the MCP23018?

We´re searching for an alternative USB Hub Controller IC with at least 3 ports which is compatible with the Omega2s. In the Omega Hardware Design Guide the GL850G-OHY37 is used, but this one is old and difficult to obtain. Any ideas or reference designs would be nice.

Thx in advance.

@crispyoz we have already 22.03. running since the beginning and also beeing part of the developing process (means we tested a lot of the new stuff and also doing some adjustements on the firmware in our system). By now we have all stuff running on 22.03. But thinking about switching to 23.05 because of beeing up to date seems better ;-)... were using almost any feature the omega has. If youre interested or for better understanding on how we use the omega you can check https://www.e1nfach.com . So the question is if its a good idea to switch to 23.05.....

Hi,

are there any Omega specific changes in 23.05. vs 22.03?
In the documentation i read about better wifi driver for example. But it hink the same driver is already implemented in 22.03, right? And i think Modemmanager is running in a newer version in 23.05 which also has some bugfixes...

Are there any other benefits with 23.05 for the omega?

I now just integrated the the mosquitto 2.0.17 package inside the firmware and removed the Mosquitto 2.0.18 package from the profile file. The i install the package after booting with the new firmware. So i just hope mosquitto will be fixed in the feature and i just can use the standard package again. If they didnt fix it i will go your way.

Thx for your help, its a nice experience to get answers really soon in the onion community!

@crispyoz said in Ask for password when using serial connection?:

uci set system.@system[0].ttylogin='1' && uci commit system

uci set system.@system[0].ttylogin='1' && uci commit system

This did the trick, Thx sir!

@crispyoz Yes and and some other libraries. Problem is that i need internet connection to install this or all the single packages.

Anyway we will use mosquitto 2.0.17, but im not sure how to integrate this when building the firmware. normally we use the profile file for this but then it takes 2.0.18. So how can we achieve to use 2.0.17 when building the firmware?

@crispyoz yeah its strange i tried your ipk but gets an error because of architecture. When im using the ipk from the source of my last post its working fine. Were using an Omega2+ with custom build firmware.

root@E1NS-d7d3:/tmp# opkg remove mosquitto-ssl
Removing package mosquitto-ssl from root...
Command failed: Not found
Not deleting modified conffile /etc/mosquitto/mosquitto.conf.
Not deleting modified conffile /etc/config/mosquitto.
root@E1NS-d7d3:/tmp# opkg install mosquitto-ssl_2.0.18-r3_mipsel_24kc.ipk
Collected errors:
 * pkg_hash_check_unresolved: cannot find dependency libopenssl3 for mosquitto-ssl
 * pkg_hash_fetch_best_installation_candidate: Packages for mosquitto-ssl found, but incompatible with the architectures configured
 * opkg_install_cmd: Cannot install package mosquitto-ssl.
root@E1NS-d7d3:/tmp#

@crispyoz Tried this but no success because of different architecture. But what i now find out is that version 2.0.15-1 and 2.0.17 of mosquitto is working as expected. Downloaded it from original openwrt packages ( https://archive.openwrt.org/releases/packages-22.03/mipsel_24kc/packages/ ). Version 2.0.18 from same source isnt. So there seems to be a bug inside the mosquitto package.

root@E1NS-d7d3:~# mosquitto -c /etc/mosquitto/mosquitto.conf
1718349698: mosquitto version 2.0.15 starting
1718349698: Config loaded from /etc/mosquitto/mosquitto.conf.
1718349698: Opening ipv4 listen socket on port 1883.
1718349698: Opening websockets listen socket on port 9001.
1718349698: mosquitto version 2.0.15 running
1718349699: New connection from 192.168.1.175:53421 on port 1883.
1718349699: New client connected from 192.168.1.175:53421 as mqtt-explorer (p2, c1, k60, u'pc').
1718349713: Saving in-memory database to /etc/data//mosquitto.db.
1718349817: New connection from 192.168.1.1:57055 on port 1883.
1718349817: New connection from 192.168.1.1:34947 on port 1883.
1718349817: New connection from 192.168.1.1:49321 on port 1883.
1718349817: New client connected from 192.168.1.1:34947 as e1ns_bridge2 (p2, c1, k60).
1718349817: New client connected from 192.168.1.1:57055 as e1ns_automation (p2, c1, k60).
1718349817: New client connected from 192.168.1.1:49321 as e1ns_hardware (p2, c1, k60).
1718349817: Saving in-memory database to /etc/data//mosquitto.db.
1718349818: Saving in-memory database to /etc/data//mosquitto.db.
1718349818: Saving in-memory database to /etc/data//mosquitto.db.
1718349818: Saving in-memory database to /etc/data//mosquitto.db.