Paul,

Bang on target and a great thought.

I dusted out the telnet RFC (I haven't looked at it in a decade or more) 
and the receiver should be able to filter on anything that is FF FA ... 
F0. Brings back old memories.

jerry

Ziggy wrote:
> The FF fx hex sequences look like telnet IAC sequences to me. In most  
> device servers these can be disabled. It's often called raw mode,  
> transparent mode, or something similar. I'll take a look at the Xport  
> doc later tonight. Maybe the whole extra character problem can be  
> avoided by setting the right config option on the Xport. You don't  
> really want a telnet connection, just a TCP 'pipe'.
> 
> Paul
> 
> On Jul 3, 2009, at 9:30 AM, Paul Alfille <[email protected]> wrote:
> 
>> Question:
>>
>> Are existing users of the Linkhub-E having trouble with acces using
>> owfs? I know it's worked in the past.
>>
>> Background:
>>
>> The linkhub-E is a 1-wire bus master made by ibuttonlink that uses
>> there (serial) bus master with a Lantronix Xport to give it ethernet
>> access. It has a telnet interface which we connect to. Although the
>> basic ascii command set it the same as the (serial) LINK, it takes a
>> bit of adjusting for some of the added control or escape characters
>> added to the stream.
>>
>> Problem:
>>
>> Ioannis Kampolis has found that his Linkhub-E doesn't work with owfs
>> because the communication gets confused with the extra characters. His
>> machine is LinkHub-E V1.1
>>
>> At variable places in the response stream, the extra 7 byte sequence
>> FF FA 2C 6A 60 FF F0 gets added.
>>
>> In the past there was a slightly different 6 byte sequence added.
>>
>> It's going to be hard to specially code to different linkhub-e
>> adapters without knowing the differentiator, nor having access to
>> different versions.
>>
>> Does anyone have some insight?
>>
>> Paul Alfille
>>
>> --- 
>> --- 
>> --- 
>> ---------------------------------------------------------------------
>> _______________________________________________
>> Owfs-developers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>>
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Owfs-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/owfs-developers

------------------------------------------------------------------------------
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to