It would be nice to know whether there's any update on this. We've given up on Picolog 6 now and have written our own Python scripts that just write the data to csv files to reduce the CPU and memory usage, in order to reduce the probability of running into this data corruption issue. Of course, kno...

I agree with Martin, far better to have missing data than swapped channels, and missing data is also preferable to interpolated data which risks being misleading. And the comments about advertising features versus supplying something reliable are spot on - I'd even rather fiddle about logging the da...

I've had a look through the windows event logs and can't see anything that seems related to the channel swapping events, and in fact there's often nothing in the logs at a similar time to the channel swapping. I do hope that someone in Pico Tehcnology will focus some attention on this issue, it's al...

After noumerious tests I found the root cause of the channel mix-up: - The problem is not related to the Picolog version (in use: 6.1.17 and 6.1.18), nor is it related to exporting csv or pdf files, nor to RAM size or similar. PicoLog runs fine. - There is definitely an interference/incompatibility...

Second attempt to attach examples of Picolog plots when this happens.

We've been suffering with this problem for months too, using Picolog 1216 dataloggers and Picolog 6.1.18. It can happen with only one datalogger connected or with a few, and it can happen after only a few days or it can work for a few months before the channels swap. It can also affect a few channel...