This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Connection to Citect using SCADA Connect

Hi,

I can successfully connect to our Citect server however when I try to pull historical data I get an error code 347 message. (I'm using WaterGems Select series 5)

Assertion did not succeed in user Cicode occurred when calling ctFindFirst(CTAPITrend( "08:47:00 ", "13/10/2015",464,1000,1,"RTU12_WTR_FLW_RT")) for signal RTU12_WTR_FLW_RT.

I can pull real time data from Citect into WaterGems but for some reason historical data is hit and miss. My theory is that it has to do with the date format in that Citect uses mm/dd/yyyy format while WaterGEMS uses dd/mm/yyyy format

Any assistance is greatly appreciated

Thanks

Matt

Parents
  • Hello Matt,

    First, make sure that you are running the 32-bit version of WaterGEMS when you are doing this. The following link may be useful as well: communities.bentley.com/.../scadaconnect-using-citect-server-as-data-source

    I don't believe that you can change the month and day format in WaterGEMS, but can you change this in your Citect system. If not, it would be good to know if the historical data that doesn't work includes items that would have an invalid month listed, such as 13/10 (for October 13), and that data that does work have valid months, such as 12/10 (for October 12). For that data you do have, you may be able to compare the SCADA data imported into WaterGEMS compared to the data in your SCADA system. If data for 12/10 is, in fact, data for December 10 instead of October 12, that would confirm the issue as well.

    Regards,
    Scott
Reply
  • Hello Matt,

    First, make sure that you are running the 32-bit version of WaterGEMS when you are doing this. The following link may be useful as well: communities.bentley.com/.../scadaconnect-using-citect-server-as-data-source

    I don't believe that you can change the month and day format in WaterGEMS, but can you change this in your Citect system. If not, it would be good to know if the historical data that doesn't work includes items that would have an invalid month listed, such as 13/10 (for October 13), and that data that does work have valid months, such as 12/10 (for October 12). For that data you do have, you may be able to compare the SCADA data imported into WaterGEMS compared to the data in your SCADA system. If data for 12/10 is, in fact, data for December 10 instead of October 12, that would confirm the issue as well.

    Regards,
    Scott
Children