The controller communicates with the SX10509 via commands. The following table lists the commands and the data that is associated with each one:<\/p>\n\n\n\n
\n:: Transmit Buffer (Commands) ::\nCommandName CommandValue NextByte NextBytes\n Byte 0 Byte 1 Bytes 2...n\n-----------------------------------------------------------------\nIdle '00 \/ '80 Unused Unused\nWrite '01 \/ '81 bLength Data..\nRead '02 \/ '82 CumulativeOffset Unused\nServer '03 \/ '83 bLength Data..\nPort '04 \/ '84 4 bytes of floating point port number\nPath '05 \/ '85 bLength Data..\nContentType '06 \/ '86 bLength Data..\nDoGet '07 \/ '87 Unused Unused\nDoPost '08 \/ '88 Unused Unused\nGetID '09 \/ '89 Unused Unused\nGetGMT '0A \/ '8A Unused Unused\nGetIP '0B \/ '8B Unused Unused\n \n:: Receive Buffer (responses) ::\nCommandName CommandValue NextByte NextBytes\n Byte 0 Byte 1 Bytes 2...n\n-----------------------------------------------------------------\nIdle '00 \/ '80 Unused Unused\nToServer '01 \/ '81 Unused Unused\nFromServer '02 \/ '82 bLength Data..\nServer '03 \/ '83 Unused Unused\nPort '04 \/ '84 Unused Unused\nPath '05 \/ '85 Unused Unused\nContentType '06 \/ '86 Unused Unused\nDoGet '07 \/ '87 bLength* 4 bytes of floating point status code\nDoPost '08 \/ '88 bLength* 4 bytes of floating point status code\nGetID '09 \/ '89 bLength IDString..\nGetGMT '0A \/ '8A bLength GMTString..\nGetIP '0B \/ '8B IP IP,IP,IP\n\n* For DoGet and DoPost responses, the bLengthByte is the number of characters available \n for readout using subsequent Read commands<\/pre>\n\n\n\nTo send a command, first load up any data associated with it, and the
bLength<\/code> byte is required. Then, once all the data is ready, load the command byte itself.<\/p>\n\n\n\nThe SX10509 will ignore the data until the command byte is loaded. Once it sees a new command byte, it will execute the command. When it finishes executing the command it will return a matching command byte in the network receive data block. For most commands this will be nearly instantaneous, but for
DoGet<\/code> andDoPost<\/code> it may take several seconds.<\/p>\n\n\n\nBe sure to wait for the command byte response before sending the next command.<\/p>\n\n\n\n
As the Xwire data blocks are limited to 32 bytes, these commands may require several iterations to be fully completed:<\/p>\n\n\n\n
Write \n Read \n Server \n Path \n ContentType<\/pre>\n\n\n\nFor example, setting a path with more than 30 characters, like “
custom\/scripts\/mmi202\/poopump\/flow_monitor.php<\/code>“, must be done in two iterations.<\/p>\n\n\n\nBit 7 of the command byte may be toggled to indicate the next iteration is ready. Here’s an example:<\/p>\n\n\n\n
\n;Creating two versions of the Path command provides a simple way to toggle\nCMDkPathA EQU '05 ;Path command\nCMDkPathB EQU '85 ;(toggled version of the) Path command\n \n SetMem bTxByte1,0 ;set the length to zero to erase any existing path\n SetMem bTxByte0,CMDkPathA ;load the command\nWafDoPath1:\n YieldTask\n GoIfMNE bRxByte0,CMDkPathA,WafDoPath1 ;waf erase to complete\n \n LoadI 0 ;zero the index (this will be used as a length indicator)\n iiPrintText bTxByte2,\"custom\/scripts\/mmi202\/p\" ;store the first part of the path\n ItoX ;get the length\n Store bTxByte1 ;store the length of the first part\n SetMem bTxByte0,CMDkPathB ;load the path command (toggled version)\nWafDoPath2:\n YieldTask\n GoIfMNE bRxByte0,CMDkPathB,WafDoPath2 ;waf the SX10509 to save the first part\n \n LoadI 0 ;zero the index (this will be used as a length indicator)\n iiPrintText bTxByte2,\"oopump\/flow_monitor.php\" ;store the second part of the path\n ItoX ;get the length\n Store bTxByte1 ;store the length of the second part\n SetMem bTxByte0,CMDkPathA ;load the path command\nWafDoPath3:\n YieldTask\n GoIfMNE bRxByte0,CMDkPathA,WafDoPath3 ;waf the SX10509 to save the second part\n ;-- the full path has now been loaded\n <\/pre>\n\n\n\nIf, instead of issuing hardcoded strings you’re running in a loop, then you can toggle the command with a NotS instruction, for example:<\/p>\n\n\n\n
NotS 7,bTxByte0 ;toggle the command\n <\/pre>\n\n\n\nNow you can check for command completion by comparing the current Tx command with the Rx command, for example:<\/p>\n\n\n\n
Recall bTxByte0 ;get the request\n Recall bRxByte0 ;get the response\n Compare ;has the command been performed?\n GoIfNZ StillWaiting ;jump if still waiting<\/pre>\n\n\n\n