This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm that you accept these cookies being set.

SMS Problem on Reactor
#1
Good morning,
I am having an issue with SMS messages from the reactor. I have verified that the SIM card is working, as email functionality—which uses the same SIM—is operating correctly. I have also checked the SMS script, and everything appears to be in order.
There are no errors showing in the log.

Thank you very much.
Reply
#2
Do you mean sending or receiving SMS messages? Add logging as suggested in this post: https://forum.logicmachine.net/showthrea...3#pid38043
Reply
#3
(09.11.2026, 08:22)admin Wrote: Do you mean sending or receiving SMS messages? Add logging as suggested in this post: https://forum.logicmachine.net/showthrea...3#pid38043

Nothing appears in the log ?
Reply
#4
Have you restarted the resident script after changing the user library? Anything in Alerts and Error logs?
Reply
#5
(09.11.2026, 12:39)admin Wrote: Have you restarted the resident script after changing the user library? Anything in Alerts and Error logs?

Yes, I’ve restarted the SMS resident  script, but there are no alerts or errors.
Reply
#6
You should at least get "SMS handler init" and "SMS handler started" / "SMS USB init failed" alerts when the resident script starts. Do you get these alerts?
Reply
#7
(09.11.2026, 13:49)admin Wrote: You should at least get "SMS handler init" and "SMS handler started" / "SMS USB init failed" alerts when the resident script starts. Do you get these alerts?
nothing

(09.11.2026, 13:49)admin Wrote: You should at least get "SMS handler init" and "SMS handler started" / "SMS USB init failed" alerts when the resident script starts. Do you get these alerts?
nothing
Reply
#8
Send your LM backup via PM.
Reply
#9
(09.11.2026, 14:05)admin Wrote: Send your LM backup via PM.

in PM is not possible to add file
Reply
#10
Use some file sharing service like WeTransfer
Reply
#11
Run this script once and post what you get in Logs tab:
Code:
res = io.readproc('ls /sys/class/tty') log(res)
Reply
#12
(09.11.2026, 16:11)admin Wrote: Run this script once and post what you get in Logs tab:
Code:
res = io.readproc('ls /sys/class/tty') log(res)



* string: console
ptmx
tty
ttyUSB0
ttyUSB1
ttyUSB3
ttyUSB4
ttyUSB5
ttymxc0
ttymxc1
ttymxc2
ttymxc4
ttymxc5
Reply
#13
Reboot LM and post what you get in System config > Status > System log.
Reply
#14
Code:
Nov 10 08:14:31 LAMBO-CAB4 daemon.info avahi-daemon[1322]: Registering new address record for 10.147.20.25 on ztppiynnew.IPv4. Nov 10 08:14:31 LAMBO-CAB4 daemon.info avahi-daemon[1322]: New relevant interface ztppiynnew.IPv4 for mDNS. Nov 10 08:14:31 LAMBO-CAB4 daemon.info avahi-daemon[1322]: Joining mDNS multicast group on interface ztppiynnew.IPv4 with address 10.147.20.25. Nov 10 08:14:16 LAMBO-CAB4 daemon.notice pppd[1419]: secondary DNS address 10.128.28.16 Nov 10 08:14:16 LAMBO-CAB4 daemon.notice pppd[1419]: primary DNS address 10.133.106.110 Nov 10 08:14:16 LAMBO-CAB4 daemon.notice pppd[1419]: remote IP address 10.64.64.64 Nov 10 08:14:16 LAMBO-CAB4 daemon.notice pppd[1419]: local IP address 100.106.52.131 Nov 10 08:14:16 LAMBO-CAB4 daemon.notice pppd[1419]: replacing old default route to eth0 [192.168.0.1] Nov 10 08:14:16 LAMBO-CAB4 daemon.info avahi-daemon[1322]: Registering new address record for 100.106.52.131 on ppp0.IPv4. Nov 10 08:14:16 LAMBO-CAB4 daemon.info avahi-daemon[1322]: New relevant interface ppp0.IPv4 for mDNS. Nov 10 08:14:16 LAMBO-CAB4 daemon.info avahi-daemon[1322]: Joining mDNS multicast group on interface ppp0.IPv4 with address 100.106.52.131. Nov 10 08:14:16 LAMBO-CAB4 daemon.warn pppd[1419]: Could not determine remote IP address: defaulting to 10.64.64.64 Nov 10 08:14:14 LAMBO-CAB4 daemon.notice pppd[1419]: Connect: ppp0 <--> /dev/ttyUSB3 Nov 10 08:14:14 LAMBO-CAB4 daemon.info pppd[1419]: Using interface ppp0 Nov 10 08:14:14 LAMBO-CAB4 daemon.info pppd[1419]: Serial connection established. Nov 10 08:14:12 LAMBO-CAB4 daemon.notice pppd[1419]: pppd 2.4.9 started by root, uid 0 Nov 10 08:14:09 LAMBO-CAB4 daemon.info pppd[1417]: Exit. Nov 10 08:14:08 LAMBO-CAB4 daemon.err pppd[1417]: Connect script failed Nov 10 08:14:05 LAMBO-CAB4 daemon.notice pppd[1417]: pppd 2.4.9 started by root, uid 0 Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.757104] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB4 Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.756522] option 2-1:1.4: GSM modem (1-port) converter detected Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.755492] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB3 Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.754884] option 2-1:1.3: GSM modem (1-port) converter detected Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.747381] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2 Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.745184] option 2-1:1.2: GSM modem (1-port) converter detected Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.744191] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1 Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.743594] option 2-1:1.1: GSM modem (1-port) converter detected Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.741249] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0 Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.740627] option 2-1:1.0: GSM modem (1-port) converter detected Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.737678] usb 2-1: SerialNumber: 0123456789ABCDEF Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.737666] usb 2-1: Manufacturer: SimTech, Incorporated Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.737654] usb 2-1: Product: SimTech, Incorporated Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.737642] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.737612] usb 2-1: New USB device found, idVendor=1e0e, idProduct=9001, bcdDevice= 3.18 Nov 10 08:14:01 LAMBO-CAB4 kern.info kernel: [ 10.569367] usb 2-1: new high-speed USB device number 4 using ci_hdrc Nov 10 08:13:59 LAMBO-CAB4 daemon.info avahi-daemon[1322]: Registering HINFO record with values 'ARMV7L'/'LINUX'. Nov 10 08:13:59 LAMBO-CAB4 daemon.info avahi-daemon[1322]: Server startup complete. Host name is LAMBO-CAB4.local. Local service cookie is 716297664. Nov 10 08:13:59 LAMBO-CAB4 daemon.info avahi-daemon[1322]: Registering new address record for 192.168.0.10 on eth0.IPv4. Nov 10 08:13:59 LAMBO-CAB4 daemon.info avahi-daemon[1322]: Registering new address record for fe80::88cd:18ff:feab:4b4d on ztppiynnew.*. Nov 10 08:13:59 LAMBO-CAB4 daemon.info avahi-daemon[1322]: Network interface enumeration completed. Nov 10 08:13:59 LAMBO-CAB4 daemon.info avahi-daemon[1322]: New relevant interface eth0.IPv4 for mDNS. Nov 10 08:13:59 LAMBO-CAB4 daemon.info avahi-daemon[1322]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.10. Nov 10 08:13:59 LAMBO-CAB4 daemon.info avahi-daemon[1322]: Loading service file /etc/avahi/services/lm.service. Nov 10 08:13:59 LAMBO-CAB4 daemon.info avahi-daemon[1322]: Loading service file /etc/avahi/services/http.service. Nov 10 08:13:59 LAMBO-CAB4 daemon.info avahi-daemon[1322]: avahi-daemon 0.8 starting up. Nov 10 08:13:59 LAMBO-CAB4 daemon.info avahi-daemon[1322]: Successfully dropped root privileges. Nov 10 08:13:59 LAMBO-CAB4 daemon.info avahi-daemon[1322]: Found user 'nobody' (UID 65534) and group 'nogroup' (GID 65534). Nov 10 08:13:58 LAMBO-CAB4 user.info sysinit: No packages removed. Nov 10 08:13:56 LAMBO-CAB4 user.info sysinit: Failed to get init ACK from device: 57 196 Nov 10 08:13:54 LAMBO-CAB4 user.info sysinit: /lib/genohm-scada/storage/db/current.db: OK
(10.11.2026, 07:42)admin Wrote: Reboot LM and post what you get in System config > Status > System log.
Reply
#15
Do you have any logs in LM Logs tab related to the SMS script now?
Reply
#16
(10.11.2026, 08:24)admin Wrote: Do you have any logs in LM Logs tab related to the SMS script now?

Yes , I have this error from sms script



* arg: 1
  * string: read timeout
* arg: 2
  * table:
Reply
#17
This looks like a hardware issue. Just to be sure, can you provide remote access via ZeroTier?
Reply
#18
(10.11.2026, 13:03)admin Wrote: This looks like a hardware issue. Just to be sure, can you provide remote access via ZeroTier?

Yes try to connect to this network ... and  I autorize access , ip of LM is ...
Reply


Forum Jump: