[Mikhail]

Good news!

[Mikhail]

It was a provider failure because of electricity break. Now it works. The first long interruption of service for several years of good operating. Thanks for noticing.

[Mikhail]

Communicator works as system user, so it uses culture settings for “system”. I don’t recommend to change it, it may cause side effects. It’s just displaying that doesn’t affect real data.

You should open Administrator – Tools – Language and set fr-FR to apply culture settings to Rapid SCADA GUI and web interface. But currently the language pack doesn’t contain French. So settings affect date and number formatting. If you decide to create a translation to French and share it, I will assist you.

[Mikhail]

Dear Mr.Han,
May be you should check timeouts.
Nothing changed in communication logic.

[Mikhail]

Hello,

The screenshot is not available. Please upload it again.

[Mikhail]

Hi,

What Rapid SCADA version do you use?

[Mikhail]

joeh6966, you should define the views exactly as it’s shown in the videos. No *.rsproj files there.

[Mikhail]

Read the document mentioned above. First, install new Rapid SCADA on another machine to test. Follow the document to convert the project.

[Mikhail]

Upgrade from v5.6 to v5.8 is similar.

[Mikhail]

The default user Admin has full rights despite you fill the Rights table. Make sure that the view is opened if Admin is logged on.

[Mikhail]

Do I need to try out the Automatic Control Module to get what I want?

I think you should use formulas.
Do you get correct double value in Communicator?

[Mikhail]

I only need to read 4 registers 5 times a day.

Set the period like written here to poll on time.

[Mikhail]

Root cause will be clear when the problem is solved.

[Mikhail]

The provided screenshots don’t contain any error.
Look for communication line log.

[Mikhail]

It’s possible to develop a native driver, but may be expensive.
Have you directly asked the manufacturer about the OPC?

[Author]

Posts