As that was my thread I'll join in here.
I ended up resolving my issue by purchasing and attaching an antenna.
I had made the assumption that the device would be ok without one if it was near the router, but that was not the case. The antenna made things a lot better.
You're trying to run that command inside the python interpreter in interactive mode, but you need to run it on the command line in your shell. The python command will also need to be in your path, there was a checkbox for that during install. (You may have already selected it and be good to go.)
@crispyoz Following that logic you could also say that bringing up another interface shouldn't cause the routing to be updated in favor of that interface as that may not be your intention. Yet that is what currently happens. And if the routing is going to be modified when I bring up that interface, I'd expect the changes to be reverted when I bring it down.
@Lazar-Demin Ok I will take a look.
Hey Guys -- @Lazar-Demin,
Pulling out the LTE for another project and came across another issue.
I updated to the latest firmware and was delighted to see that the "o2lte" command was correctly disabling the LTE data now. (I haven't tested sharing yet.)
However I did notice that when you disable the LTE data, the Omega does not fix the routing table.
When you boot your board and are connected to WiFi, the default route is correctly configured to use that.
If you then enable LTE data, the default route is correctly configured to go out of that interface.
However, when you then disable the LTE data there is no default route added back to the routing table so some traffic will fail. At this point there is no default route at all.
If we could get this fixed and another firmware pushed out, let me know and I'll test it.
Edited -- Enabling and disabling LTE sharing works well too now.
Thanks,
Nate
I found a thread in the lvgl forums where @Lazar-Demin was talking to those guys trying to get a working build of micropython + lvgl for the omega here: lvgl forums. Unfortunately I don't know if he was successful or not and couldn't find a package anywhere for it. I'm not a c coder and would very much be interested if someone knows how to get micropython + lvgl working on the omega 2.
@Marko-Lukat Thanks so much that did indeed fix it. Are there any other gotcha's you've learned with this board that someone should be aware of if they are trying to use it in a real project? Thanks so much.
@Lazar-Demin I hope we can get a fixed firmware for everyone else?
I'm also having issues controlling the gnss on this board.
Firstly, the enable / disable of o2lte doesn't seem to do anything at all. gnss is active on device boot and disable doesn't seem to stop it.
Furthermore /etc/init.d/ugps does seem to work as far as ubus call gps info is concerned however regardless of it's enabled or not I can always do cat /dev/ttyUSB1 which the documentation implies should not work if /etc/init.d/ugps is enabled.
I saw you were working on getting a build of micropython with lvgl for the Omega2 working here. I was wondering were it stood and if you were able to get it working?
@Marko-Lukat
That did indeed help thank you. Honestly I wasn't quite sure what the thinking was making the extra call to lted-run in the first place just to do those two commands. I just figured I was missing something.
@Lazar-Demin Can we get a fix for this and a firmware update please? Seems like we don't get firmware updates as often as I would have thought.
With the current firmware, if I have a SIM card in the board, when I boot it the cellular interface is up on it's own. Running o2lte data disable doesn't turn it off. I have to bring down the interface manually, remove the default route manually and add a new default route pointing back to the network gateway. It's very frustrating.
Considering it's just OpenWrt / linux I'm sure there is a way. I'll keep digging into it. Might just need to swap ap / sta.
Hello everyone,
Checking on multiple different lte boards, I noticed that once connecting to an apn ( i tried hologram and tmobile ) turning off the data connection doesn't seem to work. Even though o2lte says it turns it off, the interface is still there, it still has an ip address and traffic is still routing out off it.
There also seems to be an issue switching from one apn to another. If I add a sim after a fresh restart, it will provision it correctly, but if I want to switch to a different sim and run the apn command again, it doesn't switch correctly.
Thanks,
Nate
@György-Farkas That seems like a pretty big security concern to me. Why would a device that once connected no longer needs it's ap be forced to be broadcasting as one where anyone could attack it?
Hello,
I do not want to completely turn off the radio. In fact that is what happened to me which I wasn't trying to do. I just want to turn of the ap.
Thanks,
Nate
@Lazar-Demin I tend to prefer to connect to the omegas through my router once they are connected to it, instead of through their own ap. In fact I just put up another thread asking what the correct way to disable the ap is because when I tried, the sta connection never would come back up once I disabled the ap one and Ihad to connect back via the ethernet expansion.
I have a really good router but ended up buying little antennas to attach to the omegas. They have been working a lot better since then. The internal ones seem to be a bit lacking to me.
Hello everyone,
I am wondering how one might go about disabling the built-in AP on the omega devices.
I've tried both with an original 2+ as well as the newer LTE one. I have had the same results on both.
What I did was the following commands:
uci set wireless.ap.disabled=1
uci commit wireless
/etc/init.d/network restart
In both cases the wireless connection would not come back up and let it reconnect with the router. I had to put on the ethernet expansion and plug it in to the router to get back on it. Does anyone have any ideas on the propper way to do this? From what I read this was supposed to be the propper way.
Thanks,
Nate
@David-Ivan-Azcarate said in Ultrasonic sensor on omega2 via node red:
JSN-sr04t 2.0
I'm not sure if this will be helpful but when I was looking up that sensor I came across this forum thread where the modes are broken down.
@crispyoz Nah the system isn't under any load CPU or memory wise. This is definitely network related in my opinion.
@Douglas-Kryder Ok thank you sir! I'll give those a read and see what I can do. I really wanted to use a few Omega 2+s with the Mini Docks as some cheap network cameras around the house. If I can't get this resolved though I may have to switch to some rPi Zero Ws.
Anyone else get really bad lag on their Omegas? Fresh reset on my 2+, installed mjpeg-streamer (nothing else), and now I SSH in, type a command and have to wait 5s or so for it to catch up. Also if I change the camera, it will take 15s or so for the picture to change. It was running better than this before with the only issue being a jerky picture after running for an hour or so. Any thoughts / suggestions?
Thanks
@Lazar-Demin You beat me to it, I was just about to post that in response.
@crispyoz Keep in mind though we do only have USB2 so there will still be a bottleneck.
So I've been working on making a project that needs to utilize the USB GPS and a cellular data connection. I got my Hologram SIMs (although I think Ting would be cheaper) and went to order the cellular expansion and... nope. Apparently they were only for sale on Kickstarter. Looking in the forum I also found someone talking about not being able to use the cellular expansion and the USB GPS both due to some sort of restriction of only one device allowed to be created on the Omega.
So is there any hope? Any alternative cellular card I could use along with the USB GPS dongle? I tried asking support but have only gotten back silence.
Any help would be appreciated.