… I did so. jt9code “1 2 3 4 5“ and “i have acat“ etc. worked fine, but “i have a cat“ with three spaces resulted in a mysterious “Internal Error: EOF condition not handled-- END= tag needed“. Never mind, easy to work around. 73, Markus If your message has spaces in it, you need to place quotation marks around the message. On 1 February 2016 at 21:35, <[email protected]> wrote: Thanks a lot Andy, that’s exactly what I was looking for. It’s not obvious on the website but the download URL is http://physics.princeton.edu/pulsar/K1JT/jt9code.exe Interestingly, „i have a cat“ throws an error but „i_have_a_cat“ did what I wanted. Rik, Vinny, my term „linear transmitter“ was probably inaccurate wording, I just meant an SSB mixer from audio to RF. Best 73, Markus There is a separate utility called JT9CODE, downloadable from the WSJT website There is a similar one for JT65 They are a bit convoluted to use, so I wrote wrappers for them to intercept the output to screen and send to formatted files for including within PIC .assembler files On 1 February 2016 at 20:22, <[email protected]> wrote: While we’re at it… I recently missed the JT9 activity night, mostly due to the lack of a linear MF transmitter. For WSPR, I’ve used a commandline tool (wsprcode.exe, or wspr.exe with -tx option) to encode a message to a file. This is then read by a little homemade program (ddswspr.exe), which feeds an AD9850 DDS module through the serial port. Does anyone know whether a similar encoding option exists for JT9? Best 73, Markus (DF6NM) … "If you have a BPSK-capable beacon which uses an EEPROM to store its message, WOLF can generate a binary file suitable for programming the device. …
|
|
