Magic RDS 4 > Configuration Options and Possibilities

MAGIC4 Bridge virtual port TCPIP telnet syntax

<< < (2/2)

Jan:
Thanks for detailed info. The <LF> currently does not act as a separator but it is completely removed from the ASCII text, because the VP now represents a RDS encoder's communication port even if it is used for general purpose. User-selectable separator is already on 'TODO' list.

davidmb:
Hi Jan,

ok, thanks for the feedback.
 
Great info! :)
Any timline already in place when can we expect user-selectable separator to be implemented?

Br, David

davidmb:
Hi Jan,

I did a bit more investigation and it seems that when my client connects to the Magic4 telnet server the first mode server is into is UECP?
If for instance i connect to server with putty - this is what I get back from it in my terminal window:
ÿśÿÿśÿ

Also in RX monitor I see this:
UECP: <FE><FF>
UECP: <FE><FF>

If I press enter in putty terminal window I see this in RX monitor:
ASCII: ÿśÿÿśÿ

And only after I initialy send first CR, then I can start sending my ASCII commands.

Is there some special type of connecting procedure to telnet server (putty settings?) or string in the beggining of command to let the server know we want ASCII?
I have a feeling that this is the problem I'm having when trying to script my telnet client...

Thanks for your help in advance and br, David

Jan:
The VP supports terminal echo, this is the reason why you get the string back. The echo can be disabled by ECHO=0, but your case requires a more complex solution: the VP now behaves like a real port of the RDS encoder, incl. some specific characteristics which may not be useful for general purpose usage. We're working on adding options for the VP control.

davidmb:
Ah ok, now it makes sense.

Will wait then for the additional VP options to be added. :)

Thanks for the feedback
Br, David

Navigation

[0] Message Index

[*] Previous page

Reply