TX136/500 v1.07 OPERA and JASON modes added

[F4GCB]

Hello the TX136/500 builders,

This new unofficial version 1.07 gives the following changes :
- OPERA mode added : OP2 to OP65 (see https://rosmodem.wordpress.com/)
- JASON mode added : normal and fast speed with turbo mode (see http://www.weaksignals.com/)
- beacon configuration menu added to program the parameters for all modes.
- display menu improved with more informations
- UART2 available for optional GPS NMEA used with the WSPR mode
- WSPR locator can be defined by optional GPS NMEA
- program structure modified to improve readability and maintenance.

the PC can be used to program the parameters for all modes but the TX136/500 is now a 100% stand-alone device.
Having no TX500 this software has been validated on TX136.
For the ones who will try it, thanks in advance for your feedback.

73, Patrick F4GCB

[F4GCB]

For our Japanese friends, here is the version 1.07j which limits the RF power
according to the portable regulation in Japan.

73, Patrick F4GCB

[7L1RLL]

Patrick Thank you for the code for JUMA users in Japan.
I wll test the V1.07j later. 73
7L1RLL Rick

[7L1RLL]

Hi Patrick,
I have tried to run V1.07j on TX500 today.
The mode CW,QRSS,DFCW and WSPR work well including message modification.
But Opera can not decoded even if the receiving signal appears at a middle of the waterfall, say inside of red lines.
My receiving software is Opera V1.5.7 by EA5HVK. The frequency is 478500Hz at display. The mode is in MODE 2 of OPERA
Am I mistaken ?

PS: I made a mistake that Mode 8 shall be used in 475kHz band. Now it's resolved.

7L1RLL Rick

[7L1RLL]

Hi Patrick,
I feel a small difficulty to add a space in QRSS/DFCW/JASON message using beacon configulation mode.
I think a default letter for new position should be a space code(20h) instead of a number zero character(30h).

By the way, I can change the beacon message including a space through ETA-232-E interface at my home.
73
7L1RLL Rick

[7L1RLL]

Hi Patrick,
I find that switches of my TX-500 generates multiple noize, say chattering, so sometimes skips a character atter push freq+- button.
Now I am managing my TX500 with V1.07J.
Thank you.
7L1RLL Rick

[7L1RLL]

Hi Patrick and the others,
To fublicate of a small OPERA keyer for 136kHz/476kHz band, a small coding test program was written by my self as described in URL. The program itself is a percial copy of Patrick's control program including your copyright and acknowledgement to EA5HCK(Jose), PE1NNZ(Guido) and F4GCB(Patrick).

My WEB site is written in Japanese, but some caption and the program are written in English or Visual C++.
http://www1.u-netsurf.ne.jp/~7l1rll/OPE ... g_Test.xml

73,
Rick 7L1RLL

[7L1RLL]

I wrote a short testing program on Opera decoding: manchester decoding and de-interleaving program.
As far as my test, the start bit shall be one bit as Patrick's program and Jose's opera_generator.
73,
7L1RLL Rick

[7L1RLL]

I wrote a decode test program for Opera, but not implement of FEC at this time.
This may help for better understanding of OPERA.
URL = http://www1.u-netsurf.ne.jp/~7l1rll/OPE ... e_Test.xml

73
Rick 7L1RLL

[LA6LU]

Hello,

Since I am new to this, I have to just assume things. I am aware that there a good chance that things can be done (or not), that's not so obvious, so here are my questions and a few assumptions.

I am soon going to flash my Juma TX500 with the latest firmware from Patric.
However, before I do that, I want to preserve the original Juma firmware in case I want to revert back.

• How can I read the old firmware down to pc disk, so I can re-flash it later if I want? Or does it exist somewhere on Juma's web pages?
• Is there a way (a command) to change from CW beacon mode to WSPR (or any supported mode) and back?
  This can be useful if one wants to send a quick CW ident after each WSPR transmission. It can also be VERY useful if one wants to run different modes automated.
  For example, the mode commands could be expanded to include all supported modes like, \g0 (CW), \g1 (QRSS) , \g2 (DFCW), \g3 (JASON), \g4 (OPERA) and \g5 (WSPR)
  if the mode change is to a time critical mode like WSPR, the TX just waits until the start of the next 2 min WSPR period.

I also have a comment regarding the beacon mode. Of all the special characters supported in beacon mode (and which the majority are not used at all), I find it peculiar that there are not a command to send a beacon carrier. like \css or \c05 where c = the (suggested) carrier command and 05 = 5 seconds.

Or wait...maybe there is (but not so elegant). Will it work if the beacon string consists of these commands?

• \g0 (CW mode)
  \s012 (12 WPM)
  XY1XYZ (send Callsign)
  <space> (send a space)
  \g1 (QRSS mode)
  \d005 (set QRSS dot 5 sec)
  E (send a 5 sec QRSS dot (carrier)
  \g0 (CW mode)
  <space> (send a space (needed before looping back))
  
  (Repeat)

Thanks.

Regards
Geir, LA6LU