I suggest to host the PCB-layout on Github, too. This will allow much more users to participate than the FHEM forum. If EAGLE is used for layout the Cadlab.io Github app can be used to publish the layout and render diffs.

To be able to use it without WiFi

Other than for LGW it perhaps does not make sense here because usually there will be no server to plug it into that is outside where it rains :-)

Perhaps only for "factory reset" and so on, when the settings are junk.

I suggest to support the MQTT protocol with PubSubClient for maximum compatibility. See ESP32: Publishing messages to MQTT topic for example code.

Remove the "timerAlarmDisable(m_timer);" and add a callback that uses startCapture / stopCapture

Implement DS18B20 for temperature compensation

To allow evaluation of different sensor mounting angles, it would be great if we could add an "sensor mounting angle" field to the setup page. (and automaticall adapt the calculated speeds on the help page)
Where 0° = facing upward.
I could then dynamically adapt the FOV related parameters in the signal processing part.

"First and last bin-number for each bin-group (uint16 firstBin[32], uint16 lastBin[32])"

What shall get configured and how and where shall it be used?

The ADC IO-pin / channel should be configurable through the web-interface.
Set default IO to IO33.

Display status
Edit configuration
Reboot
...

Since bin0 denotes 0 Hz, and values greater than 255 are not allowed, we should add a check here or at least avoid writing such numbers to the NFS.

Possibilities:

1. ) as is (use dummy in FHEM)
2. ) like LGW (firmware provides tcp-port and module works like 36_LaCrosseGateway)

Advantages:

1. ) nothing else must get implemented

2. ) FHEM module can provide options (that can or should not be in the firmware) like

• OTA update
• calculations
• validations
• settings (like init commands in LGW)

Hi,

I compiled today the version V0.17.1 with arduino and encoundered obove mentioned problem.

It seems, that the old code in Tools.cpp does not work any more.

`String Tools::GetChipRevision() {
String result;

byte revision = (REG_READ(EFUSE_BLK0_RDATA3_REG) >> EFUSE_RD_CHIP_VER_RESERVE_S) && EFUSE_RD_CHIP_VER_RESERVE_V;
switch (revision) {
case 0:
result = "0 (2016.09)";
break;
case 1:
result = "1 (2017.02)";
break;
default:
result = String(revision) + "(unknown)";
break;
}

return result;
}`

replacing the string behind byte revision to

`String Tools::GetChipRevision() {
String result;

byte revision = (REG_READ(EFUSE_BLK0_RDATA3_REG) >> (EFUSE_CHIP_VER_REV1_S)&&EFUSE_CHIP_VER_REV1_V) ;
switch (revision) {
case 0:
result = "0 (2016.09)";
break;
case 1:
result = "1 (2017.02)";
break;
default:
result = String(revision) + "(unknown)";
break;
}

return result;
}`

fixed the problem.

Regards,
Andreas Gaßner

Should we stop capturing when OTA starts?

Initial content: the list of bins from 1 ... 255 with frequency and speed in m/s and km/h

Since access to the NVS seems to interfere with the ADC sampling timer ISR, we should stop capturing during NVS access.

Hi,

Where can I find instructions, PCB schemes and 3D models for this project?