Developer mode - Revision history

Bcmwiki: Consistency pass 2: airflow range via Configuration, multi-wavelength as in-development, ESP32/Pi CSV filename split, legacy sensor wording

2026-06-08T18:47:40Z

Consistency pass 2: airflow range via Configuration, multi-wavelength as in-development, ESP32/Pi CSV filename split, legacy sensor wording

← Older revision		Revision as of 18:47, 8 June 2026
Line 185:		Line 185:
	* '''Optics/ADC:''' Pi builds use ADS8344E hardware (legacy units may use MCP342X); ESP32 builds use ADS1220-based optical acquisition.		* '''Optics/ADC:''' Pi builds use ADS8344E hardware (legacy units may use MCP342X); ESP32 builds use ADS1220-based optical acquisition.
	* '''Firmware updates:''' bcMeter (DIY) builds may update through OS/GitHub release workflows, while ESP32 devices use OTA firmware images.		* '''Firmware updates:''' bcMeter (DIY) builds may update through OS/GitHub release workflows, while ESP32 devices use OTA firmware images.
	* '''Sensors:''' ~~bcMeter (~~DIY) builds ~~may~~ expose DS18B20 ~~or other prototype sensors that are~~ not present on ~~every ESP32 unit~~.		* '''Sensors:''' Some legacy or prototype DIY builds expose additional sensors (e.g. DS18B20 1-Wire temperature) not present on standard units.

Bcmwiki: Consistency pass: multi-wavelength in-development, bcmeter-pi link, anchor/Flask/V2 fixes, airflow & ATN clarifications

2026-06-08T18:43:41Z

Consistency pass: multi-wavelength in-development, bcmeter-pi link, anchor/Flask/V2 fixes, airflow & ATN clarifications

← Older revision		Revision as of 18:43, 8 June 2026
Line 182:		Line 182:
	The <code>bcmeter-dev</code> Raspberry Pi codebase powers '''bcMeter (DIY)''' builds, but it differs from the ESP32 firmware in the assembled instruments. Device-specific differences should be treated as implementation details of the same function:		The <code>bcmeter-dev</code> Raspberry Pi codebase powers '''bcMeter (DIY)''' builds, but it differs from the ESP32 firmware in the assembled instruments. Device-specific differences should be treated as implementation details of the same function:

	* '''Networking:''' Raspberry Pi builds ~~may~~ use ~~Flask~~ and NetworkManager, while ESP32 builds use the embedded web server and ESP-IDF WiFi stack.		* '''Networking:''' Raspberry Pi builds use FastAPI/uvicorn and NetworkManager, while ESP32 builds use the embedded web server and ESP-IDF WiFi stack.
	* '''Optics/ADC:''' Pi builds may ~~reference ADS8344E or~~ MCP342X ~~hardware~~; ~~current~~ ESP32 V2 builds use ADS1220-based optical acquisition.		* '''Optics/ADC:''' Pi builds use ADS8344E hardware (legacy units may use MCP342X); ESP32 builds use ADS1220-based optical acquisition.
	* '''Firmware updates:''' bcMeter (DIY) builds may update through OS/GitHub release workflows, while ESP32 devices use OTA firmware images.		* '''Firmware updates:''' bcMeter (DIY) builds may update through OS/GitHub release workflows, while ESP32 devices use OTA firmware images.
	* '''Sensors:''' bcMeter (DIY) builds may expose DS18B20 or other prototype sensors that are not present on every ESP32 unit.		* '''Sensors:''' bcMeter (DIY) builds may expose DS18B20 or other prototype sensors that are not present on every ESP32 unit.

Bcmwiki: Reframe: bcMeter (DIY) / source-available

2026-06-08T10:35:03Z

Reframe: bcMeter (DIY) / source-available

← Older revision		Revision as of 10:35, 8 June 2026
Line 178:		Line 178:
	<blockquote style="background:#fff3cd;padding:8px 16px;border-radius:4px;">'''⚠ 12V Power Missing''' — The optical ADC is not detected. Optics and light sensors will not function. Pump and airflow control may be limited by hardware state.</blockquote>		<blockquote style="background:#fff3cd;padding:8px 16px;border-radius:4px;">'''⚠ 12V Power Missing''' — The optical ADC is not detected. Optics and light sensors will not function. Pump and airflow control may be limited by hardware state.</blockquote>

	=== ~~Development Device~~ Variants ===		=== Platform Variants (DIY / open line vs assembled instruments) ===

	The <code>bcmeter-dev</code> Raspberry Pi codebase ~~is useful for development and older prototypes~~, but it differs from the ESP32 ~~production~~ firmware. Device-specific differences should be treated as implementation details of the same function:		The <code>bcmeter-dev</code> Raspberry Pi codebase powers '''bcMeter (DIY)''' builds, but it differs from the ESP32 firmware in the assembled instruments. Device-specific differences should be treated as implementation details of the same function:

	* '''Networking:''' Raspberry Pi builds may use Flask and NetworkManager, while ESP32 builds use the embedded web server and ESP-IDF WiFi stack.		* '''Networking:''' Raspberry Pi builds may use Flask and NetworkManager, while ESP32 builds use the embedded web server and ESP-IDF WiFi stack.
	* '''Optics/ADC:''' Pi builds may reference ADS8344E or MCP342X hardware; current ESP32 V2 builds use ADS1220-based optical acquisition.		* '''Optics/ADC:''' Pi builds may reference ADS8344E or MCP342X hardware; current ESP32 V2 builds use ADS1220-based optical acquisition.
	* '''Firmware updates:''' ~~Pi development devices~~ may update through OS/GitHub release workflows, while ESP32 devices use OTA firmware images.		* '''Firmware updates:''' bcMeter (DIY) builds may update through OS/GitHub release workflows, while ESP32 devices use OTA firmware images.
	* '''Sensors:''' ~~Development devices~~ may expose DS18B20 or other prototype sensors that are not present on every ESP32 unit.		* '''Sensors:''' bcMeter (DIY) builds may expose DS18B20 or other prototype sensors that are not present on every ESP32 unit.

Bcmwiki: Polish English manual/wiki wording

2026-05-02T20:15:57Z

Polish English manual/wiki wording

Bcmwiki: Update bcMeter ESP32 interface documentation and terminology (May 2026)

2026-05-02T19:58:43Z

Update bcMeter ESP32 interface documentation and terminology (May 2026)

Show changes

Bcmwiki: Update dev mode to match actual bcmeter-dev config.py: restructured sections (calibration vs optical), added all actual parameters with correct defaults, added CLI debug mode docs, added AFC slope_gain, hardware swap_channels/spi_vref/display params

2026-03-31T18:25:20Z

Update dev mode to match actual bcmeter-dev config.py: restructured sections (calibration vs optical), added all actual parameters with correct defaults, added CLI debug mode docs, added AFC slope_gain, hardware swap_channels/spi_vref/display params

Show changes

Bcmwiki: Add Identify Device section (Morse code LED blink)

2026-03-26T14:22:46Z

Add Identify Device section (Morse code LED blink)

← Older revision		Revision as of 14:22, 26 March 2026
Line 112:		Line 112:
	* '''Skip for now:''' Hides for 2 days (stored in localStorage + cookie).		* '''Skip for now:''' Hides for 2 days (stored in localStorage + cookie).
	* '''Don't show again:''' Permanently disables onboarding by writing <code>onboarding_done: true</code> to device config.		* '''Don't show again:''' Permanently disables onboarding by writing <code>onboarding_done: true</code> to device config.

			=== Identify Device ===

			The Developer tab includes an '''Identify Device''' button that blinks the status LED in a distinctive Morse code pattern (spelling "bcmeter") for 30 seconds. This helps visually locate a specific device when multiple units are deployed in the same area.

			* '''API call:''' <code>/api/control?action=identify</code>
			* '''Duration:''' 30 seconds
			* '''Pattern:''' Morse code at ~10 WPM (dot = 120 ms, dash = 360 ms)
			* '''LED reverts''' to its previous mode (idle, sampling, or error) after the pattern completes.

Bcmwiki: Update: V1/V2 naming, remove ESP32/Pi distinction

2026-03-08T13:21:07Z

Update: V1/V2 naming, remove ESP32/Pi distinction

← Older revision		Revision as of 13:21, 8 March 2026
Line 96:		Line 96:
	=== Development Build Detection ===		=== Development Build Detection ===

	When the device is running a development build ~~(the open-source [https://github.com/dahljo/bcmeter-dev bcmeter-dev] codebase)~~, the API returns <code>"env":"dev"</code> in the status response and a red banner appears at the top of the interface:		When the device is running a development build, the API returns <code>"env":"dev"</code> in the status response and a red banner appears at the top of the interface:

	<blockquote style="background:#dc3545;color:#fff;padding:8px 16px;border-radius:4px;">DEVELOPMENT BUILD — connected to dev backend</blockquote>		<blockquote style="background:#dc3545;color:#fff;padding:8px 16px;border-radius:4px;">DEVELOPMENT BUILD — connected to dev backend</blockquote>

	~~This indicates you are connected to the Python/FastAPI reference implementation rather than the ESP32 production firmware. Functionality is identical.~~

	=== 12V Power Warning ===		=== 12V Power Warning ===

	If the ~~ADS1220~~ optical ADC is not detected (because 12V power is missing), a warning modal appears:		If the optical ADC is not detected (because 12V power is missing), a warning modal appears:

	<blockquote style="background:#fff3cd;padding:8px 16px;border-radius:4px;">'''⚠ 12V Power Missing''' — The optical ADC is not detected. Optics and light sensors will not function. Pump and airflow control (5V) are unaffected.</blockquote>		<blockquote style="background:#fff3cd;padding:8px 16px;border-radius:4px;">'''⚠ 12V Power Missing''' — The optical ADC is not detected. Optics and light sensors will not function. Pump and airflow control (5V) are unaffected.</blockquote>

Bcmwiki: Wiki update: sync with manual and dev docs (2026-03)

2026-03-08T13:10:14Z

Wiki update: sync with manual and dev docs (2026-03)

New page

== Developer Mode ==

The bcMeter interface includes a hidden developer mode for advanced hardware tuning and diagnostics. '''Changes in developer mode affect hardware directly''' — only modify settings if you understand their impact.

=== Activating Developer Mode ===

# Open '''Settings''' (gear icon).
# Click on the '''device name''' text (next to "Configuration") '''7 times within 3 seconds'''.
# The name will change to show <code>[DEV]</code> in yellow.
# A new '''Developer''' tab appears in the settings panel.

Developer mode persists until the page is reloaded.

=== Developer Settings ===

The Developer tab exposes low-level configuration organized into sections:

==== Calibration (dev:calibration) ====

{| class="wikitable"
! Parameter !! Description !! Default
|-
| '''LED duty cycle (880nm)''' || Brightness of the 880nm IR LED (0–255) || Auto-set during calibration
|-
| '''LED duty cycle (520nm)''' || Brightness of the 520nm green LED || Auto-set
|-
| '''LED duty cycle (370nm)''' || Brightness of the 370nm UV LED || Auto-set
|-
| '''Calibration factor K (per channel)''' || Ratio Ref/Sen from last calibration || Auto-set
|-
| '''LED duty floor''' || Minimum duty before "no filter" is declared || 30
|}

==== Optical (dev:optical) ====

{| class="wikitable"
! Parameter !! Description !! Default
|-
| '''Sample spot diameter''' || Diameter of the filter area exposed to sample air (cm). Critical for absorption calculation. || 0.4 cm
|-
| '''Filter scattering factor''' || Correction factor for filter material light scattering || 1.39
|-
| '''Number of channels''' || Active wavelength channels (1–3) || 1 (880nm only)
|}

==== Pump (dev:pump) ====

{| class="wikitable"
! Parameter !! Description !! Default
|-
| '''Pump duty cycle''' || Base pump PWM speed (0–255) || 40
|-
| '''Min pump duty''' || Minimum duty to maintain airflow || 35
|-
| '''Max pump duty''' || Maximum pump speed limit || 255
|-
| '''Min airflow (mL)''' || Stall detection threshold || 70 mL/min
|-
| '''PWM frequency''' || Pump control frequency (Hz) || 40
|-
| '''Disable pump control''' || Manual mode — bypasses automatic pump management || false
|-
| '''Enable 12V output''' || Activate 12V auxiliary power rail || false
|}

==== Auto Flow Control (dev:afc) ====

{| class="wikitable"
! Parameter !! Description !! Default
|-
| '''AFC flow low''' || Minimum airflow when AFC is active || 0.05 L/min
|-
| '''AFC flow high''' || Maximum airflow when AFC is active || 0.5 L/min
|-
| '''AFC BC low/high''' || BC concentration thresholds for flow lookup table || Varies
|}

==== Hardware (dev:hardware) ====

{| class="wikitable"
! Parameter !! Description !! Default
|-
| '''is_ebcMeter''' || Enable direct emission mode (µg units instead of ng) || false
|-
| '''IoT enable''' || 4G/LTE modem available || false
|-
| '''Enable WiFi''' || WiFi connectivity available || true
|-
| '''Show undervoltage warning''' || Display warning when 12V rail not detected || true
|}

==== System (dev:system) ====

Internal system parameters. Modifying these may affect device stability.

=== Development Build Detection ===

When the device is running a development build (the open-source [https://github.com/dahljo/bcmeter-dev bcmeter-dev] codebase), the API returns <code>"env":"dev"</code> in the status response and a red banner appears at the top of the interface:

<blockquote style="background:#dc3545;color:#fff;padding:8px 16px;border-radius:4px;">DEVELOPMENT BUILD — connected to dev backend</blockquote>

This indicates you are connected to the Python/FastAPI reference implementation rather than the ESP32 production firmware. Functionality is identical.

=== 12V Power Warning ===

If the ADS1220 optical ADC is not detected (because 12V power is missing), a warning modal appears:

<blockquote style="background:#fff3cd;padding:8px 16px;border-radius:4px;">'''⚠ 12V Power Missing''' — The optical ADC is not detected. Optics and light sensors will not function. Pump and airflow control (5V) are unaffected.</blockquote>

=== Onboarding Skip Mechanism ===

The welcome/onboarding screen can be bypassed:

* '''Skip for now:''' Hides for 2 days (stored in localStorage + cookie).
* '''Don't show again:''' Permanently disables onboarding by writing <code>onboarding_done: true</code> to device config.

← Older revision		Revision as of 20:15, 2 May 2026
Line 1:		Line 1:
	== Developer Mode ==		== Developer Mode ==

	The bcMeter interface ~~includes~~ a hidden developer mode for ~~advanced~~ hardware tuning and diagnostics. '''Changes in developer mode affect hardware directly''' and can make measurements unusable when set incorrectly. Use it for support, development, ~~and~~ device-specific provisioning ~~only~~.		The bcMeter interface has a hidden developer mode for hardware tuning and diagnostics. '''Changes in developer mode affect hardware directly''' and can make measurements unusable when set incorrectly. Use it only for support, development, or device-specific provisioning.

	=== Activating Developer Mode ===		=== Activating Developer Mode ===
Line 18:		Line 18:
	<blockquote style="background:#fff3cd;padding:8px 16px;border-radius:4px;">Developer mode — changes affect hardware directly. Save only if you know what you are doing.</blockquote>		<blockquote style="background:#fff3cd;padding:8px 16px;border-radius:4px;">Developer mode — changes affect hardware directly. Save only if you know what you are doing.</blockquote>

	Settings are grouped by namespace. ~~Values~~ below ~~reflect~~ the current ESP32 firmware defaults in <code>cfgstore.cpp</code>.		Settings are grouped by namespace. The values below match the current ESP32 firmware defaults in <code>cfgstore.cpp</code>.

	==== BC Smoothing Algorithm ====		==== BC Smoothing Algorithm ====

	The first control selects the ~~real-time~~ BC smoothing algorithm. This setting is stored as <code>bc_filter</code>.		The first control selects the BC smoothing algorithm. This setting is stored as <code>bc_filter</code>.

	{\| class="wikitable"		{\| class="wikitable"
Line 141:		Line 141:
	\| <code>use_display</code> \|\| Device has an attached display. \|\| false		\| <code>use_display</code> \|\| Device has an attached display. \|\| false
	\|-		\|-
	\| <code>email_service_password</code> \|\| Mail service password for DIY/development devices. Provisioned devices normally already have this ~~configured~~. \|\| email_service_password		\| <code>email_service_password</code> \|\| Mail service password for DIY/development devices. Provisioned devices normally already have this set. \|\| email_service_password
	\|-		\|-
	\| <code>onboarding_step_one</code> \|\| Phase 1 onboarding complete: contact email and WiFi setup. \|\| false		\| <code>onboarding_step_one</code> \|\| Phase 1 onboarding complete: contact email and WiFi setup. \|\| false
Line 164:		Line 164:
	* <code>onboarding_email_sent</code>: welcome email has already been sent.		* <code>onboarding_email_sent</code>: welcome email has already been sent.

	The browser also uses local storage and cookies for temporary "Skip for now" behavior. "Don't show again" writes the ~~respective~~ onboarding step flag to the device ~~configuration~~.		The browser also uses local storage and cookies for temporary "Skip for now" behavior. "Don't show again" writes the matching onboarding step flag to the device.

	=== Development Build Detection ===		=== Development Build Detection ===