secs_sparkplug_b_integration_guide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
secs_sparkplug_b_integration_guide [2025/05/06 17:58]
amyw [Good Host Commands] 		secs_sparkplug_b_integration_guide [2025/05/06 18:35] (current)
wikiadmin
Line 23: Line 23:
 ===== Project Summary ===== ===== Project Summary =====
  
-TransSECS bridges legacy SECS/GEM automation with modern Sparkplug B IIoT ecosystems.+TransSECS bridges SECS/GEM automation with modern Sparkplug B IIoT ecosystems.
 By treating a GEM host as a Sparkplug node and every GEM interaction (messages, traces, polls, reports) as separate devices, the project delivers: By treating a GEM host as a Sparkplug node and every GEM interaction (messages, traces, polls, reports) as separate devices, the project delivers:
  
Line 98: Line 98:
  Parameters – ''LOTIDParamValue'' and ''PPIDParamValue'' appear exactly as entered by the host; on success they are echoed back unchanged.  Parameters – ''LOTIDParamValue'' and ''PPIDParamValue'' appear exactly as entered by the host; on success they are echoed back unchanged.
  
- Best-practice – SCADA / MES clients should subscribe to ''…HostCommandReply'' and check ''HCACK'' before assuming the tool accepted the command.+ <note tip>SCADA / MES clients should subscribe to ''…HostCommandReply'' and check ''HCACK'' before assuming the tool accepted the command</note>
  
 {{puml_002.png?500|}} {{puml_002.png?500|}}
Line 112: Line 112:
 Error detection – any non-zero ''HCACK'' must be treated as a transaction failure; the associated ''HostCommandPPSELECT'' echo still appears but only confirms that the message was transmitted, not that it succeeded. Error detection – any non-zero ''HCACK'' must be treated as a transaction failure; the associated ''HostCommandPPSELECT'' echo still appears but only confirms that the message was transmitted, not that it succeeded.
  
-Client hint – log ''ReasonList_*'' for root-cause analysis and surface a human-readable alarm where appropriate.+<note tip>log ''ReasonList_*'' for root-cause analysis and surface a human-readable alarm where appropriate.</note>
      
 {{puml_003.png?500|}} {{puml_003.png?500|}}
  • secs_sparkplug_b_integration_guide.1746572333.txt.gz
  • Last modified: 2025/05/06 17:58
  • by amyw