CR200x used with a Telit 910-DUAL based cellular modem. Am not able to successfully issue the +++ escape sequence at the end of my hourly communications session so that I can do an orderly modem shut down before I cut modem power. I know this because my shutdown AT commands show up in the LoggerNet Iow level I/O logs. I suspect that low level LoggerNet chatter is interrupting the required 1-second guard band before and after +++. A cursory inspection of time stamps in the I/O logs seems to confirm. Any thoughts on a solution or a workaround?
Looks at the other logs in Loggernet to see what it was talking to the datalogger about. If data collection hadn't finished yet, Loggernet and the datalogger will be talking back and forth to tranfer the remaining records. Without the Connect screen actively connected, other communication goes quite pretty quickly. You can increase to beacon interval on the Pakbus port to reduce some of the back and forth.
The other models of dataloggers can check to see if communication is still active. However, the CR200X does not have a way. You probably will just need to issue the hang up command several times.
@JDavis, Beacon Interval dropdown menu on PakBusTcpServer shows "00h 00m 00s" which I assume means default. How high do I dare crank it up? All of my communications are direct between loggernet and CR200x via cellular, instigated by the logger once per hour. Since I don't need to discover neighbors is the beacon needed at all?
You should be fine leaving the Beacon at 0, but set the Verify Interval up.
@JDavis, PakBus Verify Interval was set at 18h. Probably not going to help me to make it higher?
I believe that is the maximum verify interval.
The communication and transaction logs from Loggernet would show what is going on. With your settings, it shouldn't be beacons and you aren't hitting the verify interval.
Looks like I may still be transfering records in this example?
21:09:41.591 T 28 41 00 00 00 01 00 00 E3 7B BD (A.......{.
21:09:44.134 R BD AF FE 03 FA 1F FE 03 FA 89 95 00 00 02 00 00 ................
21:09:44.134 R 04 08 00 01 31 CC 0A 70 41 3C B2 21 3F 71 ED A7 ....1..pA<.!?q..
21:09:44.134 R BC DD 61 27 66 00 F6 38 BD 2B 2B 2B 0D 0A ..a'f..8.+++..
21:09:44.134 T BD A3 FA 5F FE 13 FA 0F FE 09 99 00 00 05 00 01 ..._............
21:09:44.134 T B0 75 00 00 00 01 00 13 00 15 00 00 0B 23 BD .u...........#.
21:09:44.961 R BD AF FE 03 FA 1F FE 03 FA 89 99 00 00 01 00 00 ................
21:09:44.961 R 00 1B 00 01 31 CC 0C B9 14 02 00 00 00 BF D9 BD ....1...........
21:09:44.961 T BD A3 F2 7F FE 03 F2 0F FE 09 9D 01 05 FD 20 C3 .............. .
21:09:44.961 T CE BD ..
21:09:45.928 R 2B 2B 2B 0D 0A BD AF FE 03 F2 0F FE 03 F2 89 9D +++.............
21:09:45.928 R 00 01 FD 20 72 D7 BD ... r..
21:09:46.037 T BD B3 FA 3F FE 03 FA 0F FE C2 40 BD BD A3 F2 6F ...?......@....o
21:09:46.053 T FE 13 F2 0F FE 09 96 00 00 05 00 04 6B 28 00 00 ............k(..
21:09:46.053 T 00 01 00 00 96 85 BD .......
21:09:47.113 R 41 54 2B 57 49 50 43 4C 4F 53 45 3D 32 2C 31 20 AT+WIPCLOSE=2,1
21:09:47.113 R 0D 0D 0A BD 8F FE 03 FA 0F FE 03 FA 8F FF BD 41 ...............A
21:09:47.254 R 54 2B 57 49 50 43 4C 4F 53 45 3D 32 2C 31 20 0D T+WIPCLOSE=2,1 .
21:09:47.254 R 0D 0A BD AF FE 03 F2 1F FE 03 F2 89 96 00 00 04 ................
21:09:47.254 R 00 00 00 00 00 00 00 3D 35 BD .......=5.
21:09:47.254 T BD A3 F2 6F FE 13 F2 0F FE 09 97 00 00 05 00 03 ...o............
21:09:47.254 T CD 16 00 00 00 01 00 00 17 23 BD .........#.
21:09:48.081 R BD AF FE 03 F2 1F FE 03 F2 89 97 00 00 03 00 00 ................
21:09:48.081 R 00 40 00 01 31 CB 37 80 41 3B 27 9E 3F 86 2E DB .@..1.7.A;'.?...
21:09:48.081 R 3F 86 2E DB 00 7E 11 BD ?....~..
21:09:48.081 T BD A3 F2 6F FE 13 F2 0F FE 09 98 00 00 05 00 02 ...o............
21:09:48.081 T 28 41 00 00 00 01 00 00 31 B8 BD (A......1..
21:09:48.892 R BD AF FE 03 F2 1F FE 03 F2 89 98 00 00 02 00 00 ................
21:09:48.892 R 06 19 00 01 31 CC 0A 70 41 3A DD A4 3F 82 FB 03 ....1..pA:..?...
21:09:48.892 R 3F 82 FB 03 00 A1 5A BD ?.....Z.
21:09:48.892 T BD A3 F2 5F FE 13 F2 0F FE 09 9A 00 00 05 00 01 ..._............
21:09:48.892 T B0 75 00 00 00 01 00 13 00 15 00 00 89 FA BD .u.............
21:09:51.747 R 41 54 2B 57 49 50 42 52 3D 35 2C 36 20 0D 0D 0A AT+WIPBR=5,6 ...
21:09:51.747 R BD AF FE 03 F2 1F FE 03 F2 89 9A 00 00 01 00 00 ................
21:09:51.747 R 00 2A 00 01 31 CC 0C BC DD 2E 02 00 00 00 91 8A .*..1...........
21:09:51.747 R BD .
21:09:51.871 T BD B3 F2 3F FE 03 F2 0F FE 74 82 BD ...?.....t..
21:09:52.807 R BD 8F FE 03 F2 0F FE 03 F2 CF EF BD ............
21:10:13.150 R 41 54 2B 57 49 50 42 52 3D 35 2C 36 20 0D 0D 0A AT+WIPBR=5,6 ...
21:10:13.150 R 41 54 2B 43 46 55 4E 3D 30 20 0D 0D 0A 41 54 2B AT+CFUN=0 ...AT+
21:10:13.150 R 43 46 55 4E 3D 30 20 0D 0D 0A CFUN=0 ...
Look at the Transaction log. It will tell you the intent of the packets. It tells you when data collection started and when it finished.
Awk, just noticed that the +++ is followed by 0D and 0A (CR and LF).
2B 2B 2B 0D 0A
Changing print command to:
Print (-2 ,9600, "+++")
I seemed to have solved the problem by changing the print command from:
Print (2 ,9600, "+++")
to:
Print (-2 ,9600, "+++")