TX136/500 v1.13 WSJT-X compatibility + a little effort

[F4GCB]

Hello the TX136/500 builders,

This new unofficial version 1.13 gives the following changes :
- WSJT-X, or other softs generating FSK tones, is now usable to make QSO.
This is possible with an interface derived from the QRPGuys AFP-FSK Digital Transceiver kit and its software based on the excellent work of Kazu Terasaki AG6NS.
This new feature must be earned because the interface must be build by the OM. But don’t worry, the building is very easy, based on an Arduino nano board and a ttl-rs232 converter module
and doesn’t involve any hardware modification on the TX136/500. the principle of operation and the schema are described in the manual.

- Large improvement of script management, modes hopping or power variation cycle are now possible (see the examples in the manual)
- Some bugs fixed (see V1.13 changes file).

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]

Here is the V1.13 manual ant the AFP interface sketch 1.00.

73, Patrick F4GCB

[F4GCB]

And as usual for our Japanese friends, here is the version 1.13j which limits the RF power according to the portable regulation in Japan.
By the way, is this regulation still in force ?

73, Patrick F4GCB

[OK8LEO]

Did somebody successfully installed on jump tx 500 . I have version 1.12 but I have problems inginadsPicboot. Speed is the same Jumo is in terminal mode and the right USB port is selected . Does somebody know if there is a similar dspicbyoot for Mac Montery?

[7L1RLL]

Patrick,
Thank for your providing of v1.13 and v1.13j.
There is a formal regulation equal or less than 50W for portable amateur radio equipment in Japan.
However, many amateurs use TX136/500 under 12V with re-chargeable battery.
I would like to try for re-chargeable battery in v1.13 or v1.13j.
Now I am re-studying on both MPLAB X IDE and PICkit3 which will connect to JUMA TX500.

My First RS232c TERMINAL is occupied with GPS for WSPR. It needs to modify 2nd RS232C terminal for working of the new mode.

I have to report that my v1.07j has been worked very well for about 7 years.

73
Rick Wakatori, 7L1RLL

[7L1RLL]

F5GCB and the other TX136/500 users
HI
I am success to install TX136/500 v1.13 on my TX500 today.
I feel that both MPLAB and program device were updated for 7 years so far.
Now FST4W-120 works very well with a 12V battery, GPS and additional LPF. Thank you so much.
I will use only FST4W mode as WSPR migration path.
73
Rick Wakatori, 7L1RLL

[7L1RLL]

There may be an essential problem in automatic start transmission of FST4W-120 mode.
Usually, Automatic start transmission shall be begun at every 1 second of even minutes in UTC.
But TX136/500 v1.13 start at 02s, 03s in GPS time.
This causes differential time delay as 1s , 2s at the receiving side.
It looks independent between internal clock and GPS time.

At starting next TX, the following condition shall be displayed:
Waiting time : 00:00:00
GPS time : hh:mm:01

My testing environment is a TX500 with TCXO(1pps), additional LPF and GPS at URT1.
My development environment is MPLAB X IDE and PICkit3 under Windows 10 (64).

I am looking forward to seeing any suggestion.

73
Rick Wakatori, 7L1RLL

[F4GCB]

Hi Rick,

Thanks for your feedback.

For my part, no problem. With my TX136/500 synchronized GPS, I have a max offset of 0.4 s on an FST4W-120 frame decoded with WSJT-X, the PC being synchronized with NTP server.
Are you sure that your TX136/500500's clock is well synchronized with GPS. In this case the display is T^hh:mm instead of T hh:mm without GPS synchronization ?

73 Patrick F4GCB.

[7L1RLL]

HI Patrick,
Thank you for your reply.
　I am testing of dropping pulse of GPS now. GPS is located near windows. JUMA TX500 shows "T^mm.ss".
When good working, 160 slots are finished 110s after auto starting of FST4W-120. But bad condition, transmit finish 120s after auto starting.
At this point, Display shows "00:00 T^mm:02. This means one second delay starting. This delay time continues to forever until manual start.
I suppose the problem is near delay of transmitting process in some reasons: examples are drop pulse from GPS and delayed auto starting.
The delay can be seeing on the WSJT-X screen at receiving sites.
The occurrence rate is once per several hours depend on circumstance.
73
Rick Wakatori, 7L1RLL

[7L1RLL]

HI Patrick,

There is a difference between manual TX start and automatic TX start such as:
1)Manual start is triggered by GPS time,
2)Automatic start is triggered by waiting time counter.

GPS time shows actual time if a pulse dropped.
But waiting counter counts down by IRG * 1000ms independent of dropping of GPS pulse.

I suppose that the waiting counter does not subtract by one when a GPS pulse dropped.
This error has been existed from the beginning, but we have this problem.
I made a big hole as 22mm * 25mm at GPS plastic box in front of GPS antenna.