Log4OM

Is there a way to set my Icom 7300’s clock to UTC from LOG4OM’s initialization? Like many 7300s, mine suffers from a dead clock battery that is not easily replaced. So every power on is Midnight, Jan 1. It would be so nice not to have to set the date and time every time I turn on the radio.

Alternatively, does anyone know of a small program that would do this? All it would need to do is grab the UTC date/time from the PC clock and send the appropriate codes to the appropriate USB port.

Thanks!
Peter, KD7MW

Simply NO. Log4OM is using 3rd party CAT software like Hamlib and/or Omnirig. I also don´t know
that setting up or ayctualize a internal clock in the TRX is a CAT feature. If so you may ask the HAMLIB
community or the Omnirig programmer.

By the way, CAT is different to any programming Software .... Means, if there is a programming SW
with what you can set the clock it not works with CAT commands. Which CAT commands are used
you may find in your transceivers manual.

kd7mw wrote: 09 May 2020, 05:02 Is there a way to set my Icom 7300’s clock to UTC from LOG4OM’s initialization? Like many 7300s, mine suffers from a dead clock battery that is not easily replaced. So every power on is Midnight, Jan 1. It would be so nice not to have to set the date and time every time I turn on the radio.

Alternatively, does anyone know of a small program that would do this? All it would need to do is grab the UTC date/time from the PC clock and send the appropriate codes to the appropriate USB port.

Thanks!
Peter, KD7MW

Peter,
This program will do it, for ease of use try the consul version right at the bottom of the page.

He also provides an excellent FREE memory manager for the IC7300, look in the software menu of the same page

Sorry we dont do anything but its not really within the scope of our software

Terry, thanks. But I don’t see a link to the program you’re describing. Please post it. Yes, a console mode version would be great—I can drop it into the CMD scripts I use to start Log4OM plus Fldigi or WSJTX and JTAlert.

73,
-Peter, KD7MW

kd7mw wrote: 09 May 2020, 07:46 Terry, thanks. But I don’t see a link to the program you’re describing. Please post it. Yes, a console mode version would be great—I can drop it into the CMD scripts I use to start Log4OM plus Fldigi or WSJTX and JTAlert.

73,
-Peter, KD7MW

Sorry Peter, had a senior moment! Here it is

https://kb3hha.cloppermillweather.org/I ... nager.html

See software menu for clock

Got it. Thanks! As for senior moments, no worries. I have those, too. It’s not fair. I’m only 26...with 40 years additional experience.

Terry or any others,
I searched and founf this thread to set the 7300 clock on startup of L4OM. Praise the LORD!!!

I tested it under the Command Prompt (W11) as ADMIN and it worked. This was the config: Set-7300Clock.exe -p COM3 -b 19200 -i -u

I added it to C:\Program Files (x86)\Log4OM NextGen\AutoStarts\ and went to Program Config> Software Config>AutoStart with the pramaters I wanted, enabled it and saved it. See screen shot below

It did not start although the log file shows it ran, here is the clip of the file
***
2024-09-09 23:40:23.9128 INFO: [dje_zJTRBJVFT64FYCFF9HV65UAFYPM88QHYSX3_ejd] : [UPDATE] Starting refresh of METAR data...
2024-09-09 23:40:24.0691 INFO: [dje_zGUN65TW2KQJHNCG5FGGKDPAL2FBA_ejd] : KLRO 092335Z AUTO 00000KT 9SM CLR 23/20 A3008 RMK AO2

2024-09-09 23:40:24.0847 INFO: [dje_zJTRBJVFT64FYCFF9HV65UAFYPM88QHYSX3_ejd] : [UPDATE] Refreshing METAR data updated successfully
2024-09-09 23:40:24.0847 INFO: * [dje_zJTRBJVFT64FYCFF9HV65UAFYPM88QHYSX3_ejd][171 ms] : [UPDATE] [END] Refreshing METAR data process completed

2024-09-09 23:40:24.1159 INFO: [dje_zZ6TU7566LE9B42TQ68LLZ_ejd] : Executing C:\Program Files (x86)\Log4OM NextGen\AutoStarts\Set-7300Clock.exe -p COM3 -b 19200 -i -u

2024-09-09 23:40:24.2723 INFO: [dje_zEZHKUG5Z9KLZ8ATKEVQYBPVB7T6BXKH8VSNHS7MX_ejd] : Hourly VOACAP calculation completed
2024-09-09 23:40:26.9820 INFO: [ClusterManagement] : hamalert.org:7300 Cluster Login completed
2024-09-09 23:40:27.0289 INFO: [ClusterManagement] : n8dxe.dxengineering.com:7373 Cluster Login completed
2024-09-09 23:40:27.0444 INFO: [ClusterManagement] : dxc.nc7j.com:7373 Cluster Login completed
2024-09-09 23:40:27.2006 INFO: [dje_zJTRBJVFT64FYCFF9HV65UAFYPM88QHYSX3_ejd] : [UPDATE] Starting refresh of METAR data...
2024-09-09 23:40:27.2162 INFO: [dje_zEA96V5G5B957Q67Q4KCHJ9LT24BA_ejd] : Starting remote control on port 2241
2024-09-09 23:40:27.2162 INFO: [dje_zUPE47LU5_ejd] : Starting TALK client
***

Any suggestions?

Probably the port was already in use by CAT control like Omnirig or Hamlib

The autostart is designed to start other software not send commands via a com port which might be in use already