How to Evaluate LED Therapy Device Software Quality and Update Policies
Our LED mask had a firmware bug. The timer displayed 20 minutes but delivered 23 minutes. A 15% dose error from a software bug. We’d tested the hardware extensively. We’d never tested the firmware. Here’s what we learned about LED device software quality.
Why Software Quality Matters
Treatment accuracy:
Timer controls dose delivery
A 1-minute error on a 10-minute treatment = 10% dose error
Intensity control affects output
Mode selection must be correct
Safety features:
Auto-shutoff relies on software
Over-temperature protection is firmware-controlled
Error detection and reporting
Patient safety depends on reliable software
User experience:
Button responsiveness
Display accuracy
Mode switching reliability
Battery indicator accuracy
Connectivity:
Bluetooth/WiFi reliability
App communication
Data logging accuracy
Remote control functionality
Common Firmware Issues
Timer inaccuracy:
Clock drift over time
Temperature-dependent oscillator
Software counting errors
Fix: Use crystal oscillator, calibrate in production
State machine errors:
Device gets stuck in wrong mode
Buttons don’t respond after mode change
Unexpected behavior during power cycling
Fix: Proper state machine design with timeout recovery
Memory corruption:
Settings lost after power cycle
Random mode changes
Corrupted treatment history
Fix: Checksum validation, wear-leveling EEPROM writes
Boot loader issues:
Device won’t start after failed update
Bricked device from interrupted firmware update
No recovery mode
Fix: Dual-bank bootloader with fallback
Power management bugs:
Battery indicator inaccurate
Device shuts down unexpectedly
Won’t charge properly
Fix: Calibrate battery gauge with actual discharge curves
Software Development Standards
IEC 62304 (Medical device software):
Required for medical device certification
Defines software lifecycle processes
Documentation requirements
Risk-based approach to testing
Key requirements:
Software development plan
Requirements specification
Architecture design
Unit testing
Integration testing
System testing
Release testing
Software classification:
Class A: No injury or damage possible
Class B: Non-serious injury possible
Class C: Death or serious injury possible
Most LED therapy devices: Class B
Testing Requirements
Unit testing:
Test each function independently
Boundary conditions
Error handling
Minimum 80% code coverage
Integration testing:
Test component interactions
Timer + display + driver integration
Button input + mode switching + LED output
Battery monitoring + auto-shutoff
System testing:
Full device behavior testing
All user scenarios covered
Edge cases (low battery, rapid button presses)
Environmental conditions
Regression testing:
Re-test after any software change
Automated test suite preferred
Verify bug fixes don’t break other features
Update Policy Considerations
Over-the-air (OTA) updates:
Convenient for users
Risk of bricking if interrupted
Requires robust bootloader
Security considerations
USB updates:
More controlled
User must take action
Lower risk of interruption
Requires USB port and PC software
No update capability:
Simplest approach
Bugs are permanent
No way to add features
Not acceptable for connected devices
Our policy:
OTA updates with dual-bank bootloader
Automatic rollback on failed update
User notification before update
Update history logged in device
What B2B Buyers Should Ask
1. What software development standard do you follow?
2. How is the firmware tested?
3. Can the firmware be updated?
4. What happens if a firmware update fails?
5. How do you handle software bug reports?
For LED device buyers, software quality is as important as hardware quality. Bugs can cause dose errors, safety failures, and poor user experience. Verify the software development process, not just the hardware specifications.
