quote:

---

Originally posted by ullix

The situation is rather complex, indeed.

The crux is that the firmware of GQ counters with WiFi does allow only the use of port=80. Unfortunately, running a webserver at this port (and any other port lower than port=1024) requires running as admin.

Thus GeigerLog would have to be permanently run as admin, which I find irresponsible! (I am not even sure it would work, there are many hurdles).

GeigerLog does already run http-WebServers: One is Monitor Server, which allows monitoring of GeigerLog e.g. by Smartphone, and the other is WiFiClient (when activated), which supports devices like a GMC-WiFi counter but only when the devices send to a port 1024 or higher (max is 65535).

So the only workaround I found was this hack of an Apache server. I am not sure that this hack also works on Windows, but I guess chances are good, unless Windows actively prohibits that.

You could also use anything else which translates port=80 to port >1023, like e.g. a Raspberry Pi running Apache.

Another way is to connect a Raspi by USB cable with a GMC counter, and then have the Raspi transfer the data by WiFi. The required software is already part of the GeigerLog package! The preferred method is the use of IoT - you could have the counter in Timbuktu, and read from your office.

The easiest solution would be an update of the firmware of the GMC counters, but I have never heard of GQ wanting to do that.

The best detailed explanation of what to do is still in the GeigerLog manual ...

---

quote:

---

Originally posted by simonlharrison

Hi ullix,

Thanks for your help! I'm still not able to properly stream data over WiFi.

---

geigerlog -dvw devel gmctesting

geigerlog.proglog

quote:

---

Originally posted by ihab17

quote:

---

Originally posted by simonlharrison

Hi ullix,

Thanks for your help! I'm still not able to properly stream data over WiFi.

---

No Apache is required for Windows devices.

Is your Wifi only 5.0 GHz? And is it WPA3? As far as I know, your counter can only connect to 2.4 GHz Wifi networks with WPA2 at max, so if your Wifi is using WPA3 only or 5.0 GHz, then your counter will not connect. In fact, for this reason, I had to enable my guest Wifi and set it to 2.4 GHz with WPA2

---

quote:

---

Originally posted by ullix

@Simon: what you did sounds all very reasonable. If Ihab's latest comments do not result in a solution, a deeper inspection may be needed.

I suggest to do this at my discussion site https://sourceforge.net/p/geigerlog/discussion/general/

Just create a new topic and attach a log file. To get this, start GeigerLog with

geigerlog -dvw devel gmctesting

let it run for a few minutes and stop. Attach the

geigerlog.proglog

file in GeigerLog's data directory to your new topic on Sourceforge.

Do always use the latest available version of GeigerLog. I recommend even the latest pre-release of GL-v1.5.0; you find those within the topics, latest one will be here: https://sourceforge.net/p/geigerlog/discussion/general/thread/beafedc7b1/?page=3. Search for an attachment of GeigerLog code.

---

quote:

---

Originally posted by simonlharrison



As for no apache for windows what webserver would you use to run ullix's php bandaid?

infrastructure-ssid

---

DataServer:
    A Python based webserver intended for running on a 'Raspberry Pi computer' (Raspi)
    serving data to GeigerLog as:
        - a 'GeigerLog WiFiServer Device' - when in the local (WiFi-)LAN
        - a 'GeigerLog IoT Device'        - using MQTT from a place anywhere in the world

    DataServer can act as either one or both at the same time.

    The Raspi manages any devices connected to it; it starts them, collects their data,
    prepares the data, and sends them by the desired means.

    Supported Hardware Devices for the Raspi, which can all be run simultaeously, are:

        GMC counter, any model          by USB connection
        ...