I am a bit confused as to what you expect the PC to do. Is it going to act as the master in your network? What functionality does it need?

The EDS file tells you the object dictionary of a node, but it is application-dependent what your master will do with that node. A basic master will simply place all the nodes into operational mode. A more complex master will assign node IDs and then write configurations using SDOs.

In both cases the EDS file is really used by the network designer rather than somehow built into the master code.

Note that the EDS file describes a class of devices and not a specific device. I.e. an EDS file would describe the superset of all I/O nodes. However a specific node might only implement digital inputs and no analog inputs. What you would need is called a Device Configuration File (DCF). This is the same as an EDS but it contains a node ID and the specific entries for a specific node. Only the DCF can tell you what the message IDs for PDOs will be, so if you are looking to somehow automatically process PDOs then you would need a DCF.

However I don't think you will find what you are looking for. You need to look at your network as a whole, assign node IDs and then you will know the PDO message IDs. Then in your master application you write code using the NI API to process those PDOs (which are plain CAN messages).

Anyway, most of what I have written is guessing at the functionality your master needs, so it may not be that useful. You first have to start with the master functionality then go from there.

Andy