Your comments
I guess such a person would be most welcome.
Wonderful.
Thanks
la7um Finn
Can now hook for limit to P2.
This solves both Norwegian problem of 1000HZ BW by Law on 30m towards EU.
This also solves all world using old non P3 enabled PTCIIs linking to Servers allowing P1,2,3.
No more forcing into P3 which stop the TNC from any TX at all.
73 la7um Finn
It is kind of the other way around if a PTCII with no more trial P3s is linked to a RMS allowed by sysop running P1,P2, P3, or P2,P3.
RMS Express 1.1.1.3 still do force the PTCII into MYLevel P3 mode, and then TNC stops TX.
Not a problem with Airmail. Session level is automatically detected, allowed and automatic limited to P2 and thus working.
This is part of Pactor protocol, so possible. A possibility of choosing MYLevel 2 would solve the problem. No help in doing this with HYPERTERM first. It is overrun during initialization.
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
Found recently that a PTC2 with no more P3 trials, do lock up when using RMS Express on a pactor frequency allowed by sysop for P1,P2,P3, or P2,P3. New discovery for me.
RMS Express is forcing the PTC2 into P3, but no more P3 trials, so the TNC Locks up stopping all TX.
This will be a world wide problem on all bands for people getting cheap non P3 capable PTCIIs on Ebay or elsewhere.
Solution is switching to AirMail, where BW level can be set manually to P2, and were also AirMail by initialization finds out that the box can only do max P2. This is negotiated to the RMS Pactor. Working well now.
This ability has always been inherent in the Pactor protocol, so should be easy to implement for pactor.
Would also help for the norwegian law issue on 30m at least on Pactor mode.
I understand that it is more difficult running WINMOR since not built into the protocoll.
Customer support service by UserEcho
