Skip to main content

ESEPRO and easYgen2000 - Knowledgebase / other - Power Generation

ESEPRO and easYgen2000

Authors list

This article might help, if you face communication issues between a Siemens PLC with ESPRO (CAN to Profibus) and might help you with replacements of GW4 applications


Changing Profibus Node Addrees of ESEPRO

Please make sure that you not already have changed the Profibus Node address to something else than 126 and also that your Profibus connection is working. You can use Hardware Config to search for all connected stations and the ESEPRO should identify with its assigned Profibus Address.

Note: Address 126 is the official Profibus Address for non-commissioned nodes as mandated by the Profibus standard. This node address cannot and must not be used in production and as such you cannot configure Hardware Config to use it. You must change the node address using Hardware Config's "Assing PROIFBUS Address" function as shown below:


You also can check the currently assigned Profibus Address using the ESEPRO's integrated web browser using an Ethernet cable and connect your browser to IP address 169.254.0.10. The latter is a good method do diagnose the status of the ESEPRO.



Assigning Node-ID and COB-ID
This entry is only required if you use index mapping which is more complicated. We suggest to start with direct mapping first.


How to assign Mux-ID, COB-ID for respective parameters like reading Voltage average(VLL Avg), Current Average, L1,L2,L3 phase wise current, L12,L23,L31 voltages, HZ, PF, KW, KWh. 

This depends on how you operate the ESEPRO. The simplest method would be direct mapping but you also can use index mapping. Direct mapping examples are found on page 12 of ESEPRO manual. I suggest to start with that first as it is the simplest method. The COB-ID should match the one you use in the easYgen (typically 385 for the first easYgen) and the Mux IDs you can look up in the easYgen2000 manual, section 9.2,1,1 Data Protocol 5100 (Basic Visualization)". Also refer to the ESEPRO manual showing an example how to obtain the Mux ID from the Data Protocol tables on page 13.