Brad Morris

@ullix I've attached the log as requested.

@ullix I've been running v2.0.0pre03 constantly since my last post on the 18th without any issues whatsoever. On the Windows 11 Pro machine I've kept the cycle time at 1 second and get no failures. This is with a GMC-500+. On the Raspberry Pi 4b I've changed the cycle time to 2 seconds and get no failures. At 1 second I do get occasional failures as described above. This is with the GMC-800.

@ullix the background CPM is usually around 18 CPM +/- 10 CPM. I do get a really nice poisson distribution. Nearly perfect actually. I'm going to try changing the log cycle to 2 seconds and see if that makes any difference. Brad

@ullix, I wasn't able to repeat the issue with Quick Log, but I was with normal logging. I've attached the Log for your reference. I honestly don't see anything in the log to indicate an issue and of course I didn't capture the issue on the screen before I closed GeigerLog so I'm rerunning it again. Edit: Adding in the screenshot of the error.

@ullix, I wasn't able to repeat the issue with Quick Log, but I was with normal logging. I've attached the Log for your reference. I honestly don't see anything in the log to indicate an issue and of course I didn't capture the issue on the screen before I closed GeigerLog so I'm rerunning it again.

@ullix I'm not ignoring your question, I'm trying to recreate the issue that I reported. If I'm able to recreate it, I'll post the log.

@ullix good news. I've been running GeigerLog v2.0.0pre03 on the Raspberry Pi 4B for six days without any serious issues. I did have to change the rate of recordings to 5 seconds vs 1. At 1 second I was getting a failure every 5-10 reads. After changing to 5 seconds, it works like a champ and haven't had a single other issue. One thing I would like to request...actually re-request. I posted this in a 2022 feature request and that was: Saved graph elements a. graph color changes (e.g. if I change...

During the process of receiving and installing the latest firmware updates from GQ, they let me know something that seems to have solved the issue I was having with serial ports on my Windows machine. They let me know that there's a bug that causes issues when any COM port >10 is used. This issue also won't allow more than one GQ Geiger counter to be used at a time when their serial ports are >10. Once I changed the serial port of my GMC-500+ to COM3, GeigerLog started working as advertised. None...