Hello All,
We are working on developing an application that will use the serial pass-through function available in the terminal emulator when connected to the CR1000. When we use the Terminal Emulator application available in Loggernet all is well. However, if we use telnet to connect to the CR1000 there are non-printing characters that show up approximately every 15 seconds. We would like to eliminate them as they will make decoding the dialogue with the remote serial instrument somewhat more cumbersome. Where can I find some more info on the telnet settings? Note, we are using a RavenXT modem with a Verizon service plan (configured for PPP as shown in the manual).
Thanks,
Chris
If you connect to the datalogger's PakBus/TCP service port (by default this is TCP port 6785), the datalogger's terminal services are also available. However, the datalogger will also send PakBus hello requests on that connection. It would appear that this is what you have done. The datalogger's terminal services are also available on the telnet service (by default TCP port 23). This service will not mix in PakBus as the other service will.
OK, thanks. The connection works with HyperTerm, but not with a *nix telnet client. I get the "CRx000> T = Terminal, Q = Quit, D = Debug, nnnD = change Debug: 0" response after hitting enter a couple of times, but cannot start a terminal connection unless I am in HyperTerm. Ultimately, I will need to run this connection from a linux cron job. I've been playing around with the mode and toggling crlf but have had no luck. Any suggestions?
Also, there seems to be a very short time window after the prompt (CR1000>) comes up wherein I can enter a command. If that time expires, I have to hit enter a couple more times to get back to the prompt. Is there a way to increase that time window?
Chris
When presented with
"CRx000> T = Terminal, Q = Quit, D = Debug, nnnD = change Debug: 0"
are you entering "T" and pressing ENTER?
Yes, I am entering "T" and pressing "ENTER". Turns out I needed to set up my .telnetrc file with the following configuration settings to make the system work using a *nix base telnet client.
# Settings for RavenXT --> CR1000 Telnet
***.***.*.**
mode character
set crlf
The IP address was changed to protect the innocent :>
The problem lies in how the local versus remote echo of typed characters is handled in the CR1000 telnet server and how the negotiation of same occurs between the client and the server.
Now, how about the time-out? Why do I seem to lose the connection after a few seconds of inactivity? Note, pressing "ENTER" again restores the connection. So maybe it is not a lose of connection so much as a lose of "awareness" that must be reestablished by pressing "ENTER"?
Chris