Differences

This shows you the differences between two versions of the page.

--- ffc:cm:api_i2c [2021/12/08 22:34] – 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====
-[[link|Here is a link]]\\
+Click here for the [[ffc:cm:api-osc|Laser Driver API Command List]]\\
-[[link|Here is a another]]\\
+Click here for the [[ffc:cm:quickstart| FFC-CM Quickstart Guide]]\\
 ====I2C interface====
@@ Line 13: / Line 13: @@
 Little Endian (least significant byte first) data format is used for multi-byte data types.
-The [[ffc:cm:api_ld|command API]] outlines the command set for an individual laser driver board.
+The [[ffc:cm:api-ld|command API]] outlines the command set for an individual laser driver board.
 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 [[ffc:cm:api_i2c|this section]]. When multiple laser driver boards are in the system, they are identified by the address which is determined by their position on the Pump Board.
+For Vescent products, each command is no longer than 8 bytes as outlined in the [[ffc:cm:api_i2c#I2C Format|I2C Format]] section. When multiple laser driver boards are in the system, they are identified by the address which is determined by their position on the Pump Board.
 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)