|
Re: Logger32's rotor + remoterig
Olivier F4FQH
if you have only one rotor, don’t allow rotor1 to be used. Maybe it could
interfere.
dont use hrd an logger at the same time, but i think you do.
No more ideas here for now.
73
Olivier
F4FQH
From: Steph,
F5NZY
Sent: Wednesday, October 16, 2019 8:23 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] Logger32's rotor +
remoterig Hi Olivier,
Done ; but it does not work!
73 de Steph, F5NZY
De :
hamlogger@groups.io <hamlogger@groups.io> De la part de Olivier F4FQH
Slt Steph,
I use G2800 with an ERC mini.
Try to uncheck DTR and RTS And go to band&mode edit and check if the rotor1 is set to 1 on each band you want to use.
Should work
73 Olivier F4FQH
From: Steph, F5NZY Sent: Wednesday, October 16, 2019 6:02 PM To: hamlogger@groups.io Subject: [hamlogger] Logger32's rotor + remoterig
Hello all,
|
|
|
|
Re: Logger32's rotor + remoterig
Steph, F5NZY <f5nzy75@...>
Do I need a CI-V connection, to work?
If it is the case, remotely, I do not have this possibility yet, coming soon.
73 de Steph, F5NZY
De : hamlogger@groups.io <hamlogger@groups.io> De la part de Steph, F5NZY via Groups.Io
Hi Olivier,
Done ; but it does not work!
73 de Steph, F5NZY
De : hamlogger@groups.io <hamlogger@groups.io> De la part de Olivier F4FQH
Slt Steph,
I use G2800 with an ERC mini.
Try to uncheck DTR and RTS And go to band&mode edit and check if the rotor1 is set to 1 on each band you want to use.
Should work
73 Olivier F4FQH
From: Steph, F5NZY Sent: Wednesday, October 16, 2019 6:02 PM Subject: [hamlogger] Logger32's rotor + remoterig
Hello all,
|
|
|
|
Re: Logger32's rotor + remoterig
Steph, F5NZY <f5nzy75@...>
Hi Olivier,
Done ; but it does not work!
73 de Steph, F5NZY
De : hamlogger@groups.io <hamlogger@groups.io> De la part de Olivier F4FQH
Slt Steph,
I use G2800 with an ERC mini.
Try to uncheck DTR and RTS And go to band&mode edit and check if the rotor1 is set to 1 on each band you want to use.
Should work
73 Olivier F4FQH
From: Steph, F5NZY Sent: Wednesday, October 16, 2019 6:02 PM Subject: [hamlogger] Logger32's rotor + remoterig
Hello all,
|
|
|
|
Re: Logger32's rotor + remoterig
Olivier F4FQH
Slt Steph,
I use G2800 with an ERC mini.
Try to uncheck DTR and RTS
And go to band&mode edit and check if the rotor1 is set to 1 on each
band you want to use.
Should work
73
Olivier
F4FQH
From: Steph,
F5NZY
Sent: Wednesday, October 16, 2019 6:02 PM
To: hamlogger@groups.io
Subject: [hamlogger] Logger32's rotor + remoterig Hello
all, I am trying to configure my rotor in Logger32, thru the port COM3, of my remoterig (RRC-1258MkIIs). Actually, for the moment, I use HRD ROTATOR, but I'd like to add the Bob's Program possibility. I disconnect HRD ROTATOR, I even close it, but nothing. I tried all the configurations possibilities (I think), checked the doc, but it does not connect the rotor. Any idea, pse? 73 de Steph, F5NZY
|
|
|
|
Logger32's rotor + remoterig
f5nzy75@...
Hello all,
I am trying to configure my rotor in Logger32, thru the port COM3, of my remoterig (RRC-1258MkIIs). Actually, for the moment, I use HRD ROTATOR, but I'd like to add the Bob's Program possibility. I disconnect HRD ROTATOR, I even close it, but nothing. I tried all the configurations possibilities (I think), checked the doc, but it does not connect the rotor. Any idea, pse? 73 de Steph, F5NZY
|
|
|
|
Re: Export UQF(.asc) file
ja1nlx
Bob We use "nationality" instead of "citizenship" Someone was born in New Zealand and has played rugby in Japanese team for many years. Then he acquired Japanese nationality. Some one was born in other country and has played in Japanese
team for several years. Then he acquired membership as Japanese national team. Someone's race are Japanese. 73
On 2019/10/15 23:05, Bob wrote:
--
73 de aki JA1NLX
|
|
|
|
Re: Export UQF(.asc) file
Bob
Aki, born Japanese, or granted citizenship? 73.
On October 14, 2019 at 8:50 PM ja1nlx <ayoshida0205@...> wrote:
|
|
|
|
Re: Export UQF(.asc) file
Bob
Changes made for the next auto-update. UQF? I don't even remember what the acronym stood for. I think it goes back to 198something when I wrote an Apple II logging program while in Singapore. Some Swedish stations needed an abbreviated export for QSO printing. Now, of course, we have ADIF which has assumed a life of its own. SeventyThree(s).
On October 14, 2019 at 7:37 PM Ken JN7FAH <jn7fah@...> wrote:
|
|
|
|
Re: Export UQF(.asc) file
Gerry VE6LB
Ever been near a Sumo match Bob? Macks NA rugby players look tiny. 73, LB
On 14/10/2019 18:50, ja1nlx wrote:
--
73, Gerry VE6LB ve6lb@... ve6lb.ve6hams.com
|
|
|
|
Re: Export UQF(.asc) file
ja1nlx
Bob It is true that almost all have Japanese nationality. They are actually Japanese. 73
On 2019/10/15 9:25, Bob wrote:
--
73 de aki JA1NLX
|
|
|
|
Re: Export UQF(.asc) file
Bob
Ken, I will look at this tomorrow, but while you wait, answer me this question ... I Googled this: How many of the Japanese rugby team are actually Japanese ... Google said this: Do you think maybe they're trying to avoid answering the question? SeventyThree(s).
On October 14, 2019 at 7:37 PM Ken JN7FAH <jn7fah@...> wrote:
|
|
|
|
Export UQF(.asc) file
Ken JN7FAH
Bob, I found bugs in [File] menu, Export Logs/Export UQF(.asc) file. As shown below, when I chose this menu the box showing "Including this end date" isn't the present date. Then, I pull down date selection window as shown below, it is apparent that, in this section, L32 refers the last two digits of system year for DAY and system day for YEAR. It is 8:00 in the local time 1 hour behind 2019-10-15 00:00 UTC. I think, you know why the present date of L32 is a day before UTC. Next, the extension of UQF exported file is not .asc, but it is .uqf as shown below. The file name should be "20191014.asc". This function is quite useful to export QSO records of a certain station. If possible, let me request to add callsign or country selection appears in Exporting ADIF(.adi) file section. 73 Ken JN7FAH ex JA0RYN, JA0RYN/7, DL/JA0RYN
|
|
|
|
Re: UDP Bandmap Highlight Worked Before
Bob
Art, there is a 'Calling me' BandMap. I have never tried/used it, but you may be able to reply to stations that do not show on the BandMap (if it filters stations previously worked) by clicking on the 'Calling me' BandMap. Have fun, and let you mouse do the talking. SeventyThree(s).
On October 12, 2019 at 6:11 PM Art - VE3UTT / W1AJT <W1AJT@...> wrote:
|
|
|
|
Re: UDP Bandmap Highlight Worked Before
Art - VE3UTT / W1AJT
Thanks to those who responded. I will see if I can bold the "X". I did not want to "Block Callsigns Worked Before" however, I might re-think that. I don't call those worked before but I do receive repeat calls and normally QSO them.
Thanks Again, Art - W1AJT / VE3UTT
|
|
|
|
Re: Problem
Bob
Two things - First point, the option to set WSJT/JTDX on-top must be configured. On the UDP BandMap Click START (or STOP). Click SETUP SHORTCUTS. At the bottom of the SETUP START MENUS check START WSJT/JTDX ON-TOP option. Click the APPLY button. If this option is checked, then starting WSJT/JTDX from Logger32 will send the command to WSJT/JTDX to be on-top. Second point, when Logger32 starts WSJT/JTDX (you will notice after four/five seconds that The caption of WSJT/JTDX changes to be WSJT/JTDX & LOGGER32. If/when you see this, you know Logger has successfully started WSJT/JTDX and is able to send commands to the main Window. First it sends a command to change the caption. Second it sends a command to disable the X (top right corner button), and third it sends a command to place the WSJT/JTDX window on-top. If WSJT/JTDX does as it is told, yay! If it doesn't, so sad. SeventyThree(s).
toggle quoted messageShow quoted text
On October 12, 2019 at 1:15 PM Dave Colliau <n8dc-8@...> wrote:
|
|
|
|
Problem
Dave Colliau
My friend is running win7 and he says even with the box checked for wsjt-x and jtdx to run on top wsjt-x keeps hiding if he clicks somewhere else in Logger 32.
I have win10 and its fine here ? Any ideas. Dave N8DC
|
|
|
|
Re: Error Message
Colin
OK, problem solved, I think. The offset frequency of 21141.72 was appearing in the logbook page but the band wasn't appearing. Changing the entry in the Band/Modes table from 21140 -21140 to 21140 - 21142 seems to have solved it. Thanks for pointing me in the right direction BoB. 73 Colin, G3PSM
On Sat, 12 Oct 2019 at 14:48, Bob <k4cy@...> wrote:
|
|
|
|
Re: Error Message
Bob
... the error message text should be: I see no band in your report. So, Logger32 didn't see 15M in the modified record and decided not to change the QSO as requested. SeventyThree(s).
On October 12, 2019 at 9:20 AM Colin <colin.g3psm@...> wrote:
|
|
|
|
Re: Error Message
Bob
... what were you attempting to do when the error occurred? It looks like you were attempting to modify a previously entered QSO in the Logbook. Before actually making the change, Logger32 checked that there was a callsign, a band, and a mode in the new record it was going to overwrite the existing. One of those three fields was missing. It's probably not a good idea to change the QSO with one of those three missing. Did you try again, and what happened? SeventyThree(s).
toggle quoted messageShow quoted text
On October 12, 2019 at 9:20 AM Colin <colin.g3psm@...> wrote:
|
|
|
|
Error Message
Colin
Hi all,
I have suddenly started getting the following error message, strangely enough when I started using FT4 on 21140 kHz. That might be coincidence though - "It's my fault, I'm getting old and forgetful I am about to reset the complex keys in the database and have temporarily lost track of data for your QSO with (whatever callsign) on FT4. dbBusy flag is set to false I have not modified your logbook. Please try this again." Thoughts please? 73 Colin, G3PSM
|
|
|
