+14
Voltooid

Support of the new SCS Pactor Modem

oe9fwv 13 jaar geleden bijgewerkt door Winlink Moderator 13 jaar geleden 7
SCS DR-7800 Ptc-4 Support in RMS Pactor and RMS Express

Antwoord

Antwoord
Voltooid
RMS Pactor now supports P4. It may only be used outside the USA due to symbol rate constraints in Part 97 of the FCC rules. P4 has the same bandwidth as P3.

Agree.  A driver to support the new SCS Dragon is needed now.  This modem is getting wide distribution quickly and RMS Express and Paclink don't support it.

With the addition of XE2BC RMS in Baja, capable of P4, the systems are growing. While the "symbol" rate issue is not yet resolved in the US, it will be in time. Aside from that I have been contacted by a local sailing/amateur group to give a presentation. While many still use Airmail, some want to transition to RMS Express. They desire to use P4 outside of the US while sailing and XE2BC is reachable for them. Also hope to see a driver for RMS Relay soon.

I would also like to see the correct mode listed in the RMS HF frequency list. 

in the moment the frequency lists omit P3 and P4 mode in the list. 

Without correcting the list Airmail will connect in P2 mode to the RMS. 

I second this. But Poor Programmers...When do they watch televison or talk to xyls??
Antwoord
Voltooid
RMS Pactor now supports P4. It may only be used outside the USA due to symbol rate constraints in Part 97 of the FCC rules. P4 has the same bandwidth as P3.

RMS Express has a problem with higher Speedlevel than SL5. 

It has to do with flow controll to the modem and results in Idle packets and unnecessary changes in long and short packets which slows down the traffic to the RMS. 


RMS Express at the time being has a problem with P4. So I am informed elsewhere, AirMail as a client is quicker, but is it unsolvable?...Really??...How can admin say "Completed"???

@Finn: the problem first was evident in RMS Pactor, where it is solved now. I think the programmers will be able to correct this in RMS Express. I expect it to be repaired with the next update of the program. The Winlink moderator probably was not aware of the bug when he set the issue into "completed".