Valid MSCONS files in the incoming folder of the EDIFACT service are automatically processed by visual energy 4 and the measured data contained are imported with the requested OBIS code. This service uses the recipient ID defined in the MSCONS file to check which component (visual energy 4 web / bus master, etc.) the file belongs to. For this reason, the recipient ID in the MSCONS file containing the market participant has to be identical to the recipient ID in the Participants.xml file.

At short intervals, the visual energy 4 EDIFACT service checks and then answers the request using the corresponding CONTRL (syntax and service report messages for automatic EDI processing), APERAK (application error and acknowledgment messages) as well as MSCONS files.

EDIFACT requests can be sent to visual energy 4 web as well as to the bus master.

Note for administrators:

The input folder is defined in the App.config file:

<addkey="inFolder" value="D:\Temp\edifact\In/>

The same applies to the working directory:

<add key="workFolder" value="D:\Temp\edifact\Work"/>

The answer is sent to a market participant known to the system. The market participants are defined in the Participants.xml file in the working directory. visual energy 4 is always given the ID '0000000000000'.

<?xml version=1.0" encodig="utf-8"?>

<ArrayofMarketParticipant xmlns:xsi="http://w3.org/2001/XMLSchema-instance" xmlns:xsd=:"http://w3.org/2001/XMLSchema">

  <MarketParticipant>

    <ID>0000000000000</ID>

    <Name>This email address is being protected from spambots. You need JavaScript enabled to view it.</Name>

    <CommunicationName>This email address is being protected from spambots. You need JavaScript enabled to view it.</CommunicationName>

    <CommunicationType>This email address is being protected from spambots. You need JavaScript enabled to view it.</CommunicationType>

  </MarketParticipant>

  <MarketParticipant>
    <ID>1234567890123</ID>
    <Name>Extern</Name>
    <CommunicationName>D:\Temp\edifact\out</CommunicationName>
    <CommunicationType>File</CommunicationType>
  </MarketParticipant>

...

The row for the working directory for CONTRL, APERAK and MSCONS is decisive for the export:

<CommunicationName>D:\Temp\edifact\out</CommunicationName>

The communication type has to be 'File':

<CommunicationType>File</CommunicationType>

You can import existing visual energy 3 database energy data. However, this process cannot be automated for various reasons and has to be done manually for each measuring parameter.

• The Web.config file has to include the connection string for the visual energy 3 database: (section: connectionString): <add name="VE3" connectionString="Data Source=PC_Name\VEDB;Initial Catalog=Datenbankname;Integrated Security=False;User ID=sa;Password=vedb" providerName="System.Data.SqlClient" />
• An 'Import' link is available in the properties area of the respective meter point. A new window is opened. Here, you can enter the eBus address or VEDB meter number to search for a table and import its data.