(pfbOnline card_id [operation...])
| DpMaster |
| DpSlave |
| FdlMsg |
| FdlSap |
If the command is successfully issued to the card, then
(pfbOnline card_id response status status_str)
where response, status and status_str are as defined for the pfbCmd command. Otherwise, one of the following error messages:
(error "pfbOnline DR_ERR_CARD_INVALID (time) invalid card: card_id") (error "pfbOnline PFB_ERR_NO_CARD (time) Card not available") (error "pfbOnline PFB_ERR_CMD_TIMEOUT (time) Cmd failed (timeout)") (error "pfbOnline PFB_ERR_CMD_INVALID (time) Cmd not valid in current card state")
This command simplifies the procedure for bringing the card online. At its core, it is equivalent to the command (pfbCmd card_id CMD_GO_ON). However, it also ensures that the appropriate enable and internal event flags are set. The command may take up to 7 seconds to complete. The card must be in an offline state, otherwise the command is invalid. The configuration data for the various operations (DP master, DP slave, FDL messages, FDL SAPs)must be set up before the card is put online. (See pfbLoadCfg command, as well as the following support files: pfbDpMaster.cfg, pfbDpSlave.cfg, pfbFdlSap.cfg, and pfbFdlMsg.cfg.)
When the card goes online, it checks the various configurations and allocates the required internal buffers (for SAP and messages). If no operation is specified, then the command performs a simple check of the configuration to determine which operations are possible. The following table provides a summary of the basis for the decision:
| operation | Configuration checks. |
| DP master | At least one master control block (slave device) defined. |
| DP slave | Not checked. |
| FDL messages | At least one message block with a non-zero maximum transmit or receive length. |
| FDL SAPs | At least one SAP block with a defined type. |
Copyright © 1995-2006 by Cogent Real-Time Systems, Inc. All rights reserved.