kcks66

Forum Replies Created

Viewing 15 posts - 16 through 30 (of 136 total)
  • Author
    Posts
  • in reply to: Convert historical data from V5 to V6 #14280
    kcks66
    Participant

    Hi Mikhail,

    I got the converter to run. However, I got many errors. The converter stop when encountered error. I need to remove those error .dat files and re-run the converter.

    https://ibb.co/wQHkqGF

    Is there a way to make the converter automatically re-run by skipping errors .dat files?

    By the way, why there is some error from v5 .dat file?
    Pls advice and thank you.

    in reply to: Current Data sudden become Not Ready #14247
    kcks66
    Participant

    Hi Mikhail,

    Today I purposely tripped the PC power supply and later resumed power supply. I can see Rapid SCADA instance Server and Communicator services status Starting and then Normal.

    I checked Achieve status is all Ready, and data is writing into PostgreSQL database normally.

    I will continue monitor until next PC actual sudden shutdown happen and update here.

    in reply to: Current Data sudden become Not Ready #14239
    kcks66
    Participant

    Hi Mikhail,

    Pls advice for if I configure Automatic (Delayed Start) for Rapid SCADA’s services? Do you think if I delayed the Rapid SCADA from start running for 1 ~ 2 minutes after PC restart can solve the problem?

    https://ibb.co/T2NSq4d

    Thank you.

    in reply to: Current Data sudden become Not Ready #14238
    kcks66
    Participant

    Hi Mikhail,

    Today the PC experienced power supply tripped. The Rapid SCADA Archive became Not Ready after PC auto restart when power supply resumed. However the MinCopy Achieve is Ready.

    https://ibb.co/R02v4yJ

    This round I stop and start SCADA-Serve without uploading the project. The Rapid SCADA Archive became Ready back.

    I use pgAdmin to connect to the database and open the data tables during Rapid SCADA Archive Not Ready, it just blank.

    Look’s like the Rapid SCADA Archive always become Not Ready if PC experienced shutdown and resume back, for Archive setup using PostgreSQL as main database.

    Pls advice for the counter measure can be taken to avoid this incident from happened again in the future.

    Thank you.

    in reply to: Current Data sudden become Not Ready #14225
    kcks66
    Participant

    Hi Mikhail,

    May be the error occurs after the computer restart? And PostgreSQL has not started yet?

    I managed to installed PC On/Off Monitor software into the PC and I found there was a PC shutdown exactly at that time. Kindly see below for the findings:

    https://ibb.co/9NgvPX4

    I think the PC restart is because there is Windows Update activities historical record found on 13/3.

    I believe we found the cause to make Rapid SCADA Archive suddenly became Not Ready. Pls advice for what setting should I do to make the Rapid SCADA or PostgreSQL to resume the data storing process after PC restart/resume?

    Thank you.

    in reply to: Current Data sudden become Not Ready #14222
    kcks66
    Participant

    Hi Mikhail,

    1) I am using PostgreSQL 16.

    2) Noted. I will stop and start SCADA-Serve without uploading the project, and use pgAdmin to check database if the error occurs again.

    FYI, the computer is left 24/7 without shutting down. I also enable MinCopy by using ModArcBasic just in case happen in the future I can cross check.

    in reply to: Current Data sudden become Not Ready #14214
    kcks66
    Participant

    Hi Mikhail,

    1) I couldn’t understand why PostgreSQL database suddenly shutting down?
    2) The Rapid SCADA’s Archive became READY back after I clicked the Rapid SCADA upload button. Pls advice the error is came from Rapid SCADA side or PostgreSQL database side?

    By the way, where should I check at PostgreSQL database/pgAdmin to search for error?
    Thank you.

    in reply to: Current Data sudden become Not Ready #14206
    kcks66
    Participant

    Hi Mikhail,

    The same error happened again:

    https://ibb.co/stJ9XrN

    This round I managed to capture the error log:

    2024-03-13 22:27:04 Enqueueing of 1401 data points completed successfully in 0 ms
    2024-03-13 22:27:04 Data queue has become empty
    2024-03-13 22:27:30 Enqueueing of 1401 data points completed successfully in 0 ms
    2024-03-13 22:27:31 Error writing to database:
    Npgsql.PostgresException (0x80004005): 57P03: the database system is shutting down
    at Npgsql.Internal.NpgsqlConnector.<ReadMessage>g__ReadMessageLong|223_0(NpgsqlConnector connector, Boolean async, DataRowLoadingMode dataRowLoadingMode, Boolean readingNotifications, Boolean isReadingPrependedMessage)
    at Npgsql.Internal.NpgsqlConnector.Authenticate(String username, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)
    at Npgsql.Internal.NpgsqlConnector.<Open>g__OpenCore|203_1(NpgsqlConnector conn, SslMode sslMode, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken, Boolean isFirstAttempt)
    at Npgsql.Internal.NpgsqlConnector.Open(NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)
    at Npgsql.ConnectorPool.OpenNewConnector(NpgsqlConnection conn, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)
    at Npgsql.ConnectorPool.<Get>g__RentAsync|28_0(NpgsqlConnection conn, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)
    at Npgsql.NpgsqlConnection.<Open>g__OpenAsync|45_0(Boolean async, CancellationToken cancellationToken)
    at Npgsql.NpgsqlConnection.Open()
    at Scada.Server.Modules.ModArcPostgreSql.Logic.PointQueue.ProcessItems()
    Exception data:
    Severity: FATAL
    SqlState: 57P03
    MessageText: the database system is shutting down
    File: postmaster.c
    Line: 2353
    Routine: ProcessStartupPacket
    2024-03-14 08:24:35 Reading of 1401 data points completed successfully in 81 ms
    2024-03-14 08:24:35 Enqueueing of 1401 data points completed successfully in 0 ms
    2024-03-14 08:24:36 Data queue has become empty
    2024-03-14 08:25:00 Enqueueing of 1401 data points completed successfully in 0 ms
    2024-03-14 08:25:00 Data queue has become empty

    I reupload again then the Achieve all became Ready back. Pls advice for what should I do to avoid this from happened again.

    Thank you.

    in reply to: New release Rapid SCADA 6.2.x #14202
    kcks66
    Participant

    Noted with thx.

    in reply to: New release Rapid SCADA 6.2.x #14196
    kcks66
    Participant

    Hi Mikhail,

    My PC currently runs V6.1.5. Can I directly update to V6.2.0 by skipping V6.1.6?

    in reply to: V6 Elastic Report #14181
    kcks66
    Participant

    Hi Mikhail,

    Not that everyday with record taken every one hour. I need everyday but record taken at 1:00am one record only, instead of current setting elastic report always everyday take at 0:00am.

    • This reply was modified 1 month, 1 week ago by kcks66.
    in reply to: V6 Elastic Report #14168
    kcks66
    Participant

    Hi Mikhail,

    I tried to use Exact and set ExactTimes as below, however I received error page:

    https://ibb.co/7bLCCRy

    My setting:

    <DataOptions>
    <!– Prepend additional time before the report start time –>
    <PrependTime>0:00:00</PrependTime>
    <!– Append additional time after the report end time –>
    <AppendTime>0:00:00</AppendTime>
    <!– Skip the first timestamp from output –>
    <SkipFirst>true</SkipFirst>
    <!– Skip the last timestamp from output –>
    <SkipLast>false</SkipLast>
    <!– Defines how timestamps are enumerated. Possible values: All, Step, Hour, Day, Month, Exact, BeginEnd –>
    <TimeDetailing>Exact</TimeDetailing>
    <!– Time step –>
    <TimeStep>1:00:00</TimeStep>
    <!– Times of day separated by commas –>
    <ExactTimes>1:00</ExactTimes>
    <!– Defines how the date and time column is displayed –>
    <ShowDatesOnly>false</ShowDatesOnly>
    </DataOptions>

    Pls advice and thank you.

    in reply to: V6 Elastic Report #14167
    kcks66
    Participant

    Hi Mikhail,

    I tried but still couldn’t get it sampled at 01:00:00. Can you provide example how to set?

    in reply to: ModDiffCalculator #14161
    kcks66
    Participant

    Hi Mikhail,

    I got the result in Minute archive as shown below:

    https://ibb.co/jfwNKx8

    I see every 30 minutes got data as expected. Somehow there is always 0 if out of HH:00:00 and HH:30:00. Is ModDiffCalculator working like this?

    The other part is data channel 102 always 0 in the Table, as below:

    https://ibb.co/hCxX9Gj

    Since the Channel 102 always show 0 I couldn’t use to attach to a Dynamic Text in Scheme as well as use as source channel for another calculated channel to further formula function.

    Pls advice for my ModDiffCalculator configuration:

    https://ibb.co/x6b1F1x

    Thank you.

    in reply to: ModDiffCalculator #14148
    kcks66
    Participant

    I should select custom period then is ok.

    <?xml version=”1.0″ encoding=”utf-8″?>
    <ModDiffCalculator>
    <GeneralOptions>
    <CmdCode />
    </GeneralOptions>
    <Groups>
    <Group active=”true” name=”30 Minutes” periodType=”Custom” customPeriod=”00:30:00″ offset=”00:00:00″ delay=”10″ archiveBit=”1″>
    <Item srcCnlNum=”101″ destCnlNum=”102″ />
    </Group>
    </Groups>
    </ModDiffCalculator>

Viewing 15 posts - 16 through 30 (of 136 total)