Hi,
i'm using CQRLOG Version 2.1.0 (125).
At the moment i am often qrv on short wave with FT8 and want to work VK and ZL.
So it would be nice, if you could enter VK,ZL in the Inputbox between Text and Alert in the wsjt-x cq-monitor, and it gives you an alert for *VK* and *ZL* Text.
Bye DL7OAP, Andreas
Hi !
Ok, you are using my devel-version then.
Fine. Testers and their comments are always important and welcome.
At the moment text alert search just text-in-text. So you can set ZL or VK (just one at time) for text and they hit for prefixes like those, but also suffixes like OH1ZL and someone who is calling CQ ZL CALLSING LOCATOR
Also characters like % and * are just handled as letter that it actually is.
I will consider this but it needs little more than just text search. Cases like this the search should only be targeted to originating callsign to fill the purpose.
--
Saku
OH1KH
--
Saku
OH1KH
Hi Andreas !
Please check devel-version 126 and tell me what you think. Also report bugs (and how to reproduce them) if found.
See the PDF in zip file for description of new text alert usage.
--
Saku
OH1KH
--
Saku
OH1KH
Hi Saki,
thanks :-) that's fast.
Developversion 126 is running now.
Systemsound via graphicard and HDMI over the screen (with integrated speakers).
FT8 and wsjtx rc3 via the internal soundcard on the mainboard. using ubuntu 16.04.
the very first test looks like that all works fine.
i will give you feedback in the next days.
thanks a lot, Andreas, DL7OAP
Hi Saki,
first: after testing some hours i found no bugs or errors. good work!
For me this version is perfect, just work a new maingrid and 2 new DXCC countries with the help of the alerts today.
some observations and testings i did:
- in the new document CqrlogAdditions2.pdf the "w c" alert for text is not mentioned. only in a screenshot you see this order of letters, but with no hint, for what it is good for. in the old version there was a sentence for "w c".
- the program ignores *7*. so *7*,RL*,PA* alerts RL and PA-Station fine and didn't give a crash. documentation mention perfect, that only one asterix is allowed. good!
- "w c" in text still works fine to alert new countries
- only one asterix * will alert every station. think this is a feature. good.
- HB0/DD5ZZ will be alert with HB* and with HB0/*. it will not be alert with DD*. think this is ok. good.
- EI2KO/p is alert with */p . fine.
- i used today MyAlert, LocAlert and CallAlert together. it works all fine and correct in this combination. good.
- maybe the only thing you could investigate is the follwing:
wsjtx gets this "175200 -9 0.1 1109 ~ CQ NO EU RZ3DX".
wsjt-x cq-monitor recognized it as "175200 ~ EU RZ3DX Belarus CQ:NO QSL needed !"
and it make an LocationAlert on this due to the maingrid "RZ3DX". This was the only wrong alert i get today.
Please look at the attached screenshot.
- maybe someone want to filter for VK*,ZL* and wants to combine this with the "new country" alarm, i think this is at the moment not possible. but i personaly don't need it.
Thank you very much
Andreas, DL7OAP
File:
Hi Andreas
Thanks for testing and good comments.
- in the new document CqrlogAdditions2.pdf the "w c"
I must add that, it dropped away when editing.
- the program ignores *7*. so *
Yep, only one asterisk allowed , but you get all 7 with just only 7. (but you will get 77, 73 etc, too)
- "w c" in text still works fine
Text search side is not modified at all, everything works as before.
- HB0/DD5ZZ will be alert with HB* and with HB0/*.
Use 0/DD5 should hit only that station. No asterisk needed as without them it is text-in-text search.
- EI2KO/p is alert with */p .
Alerts all /P stations, too Add part or complete suffix to specify
- i used today MyAlert, LocAlert and CallAlert together.
They should work in priority order mentioned in PDF (just one alerts per period)
~ CQ NO EU RZ3DX".
That is non standard way to call CQ using free text messages. Program can not understand all glorious ideas users may have !
Too many exceptions. I have noticed same kind of result sometimes.
- maybe someone want to filter for VK*,ZL*
Yep. call can combined, but adding also text search to it is another story. Having too many alerts is confusing, I think.
-all alerts are enabled via a checkbox (set a small hook).
Yep. I was thinking of that once I got it ready. Check boxes do not fit to text/ćall alerts way that they are now presented.
Buttons fit to MY/ALL/LOC however as well as check boxes. Maybe I change all to buttons. I have to test what it looks like.
--
Saku
OH1KH
--
Saku
OH1KH
one small hint.
all alerts are enabled via a checkbox (set a small hook). only Call/Text are enabled via an "alert-button which gets green font-color". maybe the gui should use the same standard for activating an alert.
in the first minutes of the test it was a little bit confusing.
bye DL7OAP, Andy
Hi Andy!
Fixed the PDF and also the layout of alert settings.
Tried also to make a bit more clever check for users using "innovative" CQs with free text messages. This does catch them all. Nothing ever will.
Find (127) from usual address.
--
Saku
OH1KH
--
Saku
OH1KH
Hi Saku,
thanks. 127 is now installed. i will give feedback in the next days.
55&73 de DL7OAP, Andy
Hi,
did work now several hours yesterday and today with the 127 dev-version and i found no errors.
it works fine.
no wrong alerts.
it helps me to work VK9VKL (Christmas Island) and RI1ANC (Antartica) today :-)
Thanks, DL7OAP
Hi !
Some more test work for coming weekend.
Try 128 and please give comments.
--
Saku
OH1KH
--
Saku
OH1KH
Hi Saku,
just using the new version dev 128 :-) with wsjtx 1.8.0 (now the official version, no release candidate anymore).
the jumping of some rare stations i recognize, too. Will test your new function.
in ft8 you have a chance in a pileup as a very weak station, if you send split in a free "room" on the waterfall spectrum.
RI1ANC i was working with this.
i will give a feedback in the next days .
Andreas, DL7OAP
first hour on band with dev-128 this evening works fine. i did test the follow-function and retest the call-filter on 40m and 80m. working south korea (alert!) and some european stations.
Hi Andy!
Yes. Split is the only way to get qsos with low power/small antennas.
It has been hard before, but now "Hold TX frequency" finally makes it easy.
If just people would understand that "the channel" or "working frequency" is the whole waterfall area 2,5 - 5 kHz depending on rig's filters, and you can make qso on other (audio) frequency, inside bandwidth, than your qso partner has.
Very often strong stations make sideband qrm with overloading audio, or just having so high signal that receiver front end will produce cross modulation results over the whole badwidth.
Split does not remove them, but may help in some cases when DX is jumping after callers. So every caller can choose the best spot and wait for getting qso there. For that the "Follow" makes it easier to see where DX is working in each period.
Unfortunately wsjt-UDP does not allow to start qso from other received messages than CQ or QRZ, so those "Follow"-lines can not be used to initiate own TX it have to be done from wsjt-x main window.
Next step in FT8 story seems now to be creation of DX version with maximum qso throughput. There are some notes of that project found from wsjt pages at sourceforge.
That is interesting and hopefully gives possibility also for low power/antenna stations when hunting rare DXs.
--
Saku
OH1KH
--
Saku
OH1KH
Hi, did a longer testing for dev 128. it works fine.
the dev 130 i was testing about 1-2 hours works fine, too. also did test the "Follow-Line gets red"-Feature. Its working here out of the box.
Thanks Andy, DL7OAP
Many thanks for testing!
Nice to have help as the coding takes it's own time and it is away from testing.
I have done some changes again. Seems that coding is more fun than working ;).
I do release 131 as soon as I have done the pre-testing by my self.
Somehow these ideas grow always after I have just decided that "this is the final version".
--
Saku
OH1KH
--
Saku
OH1KH
hi, dev 130 was running here now over 5 hours (2 hours it was just running and i was not in the shack, but it didn't crash in this time :-) ). And 3 hours i was operating on 20m and 40m. Did get QSOs with ZL and VK because of the nice alert function :-) so now bugs found during these period.
55&73 de DL7OAP