search

aesthernr / quectel-rgmii-simpleadmin

17 stars 16 forks source link

Reboot of 520n Modem #3

Open viberama opened 1 year ago

viberama commented 1 year ago

Rebooting the 520n Modem shows all of simpleadmin parameters, after the browser refreshes in 30 seconds, the info disappears. Only a reboot brings back the info for another 30 seconds. Rinse/repeat

iamromulan commented 1 year ago

I have a similar problem. The only thing that will show is the modem temperature. The rest of the data is missing. AT command responses don't show up either. Telnet works as intended as far as I can tell.

viberama commented 1 year ago

Telnet is fine and I can see the information in Telnet but the info in simpleadmin doesn't populate to the proper fields other than the temperature. That does seem to work all the time.

viberama commented 1 year ago

This is a screen shot of what I'm seeing on http://192.168.225.1:8080/. The data updated section never changes unless I telnet in and run an AT command like AT+QCAINFO or AT+QTEMP, etc. Then the data updated section updates but the information is never populated into simpleadmin. As you can see in the second screen shot, the data was updated but now I don't get information including the Temp:

simple

simple2

rbflurry commented 1 year ago

I have found this is due to the sleep here.

https://github.com/aesthernr/quectel-rgmii-simpleadmin/blob/603167e672f32e6f658534d6d26ebe8ccaa68e04/scripts/get_modem_data.py#L31

The delay causes the script to miss the responses from most of the AT commands

dr-dolomite commented 1 year ago

I have found this is due to the sleep here.

https://github.com/aesthernr/quectel-rgmii-simpleadmin/blob/603167e672f32e6f658534d6d26ebe8ccaa68e04/scripts/get_modem_data.py#L31

The delay causes the script to miss the responses from most of the AT commands

So should we comment it out or adjust for other value?

rbflurry commented 1 year ago

@dr-dolomite Could you try to do this instead.

systemctl disable at-telnet-daemon
systemctl stop at-telnet-daemon

This will disable the use of sending AT commands over Telnet to port 5000 and I think helps the timing of things.

Currently the at-telnet-daemon seems to run in a loop using 100% of the cpu. by stopping it. it the dashboard seems more stable

viberama commented 1 year ago

Is this a temporary or permanent fix? I like having the option to send telnet commands over port 5000.

rbflurry commented 1 year ago

Temporary. Need to work with both devs on a fix.

r2d2land commented 1 year ago

I haven't been able to get the at_telnet_daemon to work, but everything in the simple admin works as designed except results don't print in the gui. The commands go through and the modem responds. When I send telnet 192.168.225.1 5000 on any client....the connection fails. Only time it works is via usb under adb.

viberama commented 1 year ago

Temporary. Need to work with both devs on a fix.

Ok, thanks for your hard work on this project 👍

viberama commented 1 year ago

What is the command to stop simpleadmin? I'd like to wait to use it until you get the kinks worked out. Is it:

adb shell systemctl stop simpleadmin_generate_status adb shell systemctl stop simpleadmin_generate_status.timer adb shell systemctl stop simpleadmin_httpd adb shell systemctl stop ttl-override

dr-dolomite commented 1 year ago

Temporary. Need to work with both devs on a fix.

Just a question. In the installation of AT Daemon from Nates repo, it said that I need the modem to be connected via USB.

So I need to use a USB sled to connect it to my computer or I can just connect a computer via eth on a router and use the USB interface of the modem? Thank you

Running ADB directly on openwrt router works.

dr-dolomite commented 12 months ago

I haven't been able to get the at_telnet_daemon to work, but everything in the simple admin works as designed except results don't print in the gui. The commands go through and the modem responds. When I send telnet 192.168.225.1 5000 on any client....the connection fails. Only time it works is via usb under adb.

same problem. Im stumped really. i tried everything from reflashing the modem and starting from scratch to reinstalling the scripts I still cant telnet to the given ip and port

dr-dolomite commented 12 months ago

Im also having this issue when installing the simpleadmin. Do someone has any idea on how to fix this?

Job for simpleadmin_generate_status.service failed because the control process exited with error code.
See "systemctl status simpleadmin_generate_status.service" and "journalctl -xe" for details.
rbflurry commented 12 months ago

You can try my copy. There is also an uninstall script.

It gives feedback on the at command page and seems to be more robust showing stats.

https://github.com/rbflurry/quectel-rgmii-simpleadmin

dr-dolomite commented 12 months ago

You can try my copy. There is also an uninstall script.

It gives feedback on the at command page and seems to be more robust showing stats.

https://github.com/rbflurry/quectel-rgmii-simpleadmin

thank you so much. will try this EDIT: It works! I really appreciate this

r2d2land commented 12 months ago

You can try my copy. There is also an uninstall script.

It gives feedback on the at command page and seems to be more robust showing stats.

https://github.com/rbflurry/quectel-rgmii-simpleadmin

Everything seems to work now in the gui. Thanks for sharing this!