ullix

You did not provide much info. I can only guess that you missed activation of your device? Read the chapter Configuration of GeigerLog in the GeigerLog manual. Also: please post in the appropriate forum! You posted in the Gamma Spectra forum, which surely is not the place for questions on Audio counters. I will delete your post in a few days. If you still have questions, post again at a better place!

A known problem which came up with Py3.14. It is fixed in latest GeigerLog pre-releases. Download the latest pre-release from here: https://sourceforge.net/p/geigerlog/discussion/devel2/ Currently the latest is pre08.

The main reason for this pre-release is the support of the new GMC-800Re2.00. This is not only a new firmware, but also new hardware, despite an unchanged name! This hardware makes it incompatible with previous versions of GeigerLog! And, by the way, makes it also incompatible with RadPro - what a coincidence that competing software can not be installed any more :-(( GeigerLog needed modest changes, but then faces some new problems: GeigerLog was too fast (!) for this latest, greatest microprocessor,...

The main reason for this pre-release is the support of the new GMC-800Re2.00. This is not only a new firmware, but also new hardware, despite an unchanged name! This hardware makes it incompatible with previous versions of GeigerLog! And, by the way, makes it also incompatible with RadPro - what a coincidence that competing software can not be installed any more :-(( GeigerLog needed modest changes, but then faces some new problems: GeigerLog was too fast (!) for this latest, greatest microprocessor,...

The main reason for this pre-release is the support of the new GMC-800Re2.00. This is not only a new firmware, but also new hardware, despite an unchanged name! This hardware makes it incompatible with previous versions of GeigerLog! And, by the way, makes it also incompatible with RadPro - what a coincidence that competing software can not be installed any more :-(( GeigerLog needed modest changes, but then faces some new problems: GeigerLog was too fast (!) for this latest, greatest microprocessor,...

Well. I conclude that everything is working as it should?

My OS used for GeigerLog is Ubuntu 25.04. Its default Python is 3.13.3. I have now added Python3.14.0 by installing from source code. Py3.14 allows a successful GeigerLog setupfor all LATEST pips, with the exception of playsound. Audio playing is a seemingly simple tasks, and there are multiple tools for it. Unfortunately, they all seem to have a flaw somewhere. playsound 1.3 does not work on Window, but 1.2.2 does. But 1.2.2 now does not play on Py3.14, and playsound 1.3 cannot be installed on Py3.14....

I tested updating all pip-stuff to their latest version. In my case, using Python3.13, it works. Your-mileage-may-vary! To do this is simple: delete all __venv * files inside the GeigerLog working directory. Then start GL with this command: ./GeigerLog.sh setup latest then start GL with: ./GeigerLog.sh -d If it works, then the "-d" option should result in a file geigerlog.proglog.develin the data directory. Please, post this file.