Search found 31 matches
- 04 Dec 2016, 21:30
- Forum: User Support
- Topic: JT 65 logging problem
- Replies: 12
- Views: 9700
Re: JT 65 logging problem
KC0EM, I rarely visit this forum, you need to post to the JTAlert support group (see link, top of HamApps.com) to get some assistance, it is the official channel for JTAlert support. There are many Log4OM/JTAlert users there that can help if I am unavailable to answer your message in a timely manner...
- 21 Sep 2016, 20:26
- Forum: User Support
- Topic: Log4OM + JTAlert + WSJT-X = errors + double logs
- Replies: 6
- Views: 5230
Re: Log4OM + JTAlert + WSJT-X = errors + double logs
As JTAlert/WSJT-X only accesses your Log4om database (With or without Log4OM running) it would seem the issue is with the other programs, have you made this enquiry to them? Terry, Your wrong. JTAlert does not access the Log4OM log directly for writing and never has. JTAlert uses the Log4OM logging...
- 12 Sep 2016, 21:39
- Forum: User Support
- Topic: Sudden error message
- Replies: 3
- Views: 2746
Re: Sudden error message
If the QSO is getting logged correctly, but JTAlert is unable to confirm that the QSO was logged, which is done via a direct read of the log file, suggests that you don't have JTAlert configured with the correct Log4OM log file path. Logging is done via UDP, so doesn't need to know the log file path...
- 27 May 2016, 07:41
- Forum: User Support
- Topic: FREQUENCY ERROR
- Replies: 4
- Views: 2787
Re: FREQUENCY ERROR
Phil, Since your looking at differences in what HB9HQX is logging and what Log4OM is recording, you should raise this issue with the HB9HQX author. Your mention of JTAlert in your original post led me to think that JTAlert was doing the logging. Since it appears that HB9HQX is doing the logging, I c...
- 27 May 2016, 07:38
- Forum: Software Integration
- Topic: UDP Logging strips carriage returns from multiline Address
- Replies: 12
- Views: 11516
Re: UDP Logging strips carriage returns from multiline Address
Examining the Communicator Log file, I see the data sent, including the Carriage Returns and Line feeds in the multi-line address field. Double-checking, I examined the file in a hex editor and the Carriage Returns are present. I performed two tests, first sending the data as a string and the second...
- 26 May 2016, 05:37
- Forum: Software Integration
- Topic: UDP Logging strips carriage returns from multiline Address
- Replies: 12
- Views: 11516
Re: UDP Logging strips carriage returns from multiline Address
Can a Dev confirm if this is a defect within Log4OM? If it is a defect, is there any idea on when a fix will be available? If it is not a defect, what is the correct method of logging (via the API) multi-line data to avoid "Carriage Returns" being stripped from the data before being writte...
- 26 May 2016, 05:32
- Forum: User Support
- Topic: FREQUENCY ERROR
- Replies: 4
- Views: 2787
Re: FREQUENCY ERROR
Phil,
Are you saying that the frequency logged by JTAlert to Log4OM is wrong? If so, can you give an example of the value being logged and the value you expected to be logged.
de Laurie, VK3AMA
(JTAlert Author)
Are you saying that the frequency logged by JTAlert to Log4OM is wrong? If so, can you give an example of the value being logged and the value you expected to be logged.
de Laurie, VK3AMA
(JTAlert Author)
- 19 May 2016, 01:52
- Forum: Software Integration
- Topic: UDP Logging strips carriage returns from multiline Address
- Replies: 12
- Views: 11516
Re: UDP Logging strips carriage returns from multiline Address
Further testing reveals that the multiline "NOTE" log field is also have the carriage returns stripped when logged via the UDP interface.
de Laurie, VK3AMA
de Laurie, VK3AMA
- 19 May 2016, 01:34
- Forum: Software Integration
- Topic: UDP Logging strips carriage returns from multiline Address
- Replies: 12
- Views: 11516
Re: UDP Logging strips carriage returns from multiline Address
Examining the Log4OMCommunicator_log file, I also note that it records the address with the carriage returns (0x0D) stripped, line feeds (0x0A) remain. So the stripping is happening before the Communicator logfile is updated. My guess is the code responsible for either receiving the UDP packet or th...
- 17 May 2016, 19:15
- Forum: Software Integration
- Topic: UDP Logging strips carriage returns from multiline Address
- Replies: 12
- Views: 11516
Re: UDP Logging strips carriage returns from multiline Address
The UDP you're using is the one formerly used for HRD? I seem to recall that many Log4OM versions ago the UDP interface was referred to the HRD interface or something similar with HRD in the wording. I am using the inbound settings available via the Log4OM Communicator window. "UDP connection ...
