Keyboard Shortcuts
Likes
- Hamlogger
- Messages
Search
Logger32_FT897
¿ªÔÆÌåÓý?
Hi,
?
Logger32 and Yeasu FT897
Radio settings ?
Thank you
?
73! Jiri OK2LI
? |
Re: Problems with Logger32, JTAlert plus Socat
Too many different pieces of software. Why not simply connect JTAlert by TCP to Logger32?
?
If you must use socat, then look at the Logger32 TCP event viewer window. It should be 'listening' (waiting for a connection. The LED at the bottom right should be amber). From what you describe (only one contact logged, then nothing)? My SWAG is that after the first contact is logged, socat is not disconnecting and therefor cannot reconnect to log a second contact. You will see in the Logger32 TCP event viewer that after the first contact is logged, the socket stays connected (the LED at the bottom right stays green).
?
If the Logger32 TCP socket is stuck with an open connection (anything other than an amber LED), then it is not necessary to shut down all the software and restart. Simply right click on the Logger32 TCP pane on the lower status bar. Close then re-open the socket. It will re-open 'listening'.
?
Or something like that. SeventyThree(s).
?
|
Problems with Logger32, JTAlert plus Socat
¿ªÔÆÌåÓýHello, Need some help. Using for more than a year the?program combination "Logger32", "JTAlert" and - thanks Prasad - "Socat" v 1.7.3.0-windows master. For me and my needs the most convenient program system. This system was working flawlessly until a week ago when all of a sudden the logging via "Socat" into "Logger32" had partly quitt. "Partly" because the very first QSO is getting logged as expected but nothing happens with the following contacts. Although those QSOs are still logged into the JTAlerts "Standard ADIF file" they don't show up in "Socat" and are therefore not transferred to "Logger32". The whole logging control system gets stuck. Very disappointing. To get rid of this situation I've to switch off all programs in use and start again by loading "Logger32", followed by "JTAlerts" "Auto-Start" feature starting "Socat", "WSJT-X" and "VE7CC". When all needed programs are running I'm able to make ONE qso. THIS only ONE is shown on "Socat" and gets transferred to "Logger32", for all the following contacts .... see the story above. Back to square one. To me it seems the frog is hidden somewhere in "Socat". When googling around I realized that there is a newer Socat-version 1.8.0.1 for Windows available. Maybe there is a helpful person who can give me a hand on that matter. OM Prasad maybe can make a comment on whether or not "Socat" could be the root of my problem and if an update to the newer Socat-version could help to overcome it.
73 and tnx in advance de Peter, OE3EPW AR? SK
Finally here my program config ... |
Re: Spots to control radio
That did it, thank you. On Mon, Nov 18, 2024 at 11:22?AM Bob via <k4cy=[email protected]> wrote:
|
Re: Spots to control radio
Look at the parallel logging configuration. There is an option there to reroute clicked-on DX Spots to the other PC. SeventyThree(s).
|
Spots to control radio
Several weeks ago, Logger32 lost the ability to send my radio to a dx spot frequency and to populate the entry window.? Rig control works fine and I can type a frequency in and the radio will go there.? But clicking on a DX spot doesn't do anything - the entry window flashes briefly but neither the frequency or the callsign show up.? This used to work fine and I haven't (knowingly) made any changes.? I have a second computer synced to provide backup logging - that computer will populate the entry window and the frequency shows for several seconds?(but this computer doesn't have rig control).? Looking through the manual and searching for this issue hasn't shown me anything to look at. Both computers are running the latest version and have updated several times.? Any suggestions are appreciated, thanks. Don VE6JY |
Re: Issue on v4.0.329 with the Quick QSL window
Alain, it IS painful. As I cannot define the added value in that venture I had to rollback to the previous version, too... Best regards, Alec ------ Wiadomo?? oryginalna ------
Nadawca "Bob via groups.io" <k4cy@...>
Do [email protected]; "Alain F5LMJ via groups.io" <f5lmj@...>
Data 17.11.2024 10:22:46
Temat Re: [hamlogger] Issue on v4.0.329 with the Quick QSL window
|
Re: Issue on v4.0.329 with the Quick QSL window
Yes, there were changes made that slow down the opening of the Quick QSL window, but no changes that slow down how long it takes to change whatever you wanted to change. And, the delay in opening the Quick QSL window is only the first time you open the window.
?
And why the delay? When opening the Quick QSL window you are jumping into the logbook database somewhere. Loggoer32 needs to find out exactly where you are and move the vertical scrollbar thumb (the slider on the scrollbar) to the correct position. Why do this? So that scrolling up/down works correctly.
?
To see the difference, on v4.0.328, Open the Quick QSL window on a QSO somewhere in the middle of your logbook. Now on the vertical scrollbar? click with the mouse to scroll up one row. Did it go up one row? I think not.
?
C'est la vie. SeventyThree(s).
?
|
Issue on v4.0.329 with the Quick QSL window
Since version v4.0.329 I have a problem with the Quick QSL window any update takes on this version very long time before applying and block any other action. On v4.0.328 the update is done instantly. So I need to rollback to 328
Does anyone have also this issue ? Is there any change in Quick QSL window between 328 and 329 ? ?
73, Alain F5LMJ ? |
Re: Rollback
Only the last 10 are kept. Anything older is automatically deleted. SeventyThree(s).
|
Rollback
¿ªÔÆÌåÓýHello, On my rollback window, I have 4.0.318 to 4.0.328
possibility. Is possible to go back to an earlier versionn (before 4.0.318), and if yes, how ? Tks for your help and your answer. 73's. Jean-Claude? F6HDH |
Something odd with Radio connection?
So,? just recently starting seeing L32 with an odd radio connection problem...
?
Radio is FTdx101D connected to L32 via a Microham Station Master box at 19200, N, 8, 1 and polling is set at 50mS, but slower poling makes no difference.
?
When I first start L32 from cold, I see that both the Radio 1 and Rotator 1 are connected fine, as indicated by the blue status on the taskbar, and also confirmed by the frequency showing correctly in the entry window.?
?
I wait until the cluster spots have populated the band monitor panels, then I click on a spot on the monitor panel. At that exact moment the "Radio 1" on the taskbar changes from Blue (connected) to Red (not connected).? I then have to manually make L32 re-connect to the radio via the setup > Radio menu.
?
All is then fine and dandy and I don't see the problem again during that run-time session. However, the same repeats every time I start L32. Some kind of timing/hand-shake issue maybe?
?
?Any clues on this issue please?
?
Steve G1XOW
? |
Re: CW Machine and FTdx10
My configuration, and it works perfectly?:-) CW machine ?->>?CONFIG? ->> flag SOFTWARE? Keyer setup (wait a moment)? SERIAL PORT choose the port com# STANDARD (not Enhanced) Flaggare? -->> flag Use PTT to switch to transmit? -->> flag CW Keying users RTS PTT, users DTR Flaggare? ->> flag Use dedicated serial port fo CW? ->> flag Use Radio command PTT override Best 73' de Gianni IK6CGO ------ Messaggio originale ------
Da "ja1nlx via groups.io" <ayoshida0205@...>
A "Hanlogger" <[email protected]>
Data 14/11/2024 07:36:24
Oggetto Re: [hamlogger] CW Machine and FTdx10
|
Re: CW Machine and FTdx10
Clark I do not know why PC keying does not work. However WinKeyer is better than software mode. I myself prefer WinKeyer. Mine is WinKeyMini by K1EL. Good luck 73 de aki JA1NLX
|
Re: CW Machine and FTdx10
Hello Aki,
?
I am sure I tried that and it did not work either.? So, I have given up trying to get CW Machine to send CW from my FTdx10 via software.? A local friend had a WinKeyer he was not using and let me borrow it.? After some work I managed to get it working just fine with CW Machine.
?
Thanks to you and Gary for trying to help me with this.? But by adding the WinKeyer, I can now use CW Machine with the FTdx10 just like I used to with my microKEYER and K3S.?
?
?
73, Clark, W8TN
? |
Re: CW Machine and FTdx10
Clark Try RTS keying instead of DTR keying. (Select RTS keying in your radio, check "CW keying use RTS,,," in CW machine) 73 de aki JA1NLX
|
Re: CW Machine Keyer setup
Thanks for the tip. Will give it a go tomorrow. On Wed, Nov 13, 2024 at 16:22, Bob via groups.io <k4cy@...> wrote:
|
Re: CW Machine and FTdx10
Hmmmmm, OK. Your PTT is working fine using the CAT commands, so it seems it's just the CW keying using the DTR line on 'standard' virtual serial port Com23 that's playing up. I don't know why - sorry - something to do with the setup of the virtual?port I guess, but how to diagnose & fix that is beyond me (at 5:30am anyway!). All I can suggest is to work carefully through the Yaesu instructions for the ?to be sure you have the current driver correctly installed.? That may involve de-installing the driver first, then re-installing it.? Or something. If you want to prove that the CW Machine is keying the DTR line as it should, I guess you'd need some software to monitor the virtual port line, or maybe you could temporarily change to a real serial port and put a scope or DMM on the DTR line of that port, looking for the level changes when CW is being sent (easier to see with? ? v e r y? ? ?s l o w? ? ?C W).?? 73? GL Gary? ?beater/tester &? Honor Roll &? checkerOn Thu, 14 Nov 2024 at 02:18, Clark Stewart via <w8tn=[email protected]> wrote:
|
Re: CW Machine Keyer setup
Assuming your Logger32 installations were doing a full install, and not simply copying files/folders from one computer to another. My SWAG is that the dysfunctional PC has a Windows component, that Logger32 uses, missing.
?
If you don't already have one, setup a desktop shortcut that starts Logger32. Now read section 34.4 (page 758) of the help file. You will then be able to start Logger32 in full debug mode and hopefully identify the exact source of your problem.
?
SeventyThree(s).
|