Some possible reasons might be:- JT65 is very heavy on number crunching, the low power MCU in the KX2 is likely not optimised for this- UI: JT65 programs generally use a waterfall, and have enough screen real estate to display info about all stations decoded, this is not practical on a KX2 display- time synchronisation -- JT65 requires an accurate realtime clock, usually synchronised to Internet NTP servers. The KX2 has no direct interface to the Internet- frequency stability -- JT65 has some stringent frequency stability requirements, it is possible that the KX2 may have difficulty providing this, especially if it is heating up with long held transmission times of a high duty cycle mode like JT65. 73, Matt VK2RQ
On Tue, May 24, 2016 at 5:58 AM -0700, "Dan - VA3MA" <[email protected]> wrote: Could Elecraft explain why the KX2 design doesn't allow operating say JT65 out of the box? What prohibits manufacturing the rig to do the narrow digital modes? Would be helpful to know Thanks Dan VA3MA ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [email protected] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [email protected]
