Memory Manager

Hello dev team,

My station.
Radio - IC-705
Platform - Windows 10 22H2
Current App version - v2.03

Questions regarding the memory manager panel.

I have noticed when testing the export function of my memories in the radio, the export only save the data from the selected group.

If i needed to export all memory data, then I would need to select each group, that holds memory data and save multiple files .

Also on the memory panel, I have tried the scan button with my radio and will only initiate a stop scan function if radio is scanning but not a start scan function.

Could the VFO / Memory be placed on the main panel, as they more of primary use secondary function.

Cheers
Peter VK4PI / VK4QRP

I’m also using the Memories functionality (of wfview 2.03 connected to wfserver 2.03 - compiled today) with my Icom IC-705 and have an issue with it:

I’ve configured the following memories - the first groups are separated per band:

When opening the memories window it auto loads “Group 00” which works flawlessly:

When I then select “Group 02” it seems to mix up the entries between the groups.
I’ve marked the unwanted entries with red - watch out for the wrong “num” values and “freq” items…

Any ideas what’s going wrong?
Should I provide some additional info?

Best,
Lukas OE3LRT

Sorry for sort of hijacking the topic but it seems that I’m not able to post a new topic…

Thanks for the report, I will look into it.

Phil

Hi Lucas.

I have tested with my IC705 and I can’t get replicate your issue, can you look in the log to see if any error messages appear?

It may be something specific to your setup so I might need an export of your memories to be able to fully test.

Phil

Hi Phil,

Thanks for the quick response!

Here you are - there are some entries in the log like “Column “Tn Mode” Invalid data received: 7”:

20250116 wfview_memories_log_01_edt.txt (19.2 KB)

Here you can find a shortened export (from the CS-705 software) of the first 3 memory groups (rename to csv):

20250116 wfview_memories_edt.csv.txt (5.0 KB)

Lukas

Ah the log explains what is happening. It is receiving an invalid tone mode for those memory locations. (7) according to the manual, this value can only be between 0 and 3.

In case the entry got corrupted in transit, the memory manager will request it again. Unfortunately, it looks like I made an error in the re-request code, and it is requesting the entry for memory group 0.

I assume you have previously managed this with the Icom memory manager, and it looks like that sets an invalid value, which explains why I don’t see the same issue.

I can easily work around this issue (and will fix the re-request code to make sure it gets the correct group), although if there is the possibility of receiving an invalid value from the radio, I may just ignore those and set them to default.

One more test, could you enable debug mode in the log and load the memories for group 2 again please? This will dump the actual data received from the rig so I can verify that it isn’t an error in the memory manager code.

Phil

1 Like

Hi Phil,

Yes you’re right: I previously used the Icom software CS-705 (Version 1.21) to initially load and configure the memories.

I’ve also created a log with debug enabled:

wfview_memories_log.txt (173.4 KB)

Regarding the value I had a look into the CI-V Reference Guide (https://www.icomjapan.com/support/manual/3064/) and it seems that “7” is not corrupted but a valid value (at least for the IC-705):

I’ve set the “Tone” values of my memories to either nothing, “TONE” or “TONE(T)/TSQL(R)” so I would expect either “00”, “01” or “09”:

I don’t know where the “07” comes from :wink:

Lukas

1 Like

That looks like a typical Icom documentation issue, as the memory function says this:

I can add those other options though.