Reassign data protocols, both incoming and outgoing.
More...
|
void | mip::C::insert_mip_system_interface_control_command (microstrain_serializer *serializer, const mip_system_interface_control_command *self) |
|
void | mip::C::extract_mip_system_interface_control_command (microstrain_serializer *serializer, mip_system_interface_control_command *self) |
|
void | mip::C::insert_mip_system_interface_control_response (microstrain_serializer *serializer, const mip_system_interface_control_response *self) |
|
void | mip::C::extract_mip_system_interface_control_response (microstrain_serializer *serializer, mip_system_interface_control_response *self) |
|
mip_cmd_result | mip::C::mip_system_write_interface_control (mip_interface *device, mip_comms_interface port, mip_comms_protocol protocols_incoming, mip_comms_protocol protocols_outgoing) |
|
mip_cmd_result | mip::C::mip_system_read_interface_control (mip_interface *device, mip_comms_interface port, mip_comms_protocol *protocols_incoming_out, mip_comms_protocol *protocols_outgoing_out) |
|
mip_cmd_result | mip::C::mip_system_save_interface_control (mip_interface *device, mip_comms_interface port) |
|
mip_cmd_result | mip::C::mip_system_load_interface_control (mip_interface *device, mip_comms_interface port) |
|
mip_cmd_result | mip::C::mip_system_default_interface_control (mip_interface *device, mip_comms_interface port) |
|
Reassign data protocols, both incoming and outgoing.
Responds over the port that sent the command with an ACK/NACK immediately after the operation is complete. It is the user's responsibility to not send any critical information or commands while awaiting a response! Doing so while this command processes may cause those packets to be dropped.
Constraints:
- Limited parsers and data streams are available. Refer to your device manual for more information.
- The Main port always has a MIP parser and MIP data stream bound. Additionally, Main is the only port that can process interface control commands.
If response is NACK, no change was made. Here's what can cause a NACK:
- The requested protocol isn't supported on this device, or on this port, or this device doesn't support that many parsers.
- The request would break the general constraints listed above, or a device-specific constraint.
◆ mip_system_interface_control_command
◆ mip_system_interface_control_response
◆ extract_mip_system_interface_control_command()
◆ extract_mip_system_interface_control_response()
◆ insert_mip_system_interface_control_command()
◆ insert_mip_system_interface_control_response()
◆ mip_system_default_interface_control()
◆ mip_system_load_interface_control()
◆ mip_system_read_interface_control()
◆ mip_system_save_interface_control()
◆ mip_system_write_interface_control()