Signature ADCP TCP Connection
The signature manual specifies a telnet client should not be used to listen to the TCP Ports on the instrument. What software and configuration do you recommend using to utilize this capability?
-
Official comment
Hi Patrick,
Telnet is perfectly fine when you are connecting on port 9000, as this is dedicated for ASCII only communication. The Signature Manual specifies that Telnet should not be used over other ports (9001, 9002 and 9004), as they include binary output of measurements and complete sets of data. The reason for this is that Telnet uses its own binary protocol, which is neither interpreted nor sent via the raw connections. Using a Telnet client on these ports will result in extraneous character being sent and certain binary character being interpreted by the client.
The Raw Connection ports (9001/2/4) can be connected using TCP-IP, which is more thoroughly described in chapter 3.3.2 of the Signature Integration Manual.
We usually reccomend PuTTY, as you are then able to choose "raw" or "telnet" connection. In addition, you are also able to echo characters and locally edit lines.
Comment actions -
Hi Aasta,
This is exactly the info I was looking for. Thank you
A follow up question: I configured the signature to output data in the DF150 which should correspond to theRDI PD0 format. In the RDI documentation (http://www.teledynemarine.com/Documents/Brand%20Support/RD%20INSTRUMENTS/Technical%20Resources/Technical%20Notes/WorkHorse%20-%20ADCP%20Special%20Applications%20and%20Modes/FST012.pdf) the Heasder ID is indicated by a 7F 7F hex leader corresponding with PD0.
I am seeing a 7d 7d leader in the data stream which corresponds with RDI PD5 data format which does not contain velocity data.
Are there any Signature deployment configurations that do not allow velocity data to be streamed?
-
Hi Patrick,
Great to hear that you got what you needed. When it comes to you follow up questions, the general answer is that the configuration of your deployment should not affect the data format, as this is set by its own argument under the SETTMAV command (see our Integrators Guide for details).
This forum is mainly meant for discussion and exchanging experiences with fellow Nortek instrument users. If you want the support department to have a closer look at this specific case and data, please send us a request on support@nortekgroup.com, including the serial number of your instrument, the deployment configuration (for example as a .deploy-file) and an example of the output data you get.
Please sign in to leave a comment.
Comments
4 comments