Main Differences Between V0.x and V1

User-facing overview of the main differences between Koheron V0.x and V1 firmware.
Firmware V1 documentation · V1.0-rc54-2d701ce

Koheron products currently ship with firmware V0.x by default. Firmware V1 is under active development and is not publicly available yet.

Contact us if you would like early access or want to evaluate V1 firmware on your device.

Main differences between V0.x and V1

V1 is a new firmware generation. It is not a drop-in replacement for a V0.x configuration file or host integration. Use this page as an overview, then follow the V0.x to V1 Migration Guide for the upgrade procedure and the V1 command API for product-specific behavior.

Area V0.x V1
Saved configuration Existing settings may be present in EEPROM. V1 uses its own configuration layout. Re-enter and review settings after upgrade.
Startup configuration Product and firmware behavior varies. The CFG switch selects saved configuration or product defaults. An invalid, erased, or missing CRC leaves product defaults active.
TEC PID tuning PID error scaling and gain definitions vary by product. PID tuning uses temperature error in °C with kprop, tint, and tder.
Temperature stability CTL200 and HTC200 use a resistance-based stability tolerance; CTL300E has no equivalent setting. ttol uses °C on all supported boards.
Command writes Older scripts may rely on product-specific parsing and behavior. Arguments are validated strictly. A rejected write keeps the previous value and reports an error.
Saved-configuration response Older scripts may expect a text confirmation. save returns the saved configuration CRC; ecrc reports it later.
Errors Error layout can be product-specific. Errors use a 32-bit mask with common bits in positions 0 through 17. Use errlist to discover the connected product's complete layout.
Binary status No binary-status protocol. New in V1. Discover fields with fmtlist and use the active mask from fmt%.

What this means for an upgrade

  • Do not rely on V0.x saved settings being valid or loaded by V1. Start from V1 product defaults, then reapply only reviewed settings.
  • Do not copy legacy PID numeric values into V1 parameters. See TEC PID tuning migration before enabling temperature control.
  • Update host software to check command responses and errors, especially around configuration saving, binary status, and multiplexed UART use.
  • Keep outputs disabled while verifying the product identity, sensor readings, limits, and control settings. Enable the TEC with tecon or the laser with lason only after that review.

V1 behavior remains product-specific where hardware differs. Check the generated V1 command API for the connected product before using a setting in production.