01.07.2024, 09:01
Post what you have in System config > Status > System log.
problem with 4g modem
|
01.07.2024, 09:01
Post what you have in System config > Status > System log.
01.07.2024, 09:34
What LM hardware model are you using?
01.07.2024, 09:46
LM5p2-RIO3LTE
LM5M3CV15xA23010267
01.07.2024, 09:48
Do you have 3G/4G connection enabled? If it's disabled then the on-board modem won't be initialized.
01.07.2024, 10:19
It was disabled. When we try to enable it the LM stops responding.
01.07.2024, 10:22
This most likely caused by LM using mobile connection gateway instead of Ethernet.
Follow this guide if you only need SMS without 3G/4G: https://forum.logicmachine.net/showthrea...7#pid33127
01.07.2024, 12:05
It worked. Thanks!
I still have a strange situation. In the alert I still get "SMS handler lost connection" but the SMS are getting through. I only happens with a card from one provider. Using a card from a different provider it doesn't happen.
01.07.2024, 12:22
Modify AT:run() function in the user library as follows and post what you get in LM Logs tab.
Code: function AT:run()
01.07.2024, 14:08
Change the same function as follows and see if it helps.
Code: function AT:run()
26.09.2025, 11:22
I have the LM with the built-in LTE modem. It has been configured, so it is only used for SMS, while the RJ45 port is used for all IP traffice.
I have created the standard scripts according to the guide, and I can send SMS without any problems. This works very stable. However, when I try to send a SMS to the LTE modem, then nothing happens. An example of SMS is "W 1//1/9 false" without the quotes to turn off something. I get no response on read. My sender phone number is allowed in the script, and I have tried both with and without country code. I hope you can provide some temporary changes to the script, so I can find what I have missed. Thanks.
26.09.2025, 12:34
Do you have anything in LM Alerts tab? Messages from all numbers are logged there.
26.09.2025, 13:27
Yes, there are messages. See screen shot with todays messages, where I tried off instead of false, but with same result.
26.09.2025, 13:34
Make sure that the number is specified in the script the same way as in the alert between [].
Modify the handler function in the resident script as follows and post what you get in Logs tab: Code: handler = function(sms) For on/off use 0/1 or true/false.
26.09.2025, 13:39
I saw that the + sign in front of the country code was missing in the alert log, so I tried to remove the + sign and still country code number. That worked, and I have now for the first time received a response on a read SMS.
If I reboot the LM, and I send one SMS everything works fine. Both read and write. However, the next SMS send does not appear in the Alerts. Only if I reboot LM, it works correct for one single message. After a reboot it actually picks up the previous waiting message and responds. I am using LM reboot functionality - no power recycle.
26.09.2025, 13:40
Is the resident script configured correctly with 0 sleep time?
26.09.2025, 13:52
(This post was last modified: 26.09.2025, 13:54 by EjvindHald.)
Yes, see screen shot. The Generel Timer also shown is actually your staircase example with my own add ons.
This is my normal CPU and memory stats:
26.09.2025, 14:11
In the user library add logging to the AT:run() function:
Code: function AT:run() Then check what you get in LM Logs tab.
26.09.2025, 14:19
(This post was last modified: 26.09.2025, 14:53 by EjvindHald.)
I opened the user library and added the single line "log(res, err)" saved and tried again. Then everything worked smooth. Then I commented out that line and it still works fine with immediate reply.
Sorry for all this - I do not know why it did not work before. But it is working fine now. And I am glad that I now know where to add a log statement to gain more info in case of future problems. Thanks and enjoy your weekend. Update: after a LM reboot the same faulty behavior came back with only processing one message and then it stops. I will try to get some log info. I have now tried editing log on and off + reboot, and I cannot find a pattern in the behavior. Only thing is that it generally seems to work better when the log writing is enabled, which makes no sense to me. I cannot go with this, because the log will be flooded with messages, as it issues a timeout message every second. I never see any error messages in the log. Only many timeouts and now and then processing of a message. See screen shot. |
« Next Oldest | Next Newest »
|