Modbus logging with child component names, ver. 3.1.1606
This commit is contained in:
@@ -15,7 +15,8 @@ namespace TBF.Rig.GenericDevices
|
||||
/// They are calculated inside this function as required by Modbus specification.
|
||||
/// </summary>
|
||||
/// <param name="message">Message incl CRC fields, CRC bytes dont have to be set</param>
|
||||
void SendMessage(byte[] message);
|
||||
/// <param name="meno">Modbus child component name</param>
|
||||
void SendMessage(byte[] message, string meno);
|
||||
|
||||
/// <summary>
|
||||
/// Send a structured modbus message.
|
||||
@@ -24,7 +25,8 @@ namespace TBF.Rig.GenericDevices
|
||||
/// <param name="function">Function (0..127)</param>
|
||||
/// <param name="dataAddress">Address of data to be transferred (0..65535)</param>
|
||||
/// <param name="dataCount">Count of data bytes to be transferred (0..65535)</param>
|
||||
void SendMessage(byte modbusAddress, byte function, ushort dataAddress, ushort dataCount);
|
||||
/// <param name="meno">Modbus child component name</param>
|
||||
void SendMessage(byte modbusAddress, byte function, ushort dataAddress, ushort dataCount, string meno);
|
||||
|
||||
Queue<byte[]>[] ReceivedTelegrams { get; }
|
||||
|
||||
|
||||
Reference in New Issue
Block a user