ffc:cm:api_i2c
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
ffc:cm:api_i2c [2021/12/08 22:01] – external edit 127.0.0.1 | ffc:cm:api_i2c [2022/03/29 17:17] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 5: | Line 5: | ||
====Links==== | ====Links==== | ||
- | [[link|Here is a link]]\\ | + | Click here for the [[ffc: |
- | [[link|Here is a another]]\\ | + | Click here for the [[ffc: |
====I2C interface==== | ====I2C interface==== | ||
Line 12: | Line 12: | ||
The Gen2 Laser Driver is compatable with I2C Fast Mode 400 kbit/s speed and uses 7 bit addressing with the address determined by the board’s installation position on the pump laser board.. | The Gen2 Laser Driver is compatable with I2C Fast Mode 400 kbit/s speed and uses 7 bit addressing with the address determined by the board’s installation position on the pump laser board.. | ||
Little Endian (least significant byte first) data format is used for multi-byte data types. | Little Endian (least significant byte first) data format is used for multi-byte data types. | ||
+ | |||
+ | The [[ffc: | ||
+ | I2C protocols use unique addresses for each device on the I2C bus allowing many devices to share the same two wires. | ||
+ | For Vescent products, each command is no longer than 8 bytes as outlined in the [[ffc: | ||
+ | The Command index byte referenced in the description of each command is the one that follows the address byte. | ||
+ | The address byte determines which board answers the command. The channel argument which follows the command index (second byte) determines if the command is for the temperature channel (0) or the laser driver current channel (1) | ||
+ | |||
+ | For example, the command '' | ||
====I2C Addresses==== | ====I2C Addresses==== |
ffc/cm/api_i2c.1639000887.txt.gz · Last modified: 2021/12/08 22:01 by 127.0.0.1