Latest communication verification
This page keeps the current public summary only. Older detailed notes are not kept in the public documentation set.
Current Retained Summary
- current Flow Library baseline checked for release notes:
0.2.3 - current release-prep target:
0.2.12 - verified PLC models:
FX5UC-32MT/D,Q06UDVCPU,R08CPU - verified transports:
TCP,UDP - verified public nodes:
slmp-connection,slmp-read,slmp-write - retained first-run smoke path:
slmp-basic-read-write.json - 2026-05-01 iQ-R live check:
R08CPUat192.168.250.100:1025over TCP returnedLCS10=falseandLCC10=falsethroughreadNamed - 2026-05-02 release-prep docs align the Node-RED matrix flow with one-click run-all read/write, status-lamp feedback, JSONL logging,
plcProfileresult records, and PLC-type-unsupportedSKIPPEDrecords
Confirmed Public Register Scope
- bit devices:
SM,X,Y,M,L,F,V,B,TS,TC,LTS,LTC,STS,STC,LSTS,LSTC,CS,CC,LCS,LCC,SB,DX,DY - word devices:
SD,D,W,TN,LTN,STN,LSTN,CN,LCN,SW,Z,LZ,R,ZR,RD - typed forms:
:S,:D,:L,:F - high-level special forms:
.bit,,count,:STR,DSTR
Practical Cautions
- set one explicit PLC profile for every connection
- older Flow Library
0.2.3flows must be updated fromPLC series/frame typeto the current PLC profile selector - start with
Dreads before using typed, counted, or string forms - keep
slmp-device-matrix.jsonfor later verification, not for the first smoke test - do not rely on Node-RED for PLC model-specific range or upper-bound checks; format errors are local, range errors come from the PLC/runtime response
.bit,countis not part of the current public high-level surface
Where Older Evidence Went
This public page keeps only the current summary. Detailed historical evidence is retained as maintainer notes.