+2

RMS Express locks up a PTCII if not P3 enabled

LA7UM 13 year бұрын жаңартылды 13 year бұрын 4

If a PTCII is not P3 enabled, but is linked to a RMS station beeing either P1,P2,P3 or P2,P3 enabled, the PTCII is quicly forced up into P3, whitch it does not have.

The TNC locks up and stop transmitting.


Important beeing aware that SYSOP has allowed for lower levels than P3.


Workaround in Pactor is Using AirMail.

No such problem using Airmail which by initialization finds out the highest possible level, and obviously do negotiate this into the RMS Packtor server.


This is probably an easy fix, since this for long has been implemented in the very Pactor protocol.


This is a world wide problem on all bands, and probably increasing as cheap old PTC2s without P3 lisense might flourish on Ebay since the introdution of P4.



AirMail also lets the client using a P3 enabled TNC, but manually limiting the session to P2, thus making legal use of EU RMS Pactors allowed by SYSOP P1,2,3, by a norwegian client on 30m limited by LAW to P2.


I realize that this does not have same simple fix in the WINMOR protocol, but a fix for Pactor modes should be simple.

73. LA7UM FINN

Resolved in the upcoming release of RMS Express

Confirmed.
Wonderful.
Thanks
la7um Finn
Even better in the new 1.1.4.0
Thanks.
la7um Finn