开云体育

Just upgraded to v3.02 - log DB (sbitx.db) no longer updated with new contacts.? How is the log managed now?
--
Mike WB5LLI

Mike,
With which version did you start creating the database?
Which mode do you have a problem with, manual or automatic input?
--
Gyula HA3HZ

Hi Gyula,? I did a reinstall after upgrading my v2 folder to v3.02.? I had v3 operating fine in a separate folder.? The problem was with FT-8 and some repeat transmits the macros as well as showing "logged" twice.?? I did a clean install again last night and ran ./build.? So far on my tests this morning it is operating normally again.? I did foece a few manual log entries too so that may have started the autologging up again.


--
Mike WB5LLI

Mike,
I understand. A few things work interestingly with ft8 autosave.
When I turn on the device, the first connection says twice that it has been logged. Actually once.
If the double logging is not visible on the display, it is worth pressing the manual log entry, because it is not in the log.
It only does this the first time you turn it on.
Before that, I look at the log file, close it, and then leave until the data is in the LOG window on the GTK screen.
It happens that you end the connection earlier and then delete it from the LOG window. You have to pay attention to the operation.
So for the first QSO, I always press a PrtSc i.e. Print Screen button, you can find the picture in the /home/pi folder.
Because if you don't save it in the log file, then I have data for later input.

I'm writing these things because that's what I'm currently doing in order to function well.
There are more things, but so far no one has responded to my entries. Everything remains the same.
--
Gyula HA3HZ

My interesting cases today in pictures.
In the picture you can see that saving to the LOG file was done twice, while in reality it was once. The program does not allow you to save the same thing again in the log file within two minutes.
So it can be seen from this that at first he only wrote to the screen, but did not save. For the second one, I pressed the SAVE button manually, then the saving was done. The interesting thing is that when I turn on the device, it does this the first time. The subsequent qso is saved to the log file.



With the sbitx (rf output 10W) and the vertical loop antenna, this would have been my first South American qso. It failed to confirm during the past 6 minutes, but it was automatically saved to the log file three times. This happened because of the logic of saving to a log file.




--
Gyula HA3HZ

Gyula,? just confirmed what you said.? I just turned the rig on and the first contact showed "logged" twice but does not appear in the log file. It looks like the second contact worked normally and auto-logged.?? So simply manually logging the first contact seems to work around the issue.
--
Mike WB5LLI

Today when I started sbitx I opened the LOG file and then closed it.
For the first QSO, it was written on the display only once and then it saved the QSO.
Maybe this is the solution?
--
Gyula HA3HZ

I will try that and let you know.


--
Mike WB5LLI

The first QSO after switching on is written twice on the screen, while making a LOG file entry once.
The solution is to look into the LOG file after starting sbitx and then close it.
After that, everything goes normally.
If I don't open the LOG file and close it, it says on the screen twice at the first QSO that it was entered in the LOG.
In reality, it only appears once.
But it happened that he did not enter the data even once.

Maybe it's a permission issue to get into the LOG file?
I don't know the spiritual world of OS, I'm just thinking out loud.
--
Gyula HA3HZ

Gyula,? I can confirm that opening the log before making any contacts will allow that first contact to be logged.? For me it was logged twice but that is better than not at all.
--
Mike WB5LLI

I use sbitx v3.02 to save ft8 QSO auto log file. After starting the program, I need to go into the LOG file and see its contents.
If I don't go in and make a QSO, the first QSO says Logged: but in reality it doesn't save.
In such cases, as long as the data is visible in the LOG window, I save it immediately with SAVE, because sometimes it is not saved.
Since I automatically check the LOG file after every QSO, it no longer happens that the automatic save just writes and does not save.

The output power of the device is closer to the QRP category, so I often use the \r (AltGr+Q and r) command so that when a transmission is coming, I can check whether the transmission frequency I am using is empty or a 100-watt weak signal has just arrived.
If it's not empty, I have a few seconds to make changes and quickly press the F2-F3-F4 button corresponding to the current state so that I don't miss my broadcast period. This is how I do it.

I awkwardly make sure that if I can read the call sign of the station in the reception window, it should only be the accepted composition. If it is different from the usual, i.e. it contains a / sign or several numbers or several letters, the program cannot handle it and it will transmit <...> signals and save them in the log file.
Regardless, it may happen that a station with such a call sign calls you back. Then I inform him that 'Callsign not decode'.

What are these unusual call signs, some:
KH0/KC0W, DL800SI, RA3/UN7ZR, R101AE, CT9/NZ1C, AO100RADIO, NP2Q/QRP, R3KLQ/p, PJ5/SP9FIH, OZ/DK9VE, DD100FK...and so on.
These callsign combinations are not handled correctly by sbitx in ft8 mode.

The reason for this is that the built-in 7" LCD display can handle an image size of 800x480 pixels, so the author had to write this program for the RPi.
All other known weak signal mode programs use a larger image size and have undergone several years of development and these errors were eliminated there.
I have a plan to use a higher resolution monitor and make it portable and not expensive. I haven't tested it yet because I'm waiting for an adapter.
--
Gyula HA3HZ

I use sbitx v3.02 to save ft8 QSO auto log file. After starting the program, I don't have to enter the LOG file anymore. The modification can be found on github a few days ago.
Since I have been constantly testing it since its release, I can safely say that in ft8 mode, the QSO is saved automatically and without error after switching on.

The complex call signs listed in the previous message are not displayed in ft8 mode and they cannot be recorded in the log file either. Due to its size and light weight, the device can be ideally used for camping and radio broadcasting from other areas. Due to the lack of storage of complex call signs, the special call sign cannot be recorded.
This problem has been solved in other programs designed for digital plants. I'm no coder, but I understand those source files are available.

I am painfully careful not to call stations with these call signs. But I can't avoid it when I'm called by such a station, whose callsign I can see so much <...>.
Every time I answer: callsign not decode or use short callsign. I would like a contractor who can code to fix this problem. The call sign is also not visible in the reception window. The log file cannot store these characters either.
--
Gyula HA3HZ