Member Login
Search
Jump to a Date
Sponsored Communities
Cool stuff
Neat Stuff

Visit our shop for nerds in control lifestyle products.
Thermal Overload
The threads that wouldn't die...
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
- PC reliability?
- Windows, real time
- PID loops
- PCs vs. PLCs
- Replacing people
- MS 'monopoly'?
- Software quality
- Where do we go from here?
- Why pay?
Fortune
"Who cares if it doesn't do anything? It was made with our new
Triple-Iso-Bifurcated-Krypton-Gate-MOS process ..."
Triple-Iso-Bifurcated-Krypton-Gate-MOS process ..."
RSS Feed
www.control.com/rss/
To get a personalized feed, become a member at no cost.
I'm curious if anyone has details regarding the general purpose of function codes 13, 14, 40, 43.
My current understanding is as follows:
13: CANopen General Reference Request and Response
14: Read Device Indentification
40: Read/Write Object Dictionary
43: Encapsulated Interface Transport
Is there a documented usage of Function Codes 13 & 14 specific to Schneider applications that is different from above?
My current understanding is as follows:
13: CANopen General Reference Request and Response
14: Read Device Indentification
40: Read/Write Object Dictionary
43: Encapsulated Interface Transport
Is there a documented usage of Function Codes 13 & 14 specific to Schneider applications that is different from above?
The descriptions you listed for 13 and 14 aren't Modbus function codes. Those are Modbus MEI "types" for use as parameters with function 43 (encapsulated interface transport). That is an important distinction to make. I don't however see 40 listed as an MEI object type. (Function 43 is normally used for tunneling CAN over Modbus/TCP).
It does say in the back of the "MODBUS Application Protocol Specification V1.1b" spec: "The following function codes and subcodes shall not be part of this published Specification and these function codes and subcodes are specifically reserved. The format is function code/subcode or just function code where all the subcodes (0-255) are reserved: 8/19; 8/21-65535, 9, 10, 13, 14, 41, 42, 90, 91, 125, 126 and 127".
So *functions* (not MEI type) 13 and 14 are not defined in the spec, but they are "reserved" (although nothing is said about 40). I suspect they are related to certain aspects of programming and management of Schneider PLC hardware. Exactly what they do probably depends upon the particular hardware being used (which is why they wouldn't be part of the communications protocol spec).
It does say in the back of the "MODBUS Application Protocol Specification V1.1b" spec: "The following function codes and subcodes shall not be part of this published Specification and these function codes and subcodes are specifically reserved. The format is function code/subcode or just function code where all the subcodes (0-255) are reserved: 8/19; 8/21-65535, 9, 10, 13, 14, 41, 42, 90, 91, 125, 126 and 127".
So *functions* (not MEI type) 13 and 14 are not defined in the spec, but they are "reserved" (although nothing is said about 40). I suspect they are related to certain aspects of programming and management of Schneider PLC hardware. Exactly what they do probably depends upon the particular hardware being used (which is why they wouldn't be part of the communications protocol spec).
From Control Engineering magazine...
Related articles from Control
Engineering magazine- Wireless manager for instrumentation and control devices
- New podcast: One road to wireless instrumentation
- Upgraded communication modules make PLC to PLC communications easier
- Industrial Ethernet advantages using Profinet protocol
- Fieldbus Foundation Seminar: Chicago
- Radios for long-distance use in industrial mesh network
- Embedded: Precise Time Protocol enables new-generation Ethernet mobile networks
- Optimize field wiring with decentralized IP 67 fieldbus system
- Pack Expo: SERCOS real-time communications for packaging
- Modbus RTU master, distributed I/O in compact package: microNCS
Above articles copyright 2008 Reed Business Information.
Subject to its Terms of Use.
Your use of this site is subject to the terms and conditions set forth under Legal Notices and the Privacy Policy. Please read those terms and conditions carefully. Subject to the rights expressly reserved to others under Legal Notices, the content of this site and the compilation thereof is © 1999-2008 Control Technology Corporation. All rights reserved.
Our Advertisers
Help keep our servers running...
Patronize our advertisers!
Patronize our advertisers!




