Re: [Ser2net-devel] Config and Windows Client Questions
Brought to you by:
cminyard
From: Michael H. <mic...@i2...> - 2015-12-02 14:09:15
|
Hi Woody, sorry for late response. See comments inline below: Am 30.11.2015 um 09:56 schrieb Woody Wu: > > > On Monday, November 30, 2015, Michael Heimpold <mic...@i2... <mailto:mic...@i2...>> wrote: > > Hi, > > Am 29.11.2015 um 17:36 schrieb Woody Wu: > > Hello list, > > I want to link together a Windows serial reader program with a remote serial device which attached to a true serial port on a Linux box. On the Linux box, I want to run ser2net and let it listen to a tcp port, and this port should be connected from the Windows client side by some kind of virtual serial port (VSP) driver which on the other hand should emulate a virtual serial port, to which the Windows serial reader program could eventually talk. > > For this envisioned setup, I have several questions not so clear at the moment: > - On the Linux side withe ser2net, should I config the serial port with telnet mode or raw mode? > > > That depends: if your windows client programm needs to change the baudrate etc. of the remote serial port, > then you must use telnet with RFC2217. Otherwise you can choose. > > > Thank you very much. Let me describe what I now understood and please have a look to see if this is correct: > > When ser2net listening port is raw, what the client program write to its serial port are directly transfer to ser2net and nothing modified or interspersed. Correct. > If the client program will be setting its serial port parameters, that operations will be silently discarded. No. There is no chance for the client program to actually tell ser2net howto change settings: since only one socket is used, all data comming through this socket will forwarded to the uart as raw mode does not add anything which could "mark" such settings information. So, when the client would transfer such setting information, it will be forwarded as data to the uart. > When ser2net port is in telnet mode and remctrl option is also enabled, some serial port setting command will be interspersed into the normal data traffics and ser2net can understand and handling these special commands according to RFC2217. Correct. > But I still cannot image what will happen if the port mode is telnet but the rmtctrl option is disabled, in these mode what kind of telnet negotiation command could possibly be used? Original Telnet for example is 7 bit only. So the telnet negotiation first goes to 8-bit mode and such stuff. Use Wireshark or similar if you are interested in the negotiation. > > Another interesting thinking is, in the telnet+rmtctrl mode, if the client prgrom initially open the serial port with a low baudrate and after a handshaking sequence with its peer device, it then switch to a both aggreed higher buadrate, is this baudrate switch pattern also supported by ser2net. Yes, this should work. However, it the responsibility of the client programm to tell ser2net that the baudrate changed (the VSP in this case). And in such a scenario, you should examine, whether or when the remote device falls back to its initial baudrate. This often depends on some timeouts. Its also very important how the device reacts when you (i.e. ser2net) speaks to it with a wrong baudrate. Regards, mhei > > Best Regards, > -woody > > > - What Windows VSP products are compatible with ser2net? Will Moxa NPort driver and HW VSP do the job? > > HW VSP is working fine, however, I have to enable "Purge buffer when port is opened" flag as it will > forward some rfc2217 data to the client application otherwise. > > - If I enable the FRC2217 on the ser2net, what impacts will be on the Windows VSP side? > > > Your client must be telnet compatible, i.e. needs to correctly quote the data. Telnet and raw mode are > very similar, however, not the same. > > Cheers, > mhei > > I will highly appreciate if you can give some guides. Thanks in advance. > > -woody > Sent from my iPad > ------------------------------------------------------------------------------ > _______________________________________________ > Ser2net-devel mailing list > Ser...@li... > https://lists.sourceforge.net/lists/listinfo/ser2net-devel > > > Mit freundlichen Grüßen / Kind regards > Michael Heimpold > -- > Software Engineer > > I2SE GmbH Tel: +49 (0) 341 355667-00 > Friedrich-Ebert-Str. 61 Fax: +49 (0) 341 355667-02 > 04109 Leipzig > Germany > Web: http://www.i2se.com/ Mail: in...@i2... > VAT No.: DE 811528334 > Amtsgericht Leipzig HRB 23784 > Geschäftsführer/CEO: Carsten Ziermann > > *** Diese E-Mail ist allein für den bezeichneten Adressaten bestimmt. Sie kann rechtlich vertrauliche Informationen enthalten. Wenn Sie diese E-Mail irrtümlich erhalten haben, informieren Sie bitte unverzüglich den Absender per E-Mail und löschen Sie diese E-Mail von Ihrem Computer, ohne Kopien anzufertigen. > Vielen Dank. *** > > *** This email is for the exclusive use of the addressee. It may contain legally privileged information. If you have received this message in error, please notify the sender by email immediately and delete the message from your computer without making any copies. > Thank you. *** > > > > -- > Life is the only flaw in an otherwise perfect nonexistence > -- Schopenhauer > > woody > public key at http://subkeys.pgp.net:11371 (nar...@gm... <mailto:nar...@gm...>) > > Mit freundlichen Grüßen / Kind regards Michael Heimpold -- Software Engineer I2SE GmbH Tel: +49 (0) 341 355667-00 Friedrich-Ebert-Str. 61 Fax: +49 (0) 341 355667-02 04109 Leipzig Germany Web: http://www.i2se.com/ Mail: in...@i2... VAT No.: DE 811528334 Amtsgericht Leipzig HRB 23784 Geschäftsführer/CEO: Carsten Ziermann *** Diese E-Mail ist allein für den bezeichneten Adressaten bestimmt. Sie kann rechtlich vertrauliche Informationen enthalten. Wenn Sie diese E-Mail irrtümlich erhalten haben, informieren Sie bitte unverzüglich den Absender per E-Mail und löschen Sie diese E-Mail von Ihrem Computer, ohne Kopien anzufertigen. Vielen Dank. *** *** This email is for the exclusive use of the addressee. It may contain legally privileged information. If you have received this message in error, please notify the sender by email immediately and delete the message from your computer without making any copies. Thank you. *** |