Log to file doesn't work for serial connections

Hello,

Thank you for contacting un on that matter!

Quick tests to replicate this issue internally have been inconclusive so far, so I would like to verify what type of data source you use with RDM.

Best regards,

Doh! I had started a reply to say its happening on multiple machines (2021.2.18), using Local source.

However, I just upgraded from 2021.2.18 to 2021.2.20 and when checking the logging settings, the previously configured settings are now showing and enabled!

It looks like the log files have an exclusive lock. Explorer had a timestamp of 6:21pm and 0KB size files and it was 6:33pm. Since I was expecting logged data, I tried to open the log and Windows complains the file is open in RDM and doesn't let me view it. Now the data size is updated in Explorer and I can see the size change to 28KB. I try to copy the log so that I can view it, and it also gets a Windows message about it still being open in RDM. So it would be nice if there wasn't an exclusive lock on the file, or at least allow it to be copied and opened separately.

Oof, spoke too soon.

So in 2021.2.20 where its now logging serial, `Log overwrite mode` is stuck on Default and won't let me change to Append.

Edit: With the serial session open, if I right click on the Tab-Properties, then changing to Default to Append wouldn't stick. But I edited the session under "Local Data Source" and then when I right clicked on the tab and did properties, it was now showing Append. So If I try to change the setting in the tab, it doesn't take effect. If I change it in the Local Data Source, the change is immediately reflected in the tab. That is new behaviour from my understanding, where changes to saved sessions wouldn't change currently open tabs launched from those sessions.

Hello,

Thank you for your update! I will contact our IT team to create a test Serial Port entry as I don't have one available at the moment. Once I have that, I will be able to attempt to replicate the issue on my end to report it to our engineering team.

I will keep you updates as progress is made on the case!

Best regards,

Hello,

I'd like to verify something just to be sure. In the properties of your Serial Port entry, is the "Log mode" set to "Event" or "Printable output"? If it is set to "Event", does changing it for "Printable output" make the "Log overwrite mode" drop-down menu interactable?

Best regards,

Gabriel,

"Log mode" is set to "Printable output".

When set to "Event", "Log overwrite mode" is greyed out.

When I set to "Printable output", then the "Log overwrite mode" is interactive, but only saves changes from the Local Data Source session properties, not from the actively open session.

In other words, changing it from the tab doesn't save "Log overwrite mode". I need to edit the Local Data Source properties to have that setting take effect.

Hello,

Thank you for your response.

When you mention that 'In other words, changing it from the tab doesn't save "Log overwrite mode".', I believe this behavior is intended if I understand your description properly.

I'm told by our engineering team that the possibility to edit the log properties from the session's tab is only temporary, so it is normal that it does not stay saved after being applied. Like all other entry types, to properly edit a session's properties, you need to change the properties by editing the entry itself from the Navigation pane.

Just to verify if the behavior you are describing is intended as we suspect, I would be curious to see a screenshot of the location where you configure the log settings that don't get saved.

Best regards,