"Fusion" vs "API Codec" (PR49-35_NCD5500 TCP protocol)

Software
1

We are purchasing multiple PR49-35_NCD5500 to allow us to issue I2C read & write commands from a host PC (Linux running our C/C++ software) over TCP to several different sensors:

According to the page it has firmware v6 @ https://store.ncd.io/product/ethernet-to-i2c-converter/

The links to documentation eventually leads to two different articles:

  1. I2C Communications Quick Start Guide @ I2C Communications Quick Start Guide - NCD.io

  2. API Codec Quick Start Guide @ API Codec Quick Start Guide - NCD.io

Are these both correct ways to communicate with the PR49-35_NCD5500 per TCP protocol (packet format) to execute I2C reads & writes? Is the API Codec (with checksum) the preferred method?

Thanks!

Regards,
Steve

2

Just to add some further confusion: this is from the serial-to-i2C – but is it applicable to TCP as well?

This wraps I2C read/write in another single-byte header (“command header”) before wrapping in the API (“NCD”) format where the cmd header is:

0xBE → I2C Write
0xBF → I2C Read
0xC0 → I2C Write & Read (with delay between as an optimization)
0xC1 → I2C Bus Scan
0xAA → I2C Stop

…is this the correct protocol/format to use for TCP with the PR49-35_NCD5500?

Thanks again!

-Regards,
Steve