Connecting Modbus and LonWorks Networks - FieldServer ...

More documents

Recommendations

Info

Data ResolutionBit Packing//================================================================================//// Data Arrays// Packed_Bit is enabled merely by declaring the data array to be// of type: Packed_BitData_ArraysData_Array_Name ,Data_Format ,Data_Array_LengthPacker ,Packed_Bit ,200Packed Bit Data ArrayModbus 3xxxxDefault Type = Uint16PollNo typecastingoccurs. Data Arrayis treated as typeUint16 to Matchvariable typeOffset 030001Offset 0DI 1….DI16------------------------------Offset 130002Offset 16DI17…DI32No typecastingoccurs. Data Array istreated as type Bit tomatch variable typeMove each bit to a bitdata type
Translation ChallengesEngineering UnitsTHE CHALLENGE‣ Modbus is a simple protocol that transfers raw data andapplies no significance to any of the values transferred.‣ Significance is achieved through documentation of theModbus registers in the vendor documentation‣ LonWorks is obsessive about applying significance tovalues transferred. All SNVT Types inherently possess anEngineering unit, data resolution and data range.‣ All Engineering units in LonWorks are SI (Metric). This isnot obvious to most LonWorks users as applications suchas LonMaker will automatically scale the values to Imperialformat in the USA.‣ The challenge is matching up the values’ Engineering unitsused in Modbus with the SI Engineering Unit specified inLonWorks
Page 1 and 2: Connecting Modbus andLonWorks Netwo
Page 3 and 4: The Modbus Standard‣ A truly open
Page 5 and 6: 0000165536Modbus Memory MapAddressF
Page 7 and 8: Modbus VariationsVariations resulti
Page 10 and 11: Modbus TCPDealing with Ethernet and
Page 12 and 13: LonWorks OverviewLonWorks Addressin
Page 14 and 15: LonWorks OverviewNetwork Managers
Page 16: LonWorks OverviewData Transfer - Up
Page 19 and 20: LonWorks OverviewNeuron ID’s vs P
Page 21 and 22: LonWorks ConfigurationBasic Configu
Page 23 and 24: Lonworks ConfigurationXIF for Basic
Page 25 and 26: Lonworks ConfigurationCommissioning
Page 28 and 29: Translation ChallengesData Resoluti
Page 30 and 31: Data ResolutionSNVT_Option Feature/
Page 32 and 33: Data ResolutionScalingManaging Floa
Page 36 and 37: Translation ChallengesEngineering U
Page 38 and 39: Translation ChallengesSimple vs Str
Page 40 and 41: Simple vs Structured VariablesSelec
Page 42 and 43: Translation ChallengesSingle vs Blo
Page 44 and 45: Single vs Block Data TransferHelp!
Page 46 and 47: Translation ChallengesMaster/Slave
Page 48 and 49: Translation ChallengesMaster/Slave
Page 50 and 51: Master/Slave vs Peer/Peer Communica
Page 52 and 53: Translation ChallengesMultiple vs S
Page 54 and 55: Multiple vs Single Node Representat
Page 56 and 57: Multiple vs Single Node Representat
Page 58 and 59: Translation ChallengesLonMark vs Mo
Page 60 and 61: Questions?Marketing and Sales:Steve

Connecting Modbus and LonWorks Networks - FieldServer ...

Create successful ePaper yourself

Delete template?

Save as template?