Importing Hardware Catalog vs GSD files

Hi,

I'm currently working on a project where I had to import a hardware catalog as well as GSD files. It is the first time I've had to do this, and I am puzzled as to why both are necessary. What exactly is the difference in function between a hardware catalog and the GSD files? Why would it be necessary to import both into a project?

According to this manual (page 111), "All the properties of a DP slave are saved in a device database (*.GSD) file. STEP 7 requires a *.GSD file for every DP slave in order that the DP slave can be selected in the module catalog." If the GSD file is required to be able to select an item from the catalog, why bother separating the information into two sources, why not just make it available in a single file? What are the advantages of this approach?

If you know of any resources on the topic, I'd appreciate you let me know.

Thanks!

Hello,

better you saye for whixh HW you need both, a GSD and a HSP.

Normally you only need one of this!

Difference between HSP and GSD is that with a GSD you can only created a communication configuration for the device, with a HSP normaly a extend configuration is possible (GUI Wizzards etc.).

With a HSP is also possible to insert non Slave device in the catalog (new PLC, for example) this can#t be do with a GSD.

Regards

Christoph

Thanks for your answer.

On my current project, some of the hardware for which I had to add both a hardware config file and a GSD file include a kuka robot, smc valve controller, and a siemens Scalance. I don't know if this helps.

Thanks again!

Edit: I don't know if this is relevant, but the hardware config files I am importing have a .dat extension, not .hsp.

Hello,

with which SW you work ? TIA or step7 V5?
Which devices need a HSP and which a GSD?

Have you a example for the .dat files?

Normaly you get only a HSP for Siemens devices , not for 3rd party products, for this you must use the GSD Files.

Regards

Christoph