Why do I use an external LOG program for sBitx v3?
|
I want to eventually be able to use N3JFP's Amateur Contact log.?
I love his logbooks but they are all for Windows. Others have been able to get it to work on Linux. I want to get it working on my main PC that is running Linux then try it on my sBITX.? What did you use for screen capture for your videos?? -- '72 Aaron? |
|
I made the screencast recordings with a . You can install it from the command line in the terminal or from the menu.
Due to the 7" screen, it is difficult to find a good LOG program. This is also why Ashar developed the FT8 program for the 7" screen, because all the decoders that work well are made for a larger screen. That's why there are mistakes here, ones you didn't even think about. -- Gyula HA3HZ |
|
Just for those who don't understand why I put this video up.
I'm testing the FT8 mode and two qso's were not saved to the LOG file before restarting, so I restarted it. After I restarted the RPi, you can see it at the beginning of the video, it didn't save the first qso. Only the external LOG program shows that there was a valid qso. The next station has been automatically saved. Here it appears that I forgot to press <enter> in the external LOG program, so I had to correct it. That is, to enter the report. Yes, I can do it here. I cannot write to the sBitx LOG program here, so I use an external LOG program. In the FT8 mode, I have several observations: when the automatic LOG saving is done, a <MYCALL CALL 73> comes from the station goodbye, then my machine detects this as a report and reports again <CALL MYCALL R-xx> This continues until there is no goodbye again. Other: for those callsigns that are long and there is no GRID when transmitting, the program automatically writes RR73. If the call sign is long or special, <...> is shown in the reception window. This happens even if the call sign can be played for the first time, the LOG is already saved as <...>. Yes, I know... it also happened with known external programs 6-8 years ago. It should be improved to be really usable. -- Gyula HA3HZ |
|
In the log program, in the case of FT8 mode, the data of the qso is saved when the report is sent and received (if both exist).
This is fine so far when both stations receive each other well. The problem stems from the fact that if there is no RRR or RR73 followed by 73, it is not certain that the R-xx report we sent earlier has reached its destination. In this case, the station does not recognize the connection. We should delete this save from the log file. The only way to do this at the moment is to load our sbitx.db file into the DB Browser (SQLite) program and delete the given line there. Yesterday on 21 MHz, I received a report from VA2WM, which was not acknowledged due to the spread or only I did not see it, so I deleted it from the log. I'm still struggling with the problem of what to do when it doesn't record the qs in the LOG file. When I restart the RPi it still doesn't record every time. Therefore, it is necessary to use the external log program. This external log is authoritative for me as to whether the qso ran all the way through or not. After that, I will combine the data of the two log files and either delete them, because they did not finish the qso, or I have to enter them, because they did not record anything. I feel like I'm left alone with the problem. Any suggestion or solution will be gratefully accepted. -- the data in the right table are in chronological order Gyula HA3HZ |
|
On Sat, Dec 30, 2023 at 03:24 AM, HA3HZ wrote:
In the log program, in the case of FT8 mode, the data of the qso is saved when the report is sent and received (if both exist).If I understand?/g/BITX20/message/106151?correctly, then the software is operating as intended. That message states: On Fri, Nov 17, 2023 at 07:15 PM, Ashhar Farhan wrote: Sorry if I am not understanding the situation correctly. ? -- Regards, Dave, N1AI |
|
Yes, I read the message. Says someone who hasn't been making FT8 QSOs consistently.
If he had done it, then the listed mistakes would have happened to him as well and he would have understood it better. What can be done with a LOG program in which, in the case of FT8 - if you do not save the QSO and you have all the data, you already had the answer to RR73 - and saving to a log file does not work? Then you try to do something, but you can't, because the LOG data input doesn't work either. It doesn't help that sometimes it's good and sometimes it's not. I feel that it is completely unnecessary to write anything here for those who have never used it and do not know the specifics of the mode. You can read back what I said on this topic. After that, I will not write, and I will also sink the sBitx device to a great depth. I take out my older devices, I was not disappointed with them. I dismantled my antennae in the spring so that the descendants would not have to deal with it. If I hadn't seen imagination in this device, it wouldn't be here now. But I was disappointed. I guess everyone is focusing on the RPi5 now, when the RPi4 doesn't work well here either. But come on... it's the future. I wish the group all the best and good health for that. -- Gyula HA3HZ |
|
On Sat, Dec 30, 2023 at 04:56 PM, HA3HZ wrote:
If I hadn't seen imagination in this device, it wouldn't be here now. But I was disappointed.I also see the imagination in this device.? I am sorry you are disappointed. I guess everyone is focusing on the RPi5 now, when the RPi4 doesn't work well here either.
|
HA3HZ
Aaron K5ATG
Dave, N1AI