| |
UZ7HO > PACKET 16.06.20 21:10l 33 Lines 1190 Bytes #999 (0) @ WW
BID : 490086UZ7HO
Read: GUEST
Subj: Re:FX.25
Path: IW8PGT<IZ3LSV<DB0ERF<OK0NAG<F3KT<F3KT<UT1HZM<RC8SB<UZ7HO
Sent: 200616/1728Z @:UZ7HO.LUB.POL.UKR.EU #:64695 [Lubny] FBB7.00e $:490086UZ7H
From: UZ7HO@UZ7HO.LUB.POL.UKR.EU
To : PACKET@WW
Hi All
>>>From: kf7psm@ke0gb.#seco.co.usa.noam
>>X-JNOS-User-Port: Telnet (ea2rcf @ 94.177.237.192) -> Sending message
>>
>>Is anyone using FX.25? Would it be possible to upgrade a current tnc's
>>firmware to support this fec protocol or is it only possible using
>>a pc? It would be interesting to have some firmware for a tnc that
>>used standard ax.25 but then upon detection of so many retry's it
>>changed over to fx.25. Anyway just pondering what's possible I feel
>>this protocol may be useful on long backhaul links, if any still
>>exist today!
>>73 de KF7PSM
>
> It is implented in direwolf.
> there are some test going on on a couple of CB nodes over here.
> Dont know the exact status of it and dont know if there is any other
> software around supporting it..
> I do know that Xrouter32 has support for Eax25 think its not the same..
Yes, we are using FX.25 on HF, it gives +2db over original AX.25 using 25%
FEC code. FX.25 based on Reed-Solomon FEC code, I am not sure if Z80 TNC2
CPU should be enough for such operations.
The lastest UZ7HO Soundmodem with FX.25 support here: http://uz7.ho.ua/fx25
b.zip
73 de Andy
Read previous mail | Read next mail
| |
