Com'X 200 logged data

[dborle]

Hi there,

We have an installation with 3 Conext TL grid-tie inverters that are connected over Modbus RTU to a Com'X 200 and a 4-20mA solar sensor which is directly connected to the Com'X. The Com'X has Firmware V1.0.14.

For the Conext TL we had to create a custom device type. The data is logged every 15 minutes and send once per hour to EO.

No we found the following strange behaviour:

In the XLM file which is send to EO we have different timestamps for all of the devices. Eg two Conext have logged data from 06:00 until 06:45 and the third one and the solar sensor from 06:15 until 07:15

Has someone else noticed a similar problem?

Thanks

Daniel

[Anonymous user]

Hello Daniel

What is the destination platform (where data are published)

Could it be possible to have a copy of the backup file

Regards

Jef

[dborle]

Hi Jef,

The destination platform is Energy Operation. Unfortunately I don't have a backup file and nobody is on site. But I can see with my colleague who has programmed the Com'X.

The only thing I can provide you for the moment is a copy of the XML file which is sent to the Energy Operation server.

Regards

Daniel

[Anonymous user]

if it was possible to get the xml file, it should help

Regards

Jef

[dborle]

OK, I will send it by email

[Anonymous user · Accepted solution]

Daniel

This is due to the fact that the 2 processes ("data acquisition" and "data publication") are totally independant :

Example : let us imagine that we configure data acquisition with 15 minutes period, and data acquisiton with 1 hour period,

At 12:00, the first process ("data acquisition") is waked up and starts to collect data from the different slaves,

At the same time, the second process ("data publication") is also waked up and start to connect to the data publication site (eg a FTP server).

using "login", "password", "type", ... commands

Depending on the responce time of modbus slaves compared to the connection time of the FTP server,

We can understand that some time, the data publication process will send the logged data before than the last data in the last slave have been collected.

Nothing is lost in the data log, but the "late" data will be publlished at the next occurence of the data publication

Regards

[JamesAZZO]

Daniel,

This might be a bit of topic, but we are trying to integrate the Context TL inverters into a PME 7.2.2 installation and we can't find drivers. I'm just wondering if you would be willing to share the Modbus Driver for the Com'X 200 which might give us a head start?

Thanks.

James

[dborle]

Hi James,

Unfortunately we don't have any remote access to this site, what means, that someone has to go on site to get the driver. But I don't think, that it would help you a lot, as we are only reading the real energy of the Conext and that's it.

If you need the Modbus Register list, I can provide it to you.

Sorry

Daniel

[JamesAZZO]

Daniel,

Thanks. It was worth asking. 🙂

Yes, if you could just provide me the register list, we could whip something up.

Cheers!

James

[dborle]

OK, here we go!

You know: It's always worth for asking !

Daniel

[Anonymous user]

Hello James

Daniel mentionned the version was 1.0.14.

In this version there are no custom model (they have been added since version 1.1.x)

without the custom model, it will be difficult to "export" a device mapping model.