Using TRB142 with PPP over RS232 - storing settings permanently

Hi @Daumantas , could you please share the manual with me as well?

Hi everyone,
great work here, thanks.

I am trying to do the same thing with a CR800 and a TRB246.
I am letting the modem connect to internet first at boot. When I activate the Full Control mode, the connection to internet breaks. I get the error: Internal modem is in serial control

Any

Hi @AlbyDallo ,

This is the intended behavior, as modem is fully controlled by the serial device. In essence, in full control mode the router/gateway is only responsible for powering the modem. Internet connection is fully managed by the serial device.
In partial control mode, if data connection is established, the router will use it. However, this will not work with PPP, as it uses the same COM port for data and commands.

Best regards,

Hi @Daumantas , thanks for the explanation, well understood.
I will try partial control then.

Could you please share the manual?

Best regards,
Alberto

Good morning and thank you.

I’m starting to run some tests, and if you have any experience and/or suggestions, I won’t waste too much time and I’d be grateful.

So,
if I use the TRB142 normally via a ThingsMobile SIM with a fixed IP, I can reach the modem remotely.

I haven’t looked in the menus or the manual yet, nor have I tried, to see if there’s a serial server that can forward packets arriving (via the logger’s software) on port 6785 to the serial port and establish a connection with the logger. At least, that’s what I’ve done with other devices.

This, however, would be a plan B, since if the PPP procedure fails, the logger won’t know it’s on the internet and won’t be able to use the relevant protocols (email and FTP), but will only be able to answer IP calls remotely via dedicated software.

However, if I set it to full control, the TRB142 seems to stop doing anything. I assume this is because it’s waiting for AT commands on the serial port from the logger.

The logger, thanks to its programming, starts sending strings for the PPP connection. I can see the traffic on the serial port, save it, and attach it, but something isn’t working and the PPP procedure isn’t successful.

I send the traffic as an attachment when the PPP fails, and also with another serial modem when it does. Perhaps with your experience, you can figure out what’s wrong with the TRB142.

traffic with no PPP
*** NOTE: Initial modem SET phase to be performed if necessary at startup
Repeated commands for ECO
20:56:00.01 T AT&F
20:56:00.03 R
20:56:00.03 R OK
20:56:01.03 T ATE1
20:56:01.04 R ATE1
20:56:01.04 R OK
20:56:02.04 T ATX0
20:56:02.05 R ATX0
20:56:02.05 R OK
20:56:03.05 T AT+CGDCONT=1,“IP”,“JTFIXEDPUBLIC”
20:56:03.07 R AT+CGDCONT=1,“IP”,“JTFIXEDPUBLIC”
20:56:03.10 R
20:56:03.10 R OK
20:56:04.10 T AT+IPR=57600
20:56:04.11 R AT+IPR=57600
20:56:04.12 R
20:56:04.12 R OK
20:56:05.12 T AT&W0
20:56:05.13 R AT&W0
20:56:05.13 R OK
20:56:06.14 T AT+csq
20:56:06.15 R AT+csq
20:56:06.15 R +CSQ: 15
20:56:06.16 R ,99
20:56:06.16 R
20:56:06.16 R OK
*** NOTE Once the setup is complete, PPP is activated and the logger starts sending the strings
20:57:00.72 T A
20:57:00.73 R A
20:57:00.73 T T
20:57:00.74 R T
20:57:00.75 T D
20:57:00.76 R D
20:57:00.76 T *
20:57:00.77 R *
20:57:00.77 T 9
20:57:00.78 R 9
20:57:00.78 T 9
20:57:00.79 R 9
20:57:00.79 T *
20:57:00.80 R *
20:57:00.80 T *
20:57:00.81 R *
20:57:00.81 T *
20:57:00.82 R *
20:57:00.82 T 1
20:57:00.83 R 1
20:57:00.83 T #
20:57:00.84 R #
20:57:00.84 T
20:57:00.85 R
20:57:00.86 R
20:57:00.86 R CONNECT
20:57:02.72 T ~.}#.!}!}!} }4}“}&} } } } }%}&Y}”..}‘}“}(}”..~
20:57:02.74 R ~.}
20:57:02.75 R #.!}!} } }9}"}&} } } } }#}%.#}%}%}&..<.}’}“}(}”}=..}#.!}
20:57:02.76 R “}!} }4}”}&} } } } }%}&Y}“..}'}”}(}“rG~
20:57:02.76 T .}#.!}”} } }9}“}&} } } } }#}%.#}%}%}&..<.}'}”}(}"..~
20:57:02.77 T …!..Y…R~
20:57:02.78 R ~.}#.!}+}!} }(..<…
.#…#…l
20:57:02.79 R …=..l9lUMTS_CHAP_SRVR.
20:57:02.79 R .}#.!}*} } },..<.Y}“…}<~
20:57:02.81 T …#…yT|:…u..9Ck.;.v.~
20:57:02.83 R ~.#…~
20:57:02.84 T …!..-…U.~
20:57:02.85 T …W…
20:57:02.85 T …#8”..!.~
20:57:02.88 R
20:57:02.88 R NO CARRIER
20:57:08.72 T ~…!..-…U.~
20:57:08.73 T …W…
20:57:08.73 T …#8"..!.~
20:57:14.72 T ~…!..-…U.~
20:57:14.73 T …W…
20:57:14.73 T …#8"..!.~
20:57:20.72 T ~…!..-…U.~
20:57:20.73 T …W…
20:57:20.73 T …#8"..!.~
20:57:26.72 T ~…!..-…U.~
20:57:26.73 T …W…
20:57:26.73 T …#8"..!.~
20:57:32.72 T ~…!..Y…o.~
20:57:32.73 T …!..-…U.~
20:57:32.74 T …W…
20:57:32.74 T …#8"..!.~
20:57:38.72 T ~…!..-…U.~
20:57:38.73 T …W…
20:57:38.73 T …#8"..!.~
20:57:44.72 T ~…!..-…U.~
20:57:44.73 T …W…
20:57:44.73 T …#8"..!.~
20:57:50.72 T ~…!..-…U.~
20:57:50.73 T …W…
20:57:50.73 T …#8"..!.~
20:57:56.72 T ~…!..-…U.~
20:57:56.73 T …W…
20:57:56.73 T …#8"..!.~
20:58:02.72 T ~…!..Y…e~
20:58:02.73 T .}#.!}%}“} No network protocols running}7}8~
20:58:08.72 T ~.}#.!}%}#} No network protocols running#.~
*** NOTE Second attempt of the PPP since for some reason the first one was not successful
20:58:17.72 T A
20:58:17.73 R A
20:58:17.73 T T
20:58:17.74 R T
20:58:17.75 T D
20:58:17.76 R D
20:58:17.76 T *
20:58:17.77 R *
20:58:17.77 T 9
20:58:17.79 R 9
20:58:17.79 T 9
20:58:17.80 R 9
20:58:17.80 T *
20:58:17.81 R *
20:58:17.81 T *
20:58:17.82 R *
20:58:17.82 T *
20:58:17.83 R *
20:58:17.83 T 1
20:58:17.84 R 1
20:58:17.84 T #
20:58:17.85 R #
20:58:17.85 T
20:58:17.86 R
20:58:17.87 R
20:58:17.87 R CONNECT
20:58:19.72 T ~.}#.!}!}$} }4}”}&} } } } }%}&.P..}‘}“}(}”..~
20:58:19.74 R ~.}#.!}!}"
20:58:19.75 R } }9}"}&} } } } }#}%.#}%}%}&..ia}’}“}(}”.p
.}#.!}“}$} }4}
20:58:19.76 R “}&} } } } }%}&.P..}'}”}(}“b.~
20:58:19.76 T .}#.!}”}”} }9}“}&} } } } }#}%.#}%}%}&..ia}'}”}(}“%|~
20:58:19.77 T …!..P…y~
20:58:19.78 R ~.}#.!}+}#} }(..ia}2}=.#…#…Jq
20:58:19.79 R ..$..,.}]U…UMTS_CHAP_SRVR..
.}#.!}} } },..ia.P…/~
20:58:19.81 T …#…
20:58:19.81 T .15…z..
20:58:19.81 T .
20:58:19.81 T rc~
20:58:19.82 R ~.#..
20:58:19.83 R …~
20:58:19.84 T …!..-…~
20:58:19.85 T …W…
20:58:19.85 T …<…,.r~
20:58:19.87 R
20:58:19.87 R NO CARRIER
20:58:25.72 T ~…!..-…~
20:58:25.73 T …W…
20:58:25.73 T …<…,.r~
20:58:31.72 T ~…!..-…~
20:58:31.73 T …W…
20:58:31.73 T …<…,.r~
20:58:37.72 T ~…!..-…~
20:58:37.73 T …W…
20:58:37.73 T …<…,.r~
20:58:43.72 T ~…!..-…~
20:58:43.73 T …W…
20:58:43.73 T …<…,.r~
20:58:49.72 T ~…!..P..v.~
20:58:49.73 T …!..-…~
20:58:49.74 T …W…
20:58:49.74 T …<…,.r~
20:58:55.72 T ~…!..-…~
20:58:55.73 T …W…
20:58:55.73 T …<…,.r~
20:59:01.72 T ~…!..-…~
20:59:01.73 T …W…
20:59:01.73 T …<…,.r~
20:59:07.72 T ~…!..-…~
20:59:07.73 T …W…
20:59:07.73 T …<…,.r~
20:59:13.72 T ~…!..-…~
20:59:13.73 T …W…
20:59:13.73 T …<…,.r~
20:59:19.72 T ~…!..P…N~
20:59:19.73 T .}#.!}%}%} No network protocols running.S~
20:59:25.72 T ~.}#.!}%}&} No network protocols running.}4~
*** NOTE: This is the third attempt at the PPP as the second one, for some reason, was not successful.
20:59:34.72 T A
20:59:34.73 R A
20:59:34.73 T T
20:59:34.74 R T
20:59:34.74 T D
20:59:34.75 R D
20:59:34.75 T *
20:59:34.76 R *
20:59:34.76 T 9
20:59:34.77 R 9
20:59:34.78 T 9
20:59:34.79 R 9
20:59:34.79 T *
20:59:34.80 R *
20:59:34.81 T *
20:59:34.82 R *
20:59:34.82 T *
20:59:34.83 R *
20:59:34.83 T 1
20:59:34.84 R 1
20:59:34.84 T #
20:59:34.85 R #
20:59:34.85 T
20:59:34.86 R
20:59:34.87 R
20:59:34.87 R CONNE
20:59:34.88 R CT
20:59:36.72 T ~.}#.!}!}‘} }4}"}&} } } } }%}&.}^.}'}"}(}"}/.~ 20:59:36.74 R ~. 20:59:36.75 R }#.!}!}$} }9}"}&} } } } }#}%.#}%}%}&...*}'}"}(}".p~~.}#.!} 20:59:36.76 R "}'} }4}"}&} } } } }%}&.}^.}’}“}(}”..~
20:59:36.76 T .}#.!}“}$} }9}”}&} } } } }#}%.#}%}%}&…
}'}”}(}"&|~
20:59:36.77 T …!..}^...~ 20:59:36.78 R ~.}#.!}+}%} }(...*..~ 20:59:36.79 R ~.#...#..$....Dy......wUMTS_CHAP_SRV 20:59:36.80 R R.!~~.}#.! 20:59:36.81 R }*} } },...*.}^.ob~
20:59:36.81 T …#…i…AG…4V..~
20:59:36.83 R ~.#…~
20:59:36.84 T …!..-…~
20:59:36.85 T …W…
20:59:36.85 T e…]N.5X~
20:59:36.88 R
20:59:36.88 R NO CARRIER
20:59:42.72 T ~…!..-…~
20:59:42.73 T …W…
20:59:42.73 T e…]N.5X~

and so on without ever coming to a successful conclusion

*** NOTE: Initial modem SET phase to be performed if necessary at startup
Repeated commands for ECO
21:43:00.01 T AT&F
21:43:00.02 R AT&F
21:43:00.07 R
21:43:00.07 R OK
21:43:01.07 T ATE1
21:43:01.08 R ATE1
21:43:01.09 R
21:43:01.09 R OK
21:43:02.09 T ATX0
21:43:02.10 R ATX0
21:43:02.11 R
21:43:02.11 R OK
21:43:03.11 T AT+CGDCONT=1,“IP”,“JTFIXEDPUBLIC”
21:43:03.12 R AT+CGD
21:43:03.13 R CONT=1,“IP”,“JTFIXEDPUBLIC”
21:43:03.17 R
21:43:03.17 R OK
21:43:04.17 T AT+IPR=57600
21:43:04.18 R AT+IPR=57600
21:43:04.19 R
21:43:04.19 R OK
21:43:05.19 T AT&W0
21:43:05.23 R AT&W0
21:43:05.23 R OK
21:43:06.23 T AT+csq
21:43:06.25 R AT+csq
21:43:06.25 R +CSQ: 22,0
21:43:06.25 R
21:43:06.25 R OK
*** NOTA qui inizia il PPP
21:44:00.71 T A
21:44:01.17 R A
21:44:01.17 T T
21:44:01.19 R T
21:44:01.19 T D
21:44:01.51 R D
21:44:01.51 T *
21:44:01.81 R *
21:44:01.81 T 9
21:44:02.11 R 9
21:44:02.11 T 9
21:44:02.12 R 9
21:44:02.12 T *
21:44:02.14 R *
21:44:02.14 T *
21:44:02.52 R *
21:44:02.52 T *
21:44:03.06 R *
21:44:03.06 T 1
21:44:03.08 R 1
21:44:03.08 T #
21:44:03.52 R #
21:44:03.52 T
21:44:03.54 R
21:44:03.55 R
21:44:03.55 R CONNECT
21:44:05.46 T ~.}#.!}!}!} }4}“}&} } } } }%}&}”}&.g}‘}“}(}”.d~
21:44:05.49 R ~.}#.!}“}!} }4}”}&} } } } }%}&}“}&.g}
21:44:05.50 R '}”}(}".}-.}#.!}!}!} }8}“}&} } } } }#}$.#}%}&s}4}#} }'}”}
21:44:05.51 R (}“..~
21:44:05.52 T .}#.!}”}!} }8}“}&} } } } }#}$.#}%}&s}4}#} }'}”}(}“.}”~
21:44:05.53 T …!..gL.~…#…)~
21:44:05.55 R ~…!
21:44:05.55 R …dV
…#…Welcome!._~~
21:44:05.56 R …!..
21:44:05.56 R …~
21:44:05.56 T …!..-…U.~
21:44:05.57 T …W…
21:44:05.57 T ..r.z’…~
21:44:05.59 R ~…!..W…
21:44:05.59 R ..r.z’…y~
21:44:05.59 T …!..
21:44:05.59 T …l.~
21:44:06.40 R ~…!..
21:44:06.40 R …-…~
21:44:06.40 T …!..~
21:44:06.43 R ~…!..W…~
21:44:06.44 T …!..W…9.~
21:44:06.46 R ~…!..W…+~
21:44:18.47 R ~!E
21:44:18.48 R .,.1…5.C…W…f..$…..........P..~ 21:44:18.49 T ~!E..(.......sW...C...........f..%P.......5.~ 21:44:21.95 R ~!E .,0......E#...W.....<....E....…oa…
21:44:21.96 R ..P.u~
21:44:21.97 T ~!E..(…LW…#…<…FP…~
21:44:26.93 R ~!E .,C…$.EUF.W…|…M’-…...V].. 21:44:26.94 R ...P..~ 21:44:26.95 T ~!E..(......XsW...EUF....|.....M'.P...k...4.~ 21:44:35.46 T ~...!.......g.P~ 21:44:35.48 R ~...! 21:44:35.48 R ...b....a~ 21:44:46.75 R ~!E .,.1....+.@...W.........&.....P..~ 21:44:46.76 T ~!E..(.......>W...@....…P…~
21:44:46.79 R ~!E .,.1…c.
21:44:46.80 R .Q|W… ..3…....Y.....P.q~ 21:44:46.81 T !E..(........W.....Q|........ ..4P........w~ 21:44:51.85 R ~!E .,.,.....c#..PW.....V^..*.....…P.
21:44:51.86 R .~
21:44:51.87 T ~!E..(…W…#..PV^…*.P…z~
21:45:05.46 T ~…!..g..~
21:45:05.48 R ~…!
21:45:05.48 R …[…p~
21:45:14.91 R ~!E .,…Q…W…2.4|…..........P 21:45:14.92 R <j~ 21:45:14.93 T ~!E..(.......7W...Q....4.2....|...P....5....~ 21:45:35.46 T ~...!.......g"g~ 21:45:35.48 R ~...! 21:45:35.48 R ...Ts..#.~ 21:45:36.59 R ~!E .,.1....D/N...W......w6 21:45:36.60 R ......…PF.~
21:45:36.60 T ~!E..(…}^W…N…w6..P…F…~
21:45:37.05 R ~!E .,…2.d.mk].W…v…..B.... 21:45:37.06 R ...P..~ 21:45:37.07 T !E..(........W...mk]............wP...z.....~ 21:45:49.74 R ~!E .,.1.......V..W......Q...=....…v…P.C~
21:45:49.75 T ~!E..(…j.W…V…Q…>P…6~
21:45:59.13 R ~!E .,…SaQ…W…2.S^..=…`…
21:45:59.14 R ..P..~
21:45:59.15 T ~!E..(.
21:45:59.15 T …3W…Q…S.2…^..>P…V|~
*** Note: Recording stopped because the logger reported that it had acquired the IP address and the PPP was successful.
I noticed a clear welcome message that never arrives in the TRB142.

This would be my preferred solution, so that at set intervals the logger could send the data to an FTP server, where the client could retrieve it more easily than with plan B.

I could also send emails to notify users of situations and alarms more quickly.

In my imagination, compared to the preferred solution, once the PPP issues are resolved, I’d still like to reach the logger via IP address when I need to change schedules or programs, etc.

If the PPP connection doesn’t allow me to reach the logger, would it be possible to switch from normal to full control and vice versa using AT commands?

Thank you very much. I remain available for further details if needed.

Best regards

AT