ffc:cm:api-osc
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
ffc:cm:api-osc [2021/12/08 22:10] – external edit 127.0.0.1 | ffc:cm:api-osc [2021/12/09 00:16] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 19: | Line 19: | ||
=====Implementation Instructions===== | =====Implementation Instructions===== | ||
- | Listed below is the command set for the Application Programming Interface (API) for the FFC-100. | + | Listed below is the command set for the Application Programming Interface (API) for the FFC-100. |
Computer communication to the FFC-100 occurs by first establishing a Serial COM port via the USB 2.0 physical interface. Computer communication should be platform independent, | Computer communication to the FFC-100 occurs by first establishing a Serial COM port via the USB 2.0 physical interface. Computer communication should be platform independent, | ||
- | ^ Baud Rate | + | ^ Baud Rate |
- | ^ Data Bits | + | ^ Data Bits |
- | ^ Parity | + | ^ Parity |
- | ^ Stop Bits | + | ^ Stop Bits |
- | ^ Flow Control | + | ^ Flow Control |
- | To perform an operation, an ASCII-based text message is first constructed from a command and its arguments, and then the message is transmitted to the FFC-100 through the COM port. The following rules apply: | + | To perform an operation, an ASCII-based text message is first constructed from a command and its arguments, and then the message is transmitted to the FFC-CM through the COM port. The following rules apply: |
- Syntax is // | - Syntax is // | ||
Line 41: | Line 41: | ||
- Changes effected by issuing a serial command from this API are not permanently stored in non-volatile memory until you issue a SAVE command. Configuration changes without the SAVE command will be lost with power cycling. The Save command stores the entire configuration and so several configuration changes can be implemented and then a single SAVE command could be issued. | - Changes effected by issuing a serial command from this API are not permanently stored in non-volatile memory until you issue a SAVE command. Configuration changes without the SAVE command will be lost with power cycling. The Save command stores the entire configuration and so several configuration changes can be implemented and then a single SAVE command could be issued. | ||
- | For most complete version of API, download the FFC-Serial API PDF from the [[fcc:100: | + | For most complete version of API, download the FFC-Serial API PDF from the [[ffc:cm:api-osc# |
ffc/cm/api-osc.1639001428.txt.gz · Last modified: 2021/12/08 22:10 by 127.0.0.1