Search found 26 matches

by HI8SMX
22 Jan 2020, 11:03
Forum: General discussions
Topic: JTalert and Log4OM version 2
Replies: 42
Views: 1904

Re: JTalert and Log4OM version 2

New JTAlert beta here: https://hamapps.groups.io/g/Support/message/27318 This beta is working for me nicely, even when running Wsjtx with SliceMaster, one instance or two instances. 73, Santiago Santiago, When you get the prompt to save the QSO (if you use that option) do you then get an error or w...
by HI8SMX
22 Jan 2020, 01:04
Forum: General discussions
Topic: JTalert and Log4OM version 2
Replies: 42
Views: 1904

Re: JTalert and Log4OM version 2

va3vf wrote:
22 Jan 2020, 00:50
New JTAlert beta here:

https://hamapps.groups.io/g/Support/message/27318
This beta is working for me nicely, even when running Wsjtx with SliceMaster, one instance or two instances.

73, Santiago
by HI8SMX
21 Jan 2020, 18:43
Forum: User support
Topic: Callsign look with WSJT-X
Replies: 56
Views: 857

Re: Callsign look with WSJT-X

I would not go to the extent of calling this issue a screw up, there are certain operations and certain operators with particular needs that couldn't be addressed them all in a single release. The key is to identify upgrades and features and work on them I, can perfectly wait for further development...
by HI8SMX
21 Jan 2020, 02:29
Forum: User support
Topic: Callsign look with WSJT-X
Replies: 56
Views: 857

Re: Callsign look with WSJT-X

In the JT Alert forum, Laurie mentioned that probably the reason second instances of WSJTX are not sending dx call info is because of the name of the second instance (-rig), apparently Log4Om is not recognizing anything but WSJTX in the name. Probably that's the same reason why with Slicemaster it d...
by HI8SMX
20 Jan 2020, 14:38
Forum: General discussions
Topic: JTalert and Log4OM version 2
Replies: 42
Views: 1904

Re: JTalert and Log4OM version 2

All who are having trouble getting the DX Call info from WSJTx or JTDX to populate the Callsign field in Log4OM V2... Try closing JTAlert, then retry. If the call sign from WSJTx or JTDX then populates the callsign field, then JTAlert is blocking the UDP message. Cure: 1. Set up in JTAlert (either ...
by HI8SMX
20 Jan 2020, 14:08
Forum: User support
Topic: Callsign look with WSJT-X
Replies: 56
Views: 857

Re: Callsign look with WSJT-X

Hi David, I understand the issue. The DX call field from WSJTx is not making it into Log4OM V2 Callsign field. Your settings look correct, so its something else blocking the UDP messages. I have the same settings and it is working fine here. Are you using OmniRig? If so, you need to be running both...
by HI8SMX
18 Jan 2020, 13:11
Forum: Error reports
Topic: Flex Multiple Slices + Omnirig
Replies: 33
Views: 406

Re: Flex Multiple Slices + Omnirig

IW3HMH wrote:
18 Jan 2020, 08:11
I'm preparing a new test version with some additional log info that could help us making the situation clear.
I'll advise when ready
Thanks for the help and hard work. I’m hoping to take advantage of both worlds (NG Log4OM and Flex).

73 de HI8SMX
by HI8SMX
17 Jan 2020, 19:46
Forum: Error reports
Topic: Flex Multiple Slices + Omnirig
Replies: 33
Views: 406

Re: Flex Multiple Slices + Omnirig

I just tried again, only with the non-working instance open and wrote k1JT on Wsjtx and the response I got was: 2020-01-17 19:27:00.1266 DEBUG: [#=z3kID5hlOqeRk$dRRNo3sYrI=][MoveNext] : ##### UDP MESSAGE RECEIVED ##### : ???? WSJT-X - Slice ??? FT8 K1JT -15 FT8 ? ? HI8SMX FK58AK???? ???? ???????? De...
by HI8SMX
17 Jan 2020, 18:30
Forum: Error reports
Topic: Flex Multiple Slices + Omnirig
Replies: 33
Views: 406

Re: Flex Multiple Slices + Omnirig

Here is what I could interpret from Log file (sorry but I honestly get lost in the file): 241 DEBUG: [#=zfRyP11wsrr3YnUM09HZJMYLQIw59Q8vheQ==][MoveNext] : INCOMING MESSAGE FROM SERVICE: DX CALL: ???? WSJT-X 2.1.2 0068f9 2020-01-17 18:10:14.3974 DEBUG: [#=z3kID5hlOqeRk$dRRNo3sYrI=][MoveNext] : ##### ...
by HI8SMX
17 Jan 2020, 17:10
Forum: Error reports
Topic: Flex Multiple Slices + Omnirig
Replies: 33
Views: 406

Re: Flex Multiple Slices + Omnirig

EI2GLB wrote:
17 Jan 2020, 15:46
I have it set that way Terry

WSJT-X is on port 2334
Bot is on port 2333

Log4OM is set to listen to both,

I'm trying to find error's in the log file but it's not making any sense to me :?:
That’s the same way I’m doing it.