[Elecraft] K3 Firmware program and Virtual serial port

[Joe Subich, W4TV]

> For example, I have a MicroHam interface box and it cannot be
> reliably used when performing a K3 firmware load because it attempts
> to interpret the data stream -- its serial port to the radio does not
> simply emulate a wire.

microHAM Router can be set to not interpret the data if necessary. 
However, that does no good since the K3 cycles power on the Aux DC
output which causes the microHAM devices to reset and closes the port.

73,

    ... Joe, W4TV


On 2/7/2013 9:32 AM, Lyle Johnson wrote:
> Brian,
>
> Depends entirely on the software between the virtual serial port
> presented to Utility and the physical port connected to the radio.
>
> For example, I have a MicroHam interface box and it cannot be reliably
> used when performing a K3 firmware load because it attempts to interpret
> the data stream -- its serial port to the radio does not simply emulate
> a wire.
>
> I also have a RigExpert interface box and it works perfectly with
> Utility -- it does not attempt to interpret the data stream.
>
> LP Bridge is creating a "virtual K3" and passes data from its "virtual
> K3" to other applications to allow sharing of the state of the radio
> (frequency, for example) and as a result is interpreting elements of the
> data streams.  The firmware load data is thus incompatible with the
> intent of LP Bridge.
>
> 73,
>
> Lyle KK7P
>
>> ...Maybe this has come up before.  It is now obvious that the K3
>> firmware program will not work on a virtual serial port (LPBRIDGE).
>> Tried.
>>
>> For curiosity, why is that?
>
> ______________________________________________________________
> Elecraft mailing list
> Home: http://mailman.qth.net/mailman/listinfo/elecraft
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Elecraft at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>