Toho Electronics TRM-00J User manual

DWG.No. 4B-6829-A
ＴＯＨＯ ＥＬＥＣＴＲＯＮＩＣＳ ＩＮＣ．
Operation Manual (Communication Edition)
(TOHO Protocol, MODBUS）
Model: TRM-00J
Name:PaperlessRecorder

DWG.No. 4B-6829-A
ThankyouverymuchforpurchasingTRM-00J.
Kindly readthisoperationmanualfor properusage.
Table of Contents
Section１BeforeUsingtheProduct·····································································································································································-1 -
１．１． AbouttheOperationManual·······················································································································································-1 -
１．２． RequirementsforCommunication··············································································································································-1 -
１．３． ThingsCommunicationFunctionCanDo····································································································································-1 -
１．４． Position(Priority)ofCommunication···········································································································································-1 -
１．５． SettingstoBeMadePriortotheCommunication······················································································································-1 -
Section２CommunicationSettings······································································································································································-2 -
２．１． Outline·····························································································································································································-2 -
２．２． SettingofCommunicationProtocol·············································································································································-3 -
２．３． SettingofFormat···········································································································································································-3 -
２．４． SettingofDeviceAddress······························································································································································-3 -
２．５． SettingofCommunicationSpeed,DataLength,StopBit,andParity·······················································································-3 -
２．６． SettingofBCC·················································································································································································-3 -
２．７． SettingofResponseDelayTime···················································································································································-3 -
Section３CommunicationOutline·······································································································································································-4 -
３．１． CommunicationProcedures·························································································································································-4 -
３．２． KindsofMessage···········································································································································································-4 -
Section４ExplanationaboutTOHOProtocolCommunication·························································································································-5 -
４．１． AbouttheFormat··········································································································································································-5 -
４．２． StructureofRequestMessage(DataTransmissionfromUpperComputertoThisProduct)················································-5 -
４．２．１． StructureofReadRequestMessage······························································································································-5 -
４．２．２． StructureofWriteRequest Message·····························································································································-5 -
４．２．３． StructureofSaveRequestMessage ······························································································································-5 -
４．３． StructureofResponseMessage(DataTransmissionfromThisProducttoUpper Computer)·············································- 6 -
４．３．１． ResponseMessageforReadRequestMessage···········································································································-6 -
４．３．２． Response Messagefor Write/SaveRequest Message ································································································-6 -
４．３．３． ResponseMessagefortheError····································································································································-6 -
４．４． ExplanationaboutCodes······························································································································································-7 -
４．５． ThingstoBeNotedduringtheCommunication·······················································································································-10 -
４．５．１． TimingofTransmission··················································································································································-10 -
４．５．２． RequestInterval·····························································································································································-10 -
４．５．３． ConditionsforResponse···············································································································································-10 -
４．５．４． AddressSpecificationError···········································································································································-10 -
４．５．５． Number ofDigitsofDataandPositionof DecimalPoint···························································································-10 -
４．５．６． OperationafterReceivinga SaveRequestMessage··································································································-10 -
４．５．７． SavingDataOtherthanSaveRequestMessage·········································································································-10 -
４．６． Sample TOHOCommunications················································································································································-11 -
４．６．１． SampleCommunicationforReading···························································································································-11 -
４．６．２． SampleCommunicationforWriting····························································································································- 12 -
Section５ExplanationaboutMODBUSProtocolCommunication·················································································································-13 -
５．１． MODBUS RTU ··············································································································································································-13 -
５．１．１． StructureofRequestMessage(DataTransmissionfrom UpperComputertoThisProduct)································-13 -
５．１．２． StructureofResponseMessage(DataTransmissionfromThisProducttoUpperComputer)·····························-14 -

DWG.No. 4B-6829-A
５．１．３． ExplanationaboutCodes··············································································································································-15 -
５．１．４． ThingstoBeNotedduringtheCommunication·········································································································- 17 -
５．２． MODBUSASCII·············································································································································································-18 -
５．２．１． StructureofRequestMessage(DataTransmissionfrom UpperComputertoThisProduct)································-18 -
５．２．２． StructureofResponseMessage(DataTransmissionfromThisproducttoUpperComputer)·····························-19 -
５．２．３． ExplanationAboutCodes··············································································································································-20 -
５．２．４． ThingstoBeNotedduringtheCommunication·········································································································- 22 -
Section６ListofIdentifiers··················································································································································································-23 -
６．１． OtherCommands········································································································································································-23 -
６．２． Input······························································································································································································-25 -
６．３． Scaling···························································································································································································-26 -
６．４． Display···························································································································································································-28 -
６．５． Scale······························································································································································································-29 -
６．６． Alarm·····························································································································································································- 30 -
６．７． REC/CALC······················································································································································································-35 -
６．８． Group name·················································································································································································-36 -
６．９． Group channel··············································································································································································-36 -
６．１０． GraphDisplay···········································································································································································-38 -
６．１１． Autoswitching·········································································································································································-39 -
６．１２． RecordOperation····································································································································································-39 -
６．１３． Schedule···················································································································································································-40 -
６．１４． Message ···················································································································································································-40 -
６．１５． DI ·······························································································································································································-43 -
６．１６． Progresstime···········································································································································································-43 -
６．１７． LCDbacklight············································································································································································-44 -
６．１８． Keyfunction·············································································································································································-44 -
６．１９． Comm. Settings········································································································································································-45 -
６．２０． Clock··························································································································································································-45 -
６．２１． Language··················································································································································································-45 -
Section７ListofASCII Codes···············································································································································································-46 -

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 1 -
Section１Before Using the Product
１．１． Aboutthe OperationManual
Thismanualexplainsthecommunication functionofTRM-00J.
１．２． Requirements for Communication
Asastandardfeatureforcommunication,this productisequippedwithRS-485and USB communicationfunction.
１．３． ThingsCommunicationFunction CanDo
Allows usertowriteandreadtoitemsofthisproductthataredescribed in “Section６ListofIdentifiers” such as “To change, start, or stop
items that can be operated through front keys” and “To read the information that can be displayed on the display section.”
Provided,however,thatsincetheRAMofthisproductisusedduringthereading/writingofdatathrough ordinarycommand,thedata
thatwaswrittenwillbereplacedbythe previousdata(datathatissavedinEEPROM)ifthepoweristurnedOFFandthenturnedON.
TosavethewrittendataintotheEEPROMofthisproduct, executethesaverequest message.
(See “４．５．”, “５．１．４．” and “５．２．４．” Things to Be Noted during the Communication.)
１．４． Position(Priority)ofCommunication
This product allows the user to change parameters through the key (including touch operation, hereinafter referred to as “key
operation”) even during the communication. Although the same setting can be changed simultaneously through key operationand
communication,donot changethesettingthroughcommunicationwhilethesetting is beingeditedthroughkeyoperation sincethereis
noprioritybetweenkeyoperationandcommunication.
１．５． Settingsto BeMadePrior totheCommunication
Several settings need to be made to this product in order for it to perform a communication function. See “Section２Communication
Settings”

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 2 -
Section２Communication Settings
２．１． Outline
Initial settingsneedtobemadetothisproductinorderforittoperformacommunication function.Settingsshallbemadethroughkey
operation.
Follow the procedure shown below to navigate between setting screens. See User’s Manual for details.
Power-on
Initial screen
Horizontal Trend
4 Sec. after
Main Menu
MENU key
System Setting
Comm. Setting

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 3 -
２．２． Settingof CommunicationProtocol
Selectthecommunicationprotocol.
２．３． Settingof Format
Sets the format for each protocol. See “Section４ExplanationaboutTOHO ProtocolCommunication” and “Section５Explanationabout
MODBUSProtocolCommunication” for details.
２．４． Settingof DeviceAddress
Settingmustbemadeinaccordancewithformatsettingspecifications.
２．５． Settingof CommunicationSpeed,Data Length,StopBit,and Parity
Settingmustbemadeinaccordancewiththesettingsofuppercomputerthatshallbeconnected.
During thesettingofMODBUSRTU,data lengthwillbefixedto8bits(data lengthsettingwillbeignored).
２．６． Settingof BCC
In case of TOHO Protocol, set “With or Without BCC Check (Turn BCC Check ON/OFF).”
２．７． Settingof Response Delay Time
Setthetime to take for the upper computer to complete the receiving of “request message,” open the line, and get ready for the next
input.

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 4 -
Section３Communication Outline
３．１． CommunicationProcedures
This product returns the “response message” as a reply to the “request message” that will be sent by the upper computer.
Therefore,the transmissionwillneverbeinitiatedbythisproduct.
High-level computer
This product
Request message
Response message
Request message
Response message
Transmitted by a highlevel
computer Transmitted by this product Transmitted by a highlevel computer Transmitted by this product
0-250ms 2 ms or more
Response delay
３．２． Kindsof Message
■Kindsofmessagecanbrieflybeclassifiedintothefollowing:
Read request message
Write request message
Request message (transmitted
from a high-level computer) Response message (transmitted from this product)
Receipt acknowledgement and data
response
Write complete response
Reception error and error description
response
：Response when a normal "request message" is received
：When a received "request message" contains an error
Store complete responseStore request message
■IncaseofTOHO Protocol,all codes(exceptforBCC)willbeexpressedinASCIIcode.
■IncaseofMODBUSRTU,allcodeswillbeexpressedinbinarycode.
■IncaseofMODBUSASCII,all codeswillbeexpressedin ASCIIcode.
■To code the program for the upper computer, see “Section６ListofIdentifiers” and “Section７ListofASCIICodes”
See“４．５．１．”,“５．１．４．１．”and
“５．２．４．１．”TimingofTransmission
See“４．５．２．”,“５．１．４．２．”and
“５．２．４．２．”RequestInterval

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 5 -
Section４Explanation about TOHO Protocol Communication
４．１． Aboutthe Format
TherearetwotypesofformatforTOHOProtocol—namely,Type1andType2—with thedifferenceinthespecificationofaddressand
secondidentifier.
See “４．４．Explanationabout Codes” for details.
４．２． StructureofRequest Message (DataTransmissionfrom UpperComputer toThisProduct)
■See “４．４．ExplanationaboutCodes” for codes from① to ⑪.
■See “４．６．１．SampleCommunicationforReading” and “４．６．２．SampleCommunicationforWriting” for concrete
samplesoftherequestmessage.
４．２．１． StructureofReadRequestMessage
Ｓ
Ｔ
Ｘ□□Ｒ□ □ □ Ｅ
Ｔ
Ｘ
Ｂ
Ｃ
Ｃ
① ② ③ ④ ⑦ ⑧⑤
□ □
４．２．２． StructureofWriteRequest Message
Ｓ
Ｔ
Ｘ□□Ｗ□ □ □ Ｅ
Ｔ
Ｘ
Ｂ
Ｃ
Ｃ
① ② ③ ④ ⑦ ⑧
□□□□□
⑥
□ □
⑤
４．２．３． StructureofSaveRequestMessage
Ｓ
Ｔ
Ｘ□□Ｗ Ｓ Ｔ Ｒ Ｅ
Ｔ
Ｘ
Ｂ
Ｃ
Ｃ
① ② ③ ④ ⑦ ⑧

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 6 -
４．３． StructureofResponse Message (DataTransmissionfromThisProductto UpperComputer)
■See “４．４．ExplanationaboutCodes” for codes from ① to ⑪.
■See “４．６．１．SampleCommunicationforReading” and “４．６．２．SampleCommunicationforWriting” for concrete
samplesoftheresponsemessage.
４．３．１． ResponseMessageforReadRequestMessage
Ｓ
Ｔ
Ｘ□ □ Ａ
Ｃ
Ｋ□ □ □
① ② ⑨ ④
Ｅ
Ｔ
Ｘ
Ｂ
Ｃ
Ｃ
⑦ ⑧
□□□□□
⑥
□ □
⑤
４．３．２． ResponseMessageforWrite/SaveRequestMessage
Ｓ
Ｔ
Ｘ□ □ Ｅ
Ｔ
Ｘ
Ｂ
Ｃ
Ｃ
① ② ⑦ ⑧
Ａ
Ｃ
Ｋ
⑨
４．３．３． ResponseMessagefortheError
Ｓ
Ｔ
Ｘ□ □ Ｅ
Ｔ
Ｘ
Ｂ
Ｃ
Ｃ
① ② ⑦ ⑧
Ｎ
Ａ
Ｋ
⑩
□
⑪

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 7 -
４．４． ExplanationaboutCodes
■The following codes other than ⑧BCC will be expressed in ASCII code.
■See “Section７ListofASCII Codes” for the detail about ASCII codes.
■ToconvertintoASCIIcode,see “４．６．SampleTOHOCommunications”
①STX
Itisacodethatisnecessaryforthereceivingsidetodetect thestartofthemessage. It shallbeattachedtothestartofthecharacter
string tobesent.
② Address
Format =Type1
Specifiesthedevice thatwillbecommunicatedbythe uppercomputer.Addresssettingvalueshallserve astheaddressofthis
product.
Format =Type2
Specifiesthechannelofthedevicethatwillbecommunicatedbytheupper computer.Addressofthesubjectedchannelshall
becomputedbythefollowingformula:
Address={(AddressSettingValue-1)x6}+ SubjectedChannel
Example)Addressofchannel4whereaddresssettingvalue= 5
Address={(5-1)x6} +4=28
③ Contents of Request
SetthesymbolRorW.
R:Ifthedataistobereadfromthis product
W:Ifthedataistobewrittenorsavedintothisproduct
④ First Identifier
Itisaclassificationsymbol(identifier)ofthedatatobereadorwrittenthatwillbeexpressedbythe3-digitalphanumericASCIIcode.
See “10. List of Identifiers (Codes).”
⑤ Second Identifier
Format =Type1
Itisusedtospecifythechannelforthedatatobespecifiedbythefirstidentifierthathasbeenallocatedtoeach channel.
Thisisnotnecessaryforthe datathatis notallocatedperchannel.Donotincludeitintherequestmessage.
See “Section６ListofIdentifiers” to check if the second identifier is required or not.
Format =Type2
Thiswillnotbeused.Donotincludeit intherequest message.

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 8 -
⑥ Numerical Data
Uponwriting, 5-digitor6-digitnumericaldatacanbewritten.Uponreading,numericaldatawillbeconvertedinto5-digit or6-digit
numericaldata inaccordancewiththeconfigurationofthisproduct.
Negative data: The symbol “-” is considered one digit to be displayed at the largest digit.
Positionofdecimal point:Decimalpointwillnotbeincluded in thedata.
Example:5-digit numerical data “00010” means thefollowing:
Example
Meaning of Nume
rical Value
If the display unit of the data is wit
hout decimal point
→ 10
If the display unit of the data is up
to the first decimal place
→ 1.0
If the display unit of the data is up
to the second decimal place
→ 0.10
⑦ ETX
Itisacodethatisnecessaryforthereceivingsidetodetect theend of themessage.Itshallbeattached to theend ofthecharacter
string tobesent(exceptforBCC).
⑧ BCC
GetEx-ORofallcharactersfromSTXtoETXwiththecheckcodeforthedetectionof error.
ThiscodeshallnotbeincludedintheresponsemessageifBCCCheckisturnedOFFatthecommunicationsettingofthisproduct.
See “２．６．Settingof BCC”
⑨ ACK
It is an acknowledge code that will be included in the “response message” to be replied by thisproductifnoerrorisfound in the
received message.
⑩ NAK
It is a reject code that will be included in the “response message” to be replied by this product if error is found in the received
message.
If there is an error in the received “request message,” content of error (⑪ Error Code) will also be attached (next to NAK) to the
“response message” that will be returned by this product.

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 9 -
⑪ Error Code
If there is an error in the “request message” that was received by this product, the description of thesaiderror(numberinthetable
shown below) will be attached (next to “⑩ NAK”) to the “response message” that will be returned by this product.
Since error number “0” indicates the breakdown of measuring equipment (memory error or A/D conversion error),itwillbe
included in the “response message” whether or not there is an error in the “request message.”
Formultiple errors,the largesterrornumberwillbeincluded.
Contentsandclassificationoferrorarethefollowing:
ErrorNumber
Description of errors in “Request Message” that was received by this product
0
Malfunctionofmeasuringequipment(memoryerror orA/Dconversionerror)
1
Numerical value data is out of the “setting range that is specified individually by the setting
item”
2
Changingoftherequested itemisprohibitedornoitemtoread
3
ASCII code that is other than numeric value has been set to the portion for the numeric
value
ASCII code that is other than “0” or “-” has been set to the position for the symbol
4
Format Error
5
BCCError
6
OverrunError
7
FramingError
8
Parity Error

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 10 -
４．５． Thingsto BeNotedduringthe Communication
４．５．１． TimingofTransmission
Uponusingthecommunicationfunction,setenoughresponsedelaytimetoensurethecommunication(sending/receiving)withthe
hostcomputer.
See “２．７．SettingofResponseDelayTime”
４．５．２． RequestInterval
If “request message” is to be sent continuously by the upper computer, wait for at least 2msecs from the arrival of the “response
message” from this product before sending the next requestmessage.
４．５．３． ConditionsforResponse
This product will not return the “response message” if STX and ETX (BCC) are not included in the “request message.”
Therefore, although there is an error in the “request message,”“response message” with NAK anderrorcodewillnotbereturnedunless
theaboveconditionismet.
Therefore, the upper computer should resend the necessary “request message” if the “response message” is not returned within
areasonabletime.
OnceSTXisreceived,thisproductclearsallcodesthatwerereceivedpriortothesaid STX.
４．５．４． AddressSpecificationError
This product will not respond to any “request message” that specifies the address that is other than the one that has been settoitself.
Therefore,if there isanerrorintheaddress section of the “request message,” none of the slave stations will return the “response
message.”
Therefore, the upper computer should resend the necessary “request message” if the “response message” is not returned within
areasonabletime.
OnceSTXisreceived,thisproductclearsallcodesthatwerereceivedpriortothesaidSTX.
４．５．５． Number of DigitsofDataandPositionofDecimalPoint
See “4.4. Explanation About Codes ⑥ Numerical Data.”
４．５．６． OperationafterReceivinga SaveRequestMessage
Thisproductstartsthesavingofdataonceitreceivesthesaverequestmessagecorrectlyfromtheuppercomputer.
Onlythedatathatisdifferentfromtheonestoredin EEPROM(changeddata)shallbesaved.Datawillbesaved within6seconds.
Thisproductwillsendtheresponse(ACK)whenthesaverequestmessageisreceived. Somedatamay belost iftheproduct isturnedOFF
whilethesavingprocessisinprogress.Donotturn thepowerofthisproduct OFFforatleast6secondsaftersendingasaverequest
message.
４．５．７． SavingDataOtherthanSaveRequest Message
Thisproductsavestheparameter intoEEPROM even withoutreceivingthesaverequestmessageinthiscase:
・Iftheparameterischangedthroughkeyoperation,it writesonlychanged parameterandotherrelatedparameters.

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 11 -
４．６． SampleTOHO Communications
４．６．１． SampleCommunicationforReading
Example:
Request message: Request this productin which address is set as “10,” to read “Channel 1 Measuring Temperature.”
(Ifformat=Type1)
(Uppercomputer)
Fortheaboverequest,
Response message: Returns the data of “Channel 1 Measuring Temperature” (00100).
(Thisproduct)
ReadRequest Message(tobesentbytheuppercomputer)
Ｓ
Ｔ
Ｘ
１ ０ Ｒ Ｐ Ｖ １
Ｓ
Ｔ
Ｘ
１ ０
Ａ
Ｃ
Ｋ
Ｂ
Ｃ
Ｃ
ＰＶ１
Ｅ
Ｔ
Ｘ
００１００
① ② ③ ｜④｜
① ② ⑨｜④｜ ⑦ ⑧｜｜⑥｜｜
Ｂ
Ｃ
Ｃ
Ｅ
Ｔ
Ｘ
⑦ ⑧
０ １
⑤
０ １
⑤
Code
symbol and Data
ASCIIcode ※2
① Start Code
STX
02H
② Address
10
31H,30H
③ Contents of Request
R
52H
④ First Identifier ※1
PV1
50H,56H,31H
⑤ Second Identifier ※1
01
30H,31H
⑥ Numerical Data
00100
30H,30H,31H,30H,30H
⑦ End Code
ETX
03H
⑧ BCC Data
Request
Response
64H
01H
⑨ Acknowledgment Code
ACK
06H
※1: See “Section６ListofIdentifiers” for the detail about identifiers.
※2: See “Section７ListofASCIICodes” for the detail about ASCII codes.

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 12 -
４．６．２． SampleCommunicationforWriting
Example:
Request message: To change “Channel 3 Input Type” to “Pt100 (13)” and write it into thisproduct.
(Uppercomputer)
Fortheaboverequest,
Responsemessage:Returnthe messagetotellthattherequestmessage hasbeenreceived.
(Thisproduct) ※Readthedataseparatelytocheckifthedataiswrittencorrectly.
WriteRequestMessage(to besentbytheuppercomputer)
Ｓ
Ｔ
Ｘ
０ １
Ａ
Ｃ
Ｋ
Ｂ
Ｃ
Ｃ
Ｅ
Ｔ
Ｘ
Ｓ
Ｔ
Ｘ
０ １ Ｗ
Ｂ
Ｃ
Ｃ
Ｉ Ｎ Ｐ
Ｅ
Ｔ
Ｘ
０００１ ３
①②③｜④｜ ⑦ ⑧｜｜⑥｜｜
① ② ⑦ ⑧⑨
０３
⑤
Code
symbol and Data
ASCIIcode ※2
① Start Code
STX
02H
② Address
01
30H,31H
③ ContentsofRequest
W
57H
④ First Identifier ※1
INP
49H,4EH,50H
④ Second Identifier ※1
03
30H,33H
⑤ Numerical Data
00013
30H,30H,30H,31H,33H
⑥ End Code
ETX
03H
⑦ BCC Data
Request
Response
31H
06H
⑧ Acknowledgment Code
ACK
06H
※1: See “Section６ListofIdentifiers” for the detail about identifiers.
※2: See “Section７ListofASCIICodes” for the detail about ASCII codes.

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 13 -
Section５Explanation about MODBUS Protocol Communication
５．１． MODBUSRTU
５．１．１． StructureofRequestMessage(DataTransmissionfrom UpperComputertoThisProduct)
５．１．１．１． StructureofReadRequestMessage
a)
SlaveAddress
01H
b)
FunctionCode
03H
c)
RegisterAddress
Upper
00H
Firstregisteraddress
Lower
00H
d)
Number ofRegisters
Upper
00H
2(fixed)
Lower
02H
e)
CRC-16
Lower
C4H
Upper
0BH
５．１．１．２． StructureofWriteRequest Message
a)
SlaveAddress
01H
b)
FunctionCode
10H
c)
RegisterAddress
Upper
01H
Firstregisteraddress
Lower
00H
d)
Number ofRegisters
Upper
00H
2(fixed)
Lower
02H
f)
Number of Bytes
04H
Number ofRegisters x2
g)
Dataforthefirstregister
(Lowerword)
Upper
00H
③
Data structure is ①②③④H.
(① represents 1 byte)
Lower
0DH
④
Dataforthefirstregister
(Upperword)
Upper
00H
①
Lower
00H
②
e)
CRC-16
Lower
6FH
Upper
FCH
５．１．１．３． StructureofSaveRequestMessage
a)
SlaveAddress
01H
b)
FunctionCode
10H
c)
RegisterAddress
Upper
20H
Firstregisteraddress
Lower
0EH
d)
Number ofRegisters
Upper
00H
2(fixed)
Lower
02H
f)
Number of Bytes
04H
Number ofRegisters x2
g)
Dataforthefirstregister
(Lowerword)
Upper
00H
Dataforthesavingofsettingis
optional.
Lower
00H
Dataforthefirstregister
(Upperword)
Upper
00H
Lower
00H
e)
CRC-16
Lower
EBH
Upper
E2H

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 14 -
５．１．２． StructureofResponseMessage(Data TransmissionfromThisProducttoUpperComputer)
５．１．２．１． ResponseMessageforReadRequestMessage
a)
SlaveAddress
01H
b)
FunctionCode
03H
f)
Number of Bytes
04H
Number ofRegisters x2
g)
Dataforthefirstregister
(Lowerword)
Upper
00H
③
Datastructure is ①②③④H.
(① represents 1 byte)
Lower
64H
④
Dataforthefirstregister
(Upperword)
Upper
00H
①
Lower
00H
②
e)
CRC-16
Lower
BBH
Upper
ECH
５．１．２．２． ResponseMessageforWrite/SaveRequestMessage
a)
SlaveAddress
01H
b)
FunctionCode
10H
c)
RegisterAddress
Upper
01H
Firstregisteraddress
Lower
00H
d)
Number ofRegisters
Upper
00H
2(fixed)
Lower
02H
e)
CRC-16
Lower
40H
Upper
34H
５．１．２．３． ResponseMessagefortheError
a)
SlaveAddress
01H
b)
FunctionCode
83H
← In case of error, the value that is consist
offunctioncodeofrequestmessage
+80Hwillbeset.
h)
ErrorNumber
03H
e)
CRC-16
Lower
01H
Upper
31H

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 15 -
５．１．３． ExplanationaboutCodes
■Thefollowing codesfrom(a) SlaveAddress,(b)FunctionCodeupto(h)ErrorNumberwillbeexpressedin8-bitbinarycode:
(a)SlaveAddress
Itisanaddressofthedevicethatwillbecommunicatedbythe uppercomputer(thisproduct).
Address intheresponsemessageformthisproduct indicatesthesourceofresponsemessage.
(b)FunctionCode
Enterthecode03Hor10H.
・03H:Ifthedataistobereadfromthisproduct
・10H:Ifthedataistobewrittenorsavedintothisproduct
(c)RegisterAddress
Specifiesthepositionofdatatobereadorwrittenwith2bytes.
See “Section６ListofIdentifiers” for the address of each command.
(d)NumberofRegisters
Specifiesthenumberofregistersthatwrites.
Since the number of registers of this product is fixed to 2, set it to “0002H.”
(e)CRC-16
Itisanerror-checkingcodeforthedetectionofapossibleerrorinthe message.ItsendsCRC-16(CyclicRedundancyCode).
GeneratingpolyomicalofCRC-16thatisused in thisproductis X16 +X15 +X2+ 1.
Ifitistobeattachedattheendofthemessageasanerrornumber,attachthelowerbyteofCRCbeforetheupperbyte.
(f)NumberofBytes
Specifiesthenumberofregistersthatreadsandwrites x2.
Since the number of registers of this product is 2 (fixed), set “04H.”
(g)DataSection
Specifiesthedatatobewrittenintotheregister.Datais4bytes(fixed).
Ifthedatacontainsa decimalpoint,setthenumeric value thatignoresthedecimalpoint.
Datathatisenclosedinparenthesesisthevaluethatwillbeusedintheactualmessage to be sent. See “５．１．１．
StructureofRequestMessage(DataTransmissionfrom UpperComputertoThisProduct)” for details.
ContentsofCommunication
HEXData
PV=1200.0(℃)
00002EE0h(2EE00000)
PV=-10.00(℃)
FFFFFC18h(FC18FFFF)

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 16 -
(h)ErrorNumber
Ifthereisanerror inthemessage that was sent by the upper computer, the error number will be included in the “response
message” of this product for the reply.
Formultiple errors,the largesterrornumberwillbeincluded.
Contentsand classificationoferrorarethefollowing:
ErrorNumber
Description of errors in “Request Message” that was received by this product
01
Receivedanunsupportedfunctioncode
02
Receivedanunspecifiedaddress
03
Numerical value data is out of the “setting range that is specified individually by the
setting item”
04
Malfunctionofmeasuringequipment(memoryerror orA/Dconversionerror)

Communication manual TOHO ELECTRONICS INC.
DWG.No. 4B-6829-A
- 17 -
５．１．４． ThingstoBeNotedduringtheCommunication
５．１．４．１． TimingofTransmission
Uponusingthecommunicationfunction,setenoughresponse delaytimeto ensurethecommunication (sending/receiving)withthe
hostcomputer.
See “２．７．SettingofResponseDelayTime”
５．１．４．２． RequestInterval
If “request message” is to be sent continuously by the upper computer, wait for at least 2msecs from the arrival of the “response
message” from this product before sending the next request message.
５．１．４．３． ConditionsforResponse
This product will not return the “response message” if there is a time intervalofmorethan3.5charactersbetween datathatconsistof
the “request message” since it cannot identify these data as one whole “request message.”
Therefore, although there is an error in the “request message,”“response message” with the errornumber(responsefortheerror)will
notbereturnedunlesstheaboveconditionismet.
Therefore, the upper computer should resend the necessary “request message” if the “response message” is not returned within
areasonabletime.
Atatime intervalofmorethan 3.5characters,thisproductclearsallcharactersthatwerereceivedpriortothesaidinterval.
５．１．４．４． AddressSpecificationError
This product will not respond to any “request message” that specifies the address that is other than the one that has beensettoitself.
Therefore, if there is an error in the address section of the “request message,” none of the slave stations will return the “response
message.”
Therefore, the upper computer should resend the necessary “request message” if the “response message” is not returned within
areasonabletime.
Atatime intervalofmorethan3.5 characters,thisproductclearsallcharactersthatwerereceivedpriortothesaidinterval.
５．１．４．５． Number of DigitsofDataandPositionofDecimalPoint
See “５．１．３．ExplanationaboutCodes(g) Data Section.”
５．１．４．６． OperationaftertheReceivingofSaveRequestMessage
Thisproductstartsthesaving ofdataonceitreceivesthesave requestmessagecorrectlyfromtheuppercomputer.
Onlythedatathatisdifferentfromtheonestoredin EEPROM(changeddata)shallbesaved.Datawillbesaved within6seconds.
Thisproductwillsendtheresponse(ACK)whenthesaverequestmessageisreceived. Somedatamaybelost iftheproductisturnedOFF
whilethesavingprocessisinprogress.Donotturn thepowerofthisproduct OFFforatleast6secondsafterthesendingofsaverequest
message.
５．１．４．７． SavingDataOtherthanSaveRequest Message
Thisproductsavestheparameter intoEEPROM even withoutreceivingthesave requestmessageinthiscase:
・Iftheparameterischangedthroughkeyoperation,it writesonlychanged parameterandotherrelatedparameters.