Date   

locked Re: 500 KHz drop #Cat_RigControl #txaudio

Gene Horr
 

Read my posts from several days ago about similar action when changing the TX offset and see whether you are having similar problems.

Also how is your split handled, rig or "fake it"?

Gene
NG1H


locked Re: LoTW Confirmations #TechnicalHelpQuestion

Bill Murray
 

Been mean to reply to this for a day or two.  I am not sure if we are talking the same thing.

I have JTAlert in the Settings Menu to alert me when an unworked DX station has appeared.  I don't have it show in a new panel.  Go to Wanted DX or Wanted States or whatever you want in the Individual Band.  In the new window will be, say for new DX, a two-pane panel.  On the right side are the 340 (?) DX entities and the left side will be blank.  Find your LOTW confirmations on the right side, click on them and move them with either > or >> to the left side.  Your initial effort will be tedious.   Now, those Countries won't alert you as being new.  

Under Band Enable and Select, Check the bands you want--I didn't select 160m, 60m, 4m, and 2m.  When you get a new LOTW confirmation, with JTAlert up and running, Click on the Band you want to add this new country to and then scroll down the right-hand panel, find the new country and move it to the left-hand panel.  If you are already on, say, 40m, and the new LOTW is on 40m, the Window for 40m will come up automatically.  If you are on 20m, you just click on 40m and you'll be taken to the 40m listing.

On the initial Wanted DX selection, you can have it send you a sound to let you know that a new DX country is on, say 40m. You have to be on the same band--it won't alert you to 20m when your radio is on 40m.  I chose a siren and it's loud.  So, I can be 25' away watching TV, hear the siren and then go see what the new country is.  In the WSJT-X panel, the new country will be highlighted in some color that you or the program has selected.  For me, it's yellow for the call sign although sometimes the entire line is highlighted in blue. Haven't figured that out.  Probably blatantly obvious.

I'm not sure your message is telling me that you're doing the same thing.

Bill




On Tue, Sep 7, 2021 at 7:19 AM Patrick Hung <pathung@...> wrote:
Thanks, all. I've now set JTAlert to show me only LoTW stations in one of its panels, which is of great help. A second panel shows all needed DXs, so that I can make a decision to answer or not on a case by case basis. With physical card rate being low as it is, I'll likely just patiently wait for the right LoTW station to come along.
--
73,
Patrick, W6AJR



locked Re: 500 KHz drop #Cat_RigControl #txaudio

Matthew Chambers NR0Q
 

I meant to say 500Hz not kHz in my reply earlier (brain-keyboard error)

On 9/10/21 1:14 PM, William Smith wrote:
Two possibilities:

1) WSJT-x will shift your Tx frequency by 500 Hz (not KHz) in order to keep the Tx audio in the presumed middle of your T audio filters. Works as designed, don’t try to correct it.

2) You have a Transverter setting that’s shifting you by 500 KHz (not Hz). Check your settings.

73, Willie N1JBJ
--
The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent
of the sender. If you received this message by mistake, please reply to
this message and follow with its deletion, so that we can ensure such a
mistake does not occur in the future.

Please do not print this email unless it is necessary. Every unprinted email helps the environment.


locked Re: 500 KHz drop #Cat_RigControl #txaudio

William Smith
 

Two possibilities:

1) WSJT-x will shift your Tx frequency by 500 Hz (not KHz) in order to keep the Tx audio in the presumed middle of your T audio filters. Works as designed, don’t try to correct it.

2) You have a Transverter setting that’s shifting you by 500 KHz (not Hz). Check your settings.

73, Willie N1JBJ

On Sep 10, 2021, at 1:52 PM, Wayne Rash <Wayne@rash.org> wrote:

I know there’s probably a simple explanation for this, but WSJTX is dropping the frequency on the transmitter by 500 KHz every time it transmits a CQ. This means that I have to constantly correct this just to stay within the FT8 frequencies. I’m sure it’s a setting that I can’t find, but if someone knows the answer, I’d sure appreciate it.

I’m running WSJTX 3.9.0 on Windows 10 Pro v. 10.0.19043 using Log for OM 2.17. The rig is a Yaesu FT920

Thanks for your thoughts.

Wayne, N4HCR



locked Re: 500 KHz drop #Cat_RigControl #txaudio

Matthew Chambers NR0Q
 

This is by design, WSJT-X will shift your VFO frequency up/down in 500kHz steps and your transmit audio frequency to always stay within 1500-2000kHz in the sweet spot of most radio's bandpasses.  Here's an article that explains further https://www.k0pir.us/wsjt-x-split-operation/.

Matthew NR0Q

On 9/10/21 12:52 PM, Wayne Rash wrote:

I know there’s probably a simple explanation for this, but WSJTX is dropping the frequency on the transmitter by 500 KHz every time it transmits a CQ. This means that I have to constantly correct this just to stay within the FT8 frequencies. I’m sure it’s a setting that I can’t find, but if someone knows the answer, I’d sure appreciate it.

 

I’m running WSJTX 3.9.0 on Windows 10 Pro v. 10.0.19043 using Log for OM 2.17. The rig is a Yaesu FT920

 

Thanks for your thoughts.

 

Wayne, N4HCR





The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.

Please do not print this email unless it is necessary. Every unprinted email helps the environment.


locked Re: 500 KHz drop #Cat_RigControl #txaudio

Bill Somerville
 

On 10/09/2021 18:52, Wayne Rash wrote:

I know there’s probably a simple explanation for this, but WSJTX is dropping the frequency on the transmitter by 500 KHz every time it transmits a CQ. This means that I have to constantly correct this just to stay within the FT8 frequencies. I’m sure it’s a setting that I can’t find, but if someone knows the answer, I’d sure appreciate it.

 

I’m running WSJTX 3.9.0 on Windows 10 Pro v. 10.0.19043 using Log for OM 2.17. The rig is a Yaesu FT920

 

Thanks for your thoughts.

 

Wayne, N4HCR

Wayne,

are you sure the Tx frequency is shifting down by 500 kHz?

A -500 Hz Tx VFO dial frequency shift, when your Tx offset is between 1000 Hz and 1499 Hz, is normal and correct behaviour if you have one of the"Settings->Radio->Split Operating" options checked.

73
Bill
G4WJS.


Wayne Rash
 

I know there’s probably a simple explanation for this, but WSJTX is dropping the frequency on the transmitter by 500 KHz every time it transmits a CQ. This means that I have to constantly correct this just to stay within the FT8 frequencies. I’m sure it’s a setting that I can’t find, but if someone knows the answer, I’d sure appreciate it.

 

I’m running WSJTX 3.9.0 on Windows 10 Pro v. 10.0.19043 using Log for OM 2.17. The rig is a Yaesu FT920

 

Thanks for your thoughts.

 

Wayne, N4HCR


locked Re: Accidental conversion of adi log to Notepad doc #logging

Istvan Nyul
 

If the incorrect file name is "xxxxx.ADI.TXT then just delete the .TXT leaving the .ADI at the end and you will be fine.

​Regards,
​Steve - VE3USP



----- Original Message -----

From: K1dj via groups.io (k1dj@...)
Date: 09/10/21 12:39
To: main@WSJTX.groups.io
Subject: [WSJTX] Accidental conversion of adi log to Notepad doc #logging

I made the mistake of trying to correct a callsign in my adi log, and mistakenly saved the result as a Notepad document.  The document still is identified in the "type" column as an "adi."

Any way to undo or correct this?

Running WSJT-X v.2.3.1 on PC with Windows 10 Pro v. v.20H2






locked Re: #Cat_RigControl Rig Control Error WSJT-X FT8 v2.5.0-rc6 #Cat_RigControl #Icom

Gene, K5PA
 
Edited

Bill, the Com40 is a com0com pair (com40 and com41). Com40 is for the WSJT-X and Com41 is for the Win4Icom Client at my home QTH. The Win4Icom Server of course is at the remote site connected via a standard USB interface from computer to IC-7300. On the local com port baud, I have tried decreasing to as low as 9600 but has not had an effect.

I went back this morning to verify my statement that it was working with WSJT-X v2.5.0-rc4 on FT8 but noticed it also was failing. I then re-installed the WSJT-X v2.4.0 GA and it works flawlessly. I have been using v2.4.0 GA for some time now but decided v2.5.0-RC6 was getting close to the GA release that I started working with it to see how it behaves. Locally, my IC-7610 seems fine on the ver 2.5.0-rc6 with it using Split, Fake It or None.

UPDATE:  Mike, W9MDB, provided me a code update that corrected the erroneous behavior I was seeing. I ran his modified code for a day on the remote IC-7300 using the Win4Icom Server and Client and can report it worked flawlessly. I also ran it with my home QTH station consisting of the IC-7610 and it work fine there too. Mike told me he would have the code updated with his changes in the next version released. THANK YOU Mike for working with me on this.

73, Gene, K5PA



locked Re: PC Audio Output Level decreases during Transmission #AudioIssues #transmit

Glen Jenkins WB4KTF
 

Hello Willie,
Clarification:  On the PC under Settings/Sound at the OUTPUT Master Volume  bar, I have it set at 91, during transmission the horizontal indicating bar starts at the 91 reading and then moves DOWN to around 25.  Note that there is a moveable setpoint marker, I have this set at 91, it stays fixed at 91, The indicating bar/meter is what I see moving from 91 to 25.   Then each and every transmission it starts back at 91 and then moves down to about 25.  My transmitter RF output follows this reduction thus starting at about 90 watts and ending up near 27 watts output.  It's like some ALC is reducing the audio drive level, yet there is NO ALC reading on the IC-7610 the whole transmit cycle.
The same reduction occurs when I initiate a TUNE from the WSJT-X button.  The ALC indicating bar on the IC-7610 stays at Zero 0, with no reading, yet the PC Master Volume indicator moves down to lower values..
Glen, WB4KTF
Austin, TX


locked Re: Accidental conversion of adi log to Notepad doc #logging

Pietro Molina
 

OM,

do you intend that the icon of the document is the notepad one? Don't worry, it just indicates that you will open adi files with notepad by default. File is still ADI.

Pietro I2OIM

PS: sign your messages!

Il giorno ven 10 set 2021 alle ore 18:39 K1dj via groups.io <k1dj=aol.com@groups.io> ha scritto:
I made the mistake of trying to correct a callsign in my adi log, and mistakenly saved the result as a Notepad document.  The document still is identified in the "type" column as an "adi."

Any way to undo or correct this?

Running WSJT-X v.2.3.1 on PC with Windows 10 Pro v. v.20H2



locked Re: #Cat_RigControl Rig Control Error WSJT-X FT8 v2.5.0-rc6 #Cat_RigControl #Icom

Bill Somerville
 

On 10/09/2021 15:19, Gene, K5PA wrote:
I had been using WSJT-X FT8 v2.5.0-rc4 without a rig control error message. However, when I began using v2.5.0-rc5 or -rc6 this week, I would receive a Hamlib error: IO error message. This was when using either Fake It or Split modes on an IC-7300 transceiver. Going back to version -rc4 cleared this error from occurring. The error message is pasted below.

The unusual setup I have is that I am using a transceiver at a remote location and controlling over the Internet. I am using Win4IcomSuite remote server to control the radio and to send audio between my local client computer and the server computer attached to the IC-7300. I can reproduce this error and it happens fairly regularly. I have done several days of troubleshooting but have not been able to resolve and had to revert back to WSJT-X v2.5.0-rc4. I believe my system also operated correctly when using WJST-X v2.4.0 GA so I was surprised to find this error when I tried WSJT_X v2.5.0-rc6.

My station computers at both locations are Windows Pro x64. The remote only has the win4Icom Server running on it and my local computer has the WJST-X, JTAlert v2.50.5  and HRD logging run on it. Any insight would be appreciate or tell me what tests to run to provide added information.
Thanks, Gene, K5PA

Hi Gene,

what is providing COM4 on your local machine?

73
Bill
G4WJS.


locked Re: Accidental conversion of adi log to Notepad doc #logging

William Smith
 

Did you add a file type (.txt or something) to the end of the filename? You might have to enable ’see file types’ or right-click and show properties to determine if it’s a file type mismatch.

If you somehow changed the newline character, you might have to do some more surgery, though I’d hope that would be transparent to whatever’s reading the file.

73, Willie N1JBJ

On Sep 10, 2021, at 12:18 PM, K1dj via groups.io <k1dj=aol.com@groups.io> wrote:

I made the mistake of trying to correct a callsign in my adi log, and mistakenly saved the result as a Notepad document. The document still is identified in the "type" column as an "adi."

Any way to undo or correct this?

Running WSJT-X v.2.3.1 on PC with Windows 10 Pro v. v.20H2


locked Re: Accidental conversion of adi log to Notepad doc #logging

Bill Somerville
 

On 10/09/2021 17:18, K1dj via groups.io wrote:
I made the mistake of trying to correct a callsign in my adi log, and mistakenly saved the result as a Notepad document.  The document still is identified in the "type" column as an "adi."

Any way to undo or correct this?

Running WSJT-X v.2.3.1 on PC with Windows 10 Pro v. v.20H2
OM,

there is no such thing as a "Notepad document", notepad is a basic text editor. If MS Windows identifies the file as an ADI type file then there is nothing to fix.

73
Bill
G4WJS.


locked #Cat_RigControl Rig Control Error WSJT-X FT8 v2.5.0-rc6 #Cat_RigControl #Icom

Gene, K5PA
 

I had been using WSJT-X FT8 v2.5.0-rc4 without a rig control error message. However, when I began using v2.5.0-rc5 or -rc6 this week, I would receive a Hamlib error: IO error message. This was when using either Fake It or Split modes on an IC-7300 transceiver. Going back to version -rc4 cleared this error from occurring. The error message is pasted below.

The unusual setup I have is that I am using a transceiver at a remote location and controlling over the Internet. I am using Win4IcomSuite remote server to control the radio and to send audio between my local client computer and the server computer attached to the IC-7300. I can reproduce this error and it happens fairly regularly. I have done several days of troubleshooting but have not been able to resolve and had to revert back to WSJT-X v2.5.0-rc4. I believe my system also operated correctly when using WJST-X v2.4.0 GA so I was surprised to find this error when I tried WSJT_X v2.5.0-rc6.

My station computers at both locations are Windows Pro x64. The remote only has the win4Icom Server running on it and my local computer has the WJST-X, JTAlert v2.50.5  and HRD logging run on it. Any insight would be appreciate or tell me what tests to run to provide added information.
Thanks, Gene, K5PA
  


locked Accidental conversion of adi log to Notepad doc #logging

K1dj
 

I made the mistake of trying to correct a callsign in my adi log, and mistakenly saved the result as a Notepad document.  The document still is identified in the "type" column as an "adi."

Any way to undo or correct this?

Running WSJT-X v.2.3.1 on PC with Windows 10 Pro v. v.20H2


locked Re: After upgrade to WSJT-X 2.4.0, an IC-7600 no longer changes bands on SPE Expert 1K-FA power amplifier #Cat_RigControl

Frode Igland
 

This regrettably late reply responds to comments by Allan ZS1LS in Digest #2090 on 25 August 2021, and by Bill G4WJS and Mike W9MDB in Digest #2075 on 20 August 2021.

In our club station, we have now made more extensive examinations of the latest versions of WSJT-X and how they work with the IC-7600 and SPE Expert amplifiers.

The setup was:

  • Softwares: WSJT-X 2.3.1, WSJT-X 2.4.0, WSJT-X 2.5.0-rc5;
  • Radio: IC-7600 (firmware 2.0);
  • Amplifiers: SPE Expert 1K-FA and SPE Expert 1.3K-FA both set to “ICOM” Cat control.

The HP computer is connected to the radio via USB A-B cable. The radio is connected to the PA via the CI-V socket on the radio to the DB-15 CAT socket in the amplifier, as well phono plugs from the “Send” and “ALC” sockets on the radio to the “Relay”/”RY1” and “ALC”/”ALC1” sockets on the amplifiers.

First of all, some clarifications/reminders. The amplifiers are always connected to the TX VFO in use. If WSJT-X Settings – Radio – Split is set to “None”, VFO A is used for transmission as well as reception. VFO B is not in use. The same applies to “Fake it”, only VFO A is in use. In “Fake it”, the “split” effect is achieved by VFO A changing frequencies between the TX and RX sequences, if the audio frequency is outside the 1500-2000 Hz sweetspot. Only when Split is set to “Rig” does WSJT-X apply both VFOs, and then VFO A is used for RX only, whilst VFO B is the one used for transmission and thereby is the one to activate the amplifier.

WSJT-X 2.3.1 – All OK

We first tried with WSJT-X 2.3.1. No matter which Split setting we used, the radio and the PA immediately followed all band changes in WSJT-X. This has been our smooth experience for years, until version 2.4.0.

WSJT-X 2.4.0 – Radio VFO B changes band, the PA does not

We then tried with WSJT-X 2.4.0 (the current GA). With Split set to “None” or “Fake it”, VFO A followed the band changes in WSJT-X and the amplifier followed the VFO A. VFO B stayed in the previous band, which was as expected, as for “None” or “Fake it” VFO B is simply not in use.

With Split set to “Rig”, VFO A and VFO B followed the band change in WSJT-X, whilst the amplifier did not and stayed in the previous band, as previously described. As the amplifier follows the TX VFO, i.e. VFO B, it was to be expected that the amplifier changed bands when VFO B changed bands. The question here is: Why has VFO B stopped instructing the amplifier to change bands, or why has the amplifier stopped taking orders from VFO B? 

WSJT-X 2.5.0-rc5 – Neither the Radio VFO B nor the PA changes band

Finally, we tried WSJT-X 2.5.0-rc5, the release candidate at hand when the tests were conducted.

With Split set to “None” or “Fake it”, VFO A changed bands, but the amplifier did not follow. VFO B was unaffected, as expected, as it is not in use in “None” or “Fake it”.

With Split set to “Rig”, VFO A followed the band changes in WSJT-X, whilst VFO B as well as the amplifier stayed in the previous band. As the amplifier follows the TX VFO, i.e. VFO B, it was to be expected that the amplifier did not change when VFO B did not change.

The question now is: Why has WSJT-X stopped instructing VFO B to change bands? This time the PA can not be the one to blame (yet), as the PA does exactly as instructed by VFO B: Stay in the previous band.

CI-V Transceive and CI-V Output (for ANT) ON or OFF have no influence

All the exercises above were systematically conducted with all combinations of the radio’s SET – OTHERS – “CI-V Transceive” and SET – OTHERS – “CI-V Output (to ANT)” toggled between ON and OFF. These two settings made no difference in the results described above.

That it works with “CI-V Transceive” ON as well as OFF seems to be in line with the WSJT-X User Guide, section 16. Frequently Asked Questions, #4:

I occasionally get Rig Control Errors if I adjust my Icom rig’s VFO. What’s wrong?

By default, most Icom transceivers have *CI-V Transceive Mode" enabled. This will cause unsolicited CAT traffic from the rig that disrupts CAT control by a PC. Disable this option in the rig’s menu.

Expert 1.3K-FA and Expert 1K-FA give the same results

We have made the above tests on both our old Expert 1K-FA and our new Expert 1.3K-FA. The results are identical.

TX Audio frequency makes no difference

Trying several TX audio frequencies below, above and in the 1500-2000 Hz audio sweetspot made no difference.

N1MM Logger+ works smoothly with version 2.4.0

In the WW-DIGI Contest, I used the club station with WSJT-X 2.4.0 with N1MM Logger+ running the IC-7600 and the Expert 1.3K-FA. Everything worked smoothly, just like in version 2.3.1. As soon as I tried to operate version 2.4.0 standalone with no other changes made anywhere, the band change issue returned.

Is there any clue in the fact that version 2.4.0 does not change PA bands when operated standalone, whilst it works just fine when controlled by N1MM Logger+?

Summary

In version 2.3.1, everything works smoothly.

In version 2.4.0, VFO-B changes bands as instructed by WSJT-X, but the amplifier does not change bands. Version 2.4.0 works flawlessly when WSJT-X operates under N1MM Logger+.

In version 2.5.0-rc5, VFO B does not even change and then obviously not the amplifier.

The WSJT-X version number is the only identifiable variable that has an influence on the PA band changes.

That is why we think that the non-working PA band changes in WSJT-X 2.4.0 (standalone) and 2.5.0-rc5 have something to do with changes in the later versions of WSJT-X and/or it’s auxiliary CAT software.

73, Frode LA6VQ


locked A Pocket Sized FT Transceiver #decode #FT8 #transmit #Waterfall

Charles Hill
 

To All,

I have published another FT8 Transciever Project called Pocket_FT8 on github at https://github.com/chillmf/Pocket-FT8.

This project uses a Teensy 3.6 to send and receive FT8 messages on 17 meters. All you need to add is an antenna.

Source code and build instructions are included.

Regards,

Charley, W5BAA


locked Re: #IssueReport #WSPR #IssueReport #WSPR

Hasan Schiers N0AN
 

Kenwood TS-590sg, not using internal tuner. Only using the MFJ-998RT in the shack, 1500w autotuner.
Hasan


On Fri, Sep 10, 2021 at 3:29 AM Bill Somerville <g4wjs@...> wrote:
Hi Hasan,

which rig are you using? Are you using an auto-ATU built into your rig?

73
Bill
G4WJS.

On 08/09/2021 21:22, Hasan Schiers N0AN wrote:
Also RC6 here, although downloaded a few days ago. I think there was a hamlib fix since then, but have not downloaded since very early RC6.

73, N0AN
Hasan


On Wed, Sep 8, 2021 at 11:21 AM Bill Somerville <g4wjs@...> wrote:
Hi Hasan,

Steve, K9AN, and I are running WSPR band-hopping with a variety of bands set for Tune and Rx only. Neither of us are seeing this issue so far. I am using the latest 2.5.0 RC6 version.

73
Bill
G4WJS.

On 08/09/2021 15:00, Hasan Schiers N0AN wrote:
No, no errors at all, see an occasional audio stream error, nothing else

Hasan


On Wed, Sep 8, 2021 at 8:20 AM Bill Somerville <g4wjs@...> wrote:
Hi Hasan,

are there any Hamlib error messages in the WJST-X wsjtx_syslog.log file that correlate with the time of the issue?

73
Bill
G4WJS.

On 08/09/2021 01:09, Hasan Schiers N0AN wrote:
Bill,
I found the correlation I was looking for. 

If I tell WSPR Schedule to use the TUNE function (to make the autotuner adjust the antenna SWR on each band prior to transmitting), the ENABLE Tx light goes out in short order (next transmission or so).

If I uncheck the boxes on each band for Tune, and let the transmit signal itself actuate the auto-tuner, everything works normally.  

In reality, the TUNE function in the Scheduler is redundant, because the autotuner itself will auto-tune when RF is sent to it anyway, there is no need to 'pre-tune' things.

However, what I am reporting is undesirable and probably should be fixed, if it's a real malfunction.

73, N0AN
Hasan


On Sat, Sep 4, 2021 at 12:21 PM Bill Somerville <g4wjs@...> wrote:
On 04/09/2021 13:34, Hasan Schiers N0AN wrote:
WSJT-X 2.5.0 RC5
Mode WSPR
 
Issue:
 
When in Band Hopping Mode, with a proper schedule, the Enable Transmit button randomly goes dark and never lights up again.
 
This results in hours and hours of listening overnight with no transmitting. 
 
Is there an order effect or something that would cause this in terms of setup? It used to work perfectly with identical settings many versions ago.
 
Anyone else seen this?
 
TIA, 73, N0AN
Hasan

Hi Hasan,

that behaviour may be caused by a CAT error. Have a look in the wsjtx_syslog.log file (in the WSJT-X log files directory) for any Hamlib error messages around the time that the "Enable Tx" button resets.

73
Bill
G4WJS.






locked Re: JT65 #decode

Bill Somerville
 

On 10/09/2021 03:58, Jim Brown wrote:
On 9/9/2021 6:58 AM, Robert Woltag wrote:
  JT65 mode does not seem to decode anything.

Where are you looking for JT65? It's not a "random QSO" mode like FT8 and FT4, but more of a special purpose weak signal mode like MAP65, JT9, FST4 and Q65, and the newer of those modes, FST4 and Q65, are likely to replace JT65 and JT9.

73, Jim K9YC

Hi Jim,

a minor correction to thee above, MAP65 is not a mode, it is another data communications application designed to take advantage of wide-band I/Q input (it also supports base band audio and UDP data from Linrad) and dual polarization aerial systems. It supports JT65 and Q65-60* modes, and is used for VHF and UHF EME where adaptive polarization can give significant decode sensitivity advantages.

73
Bill
G4WJS.

5701 - 5720 of 34101