TAGs in BadTimeout after net fail

TAGs in BadTimeout after net fail

  • 30 gennaio 2020 alle 10:16 am #35493
    multilogic
    Partecipante

    Good morning, i’ve got an isuue, after a net failure (com GPRS ecc), i’m using a Modubus TCP protocol, all TAGs that non not have changed of value goes in BadTimeout. But if i read them thougt a modbus scanner i can see them correctly. Thanks for yours support.

  • 31 gennaio 2020 alle 3:35 pm #35495
    ThomasIslera
    Partecipante

    Hi Multilogic,
    Are you using the last version of the driver available in the Movicon.NexT 3.4.268 setup? ;or maybe you are using an old version? I know Progea R&D released recently a new version of the driver.
    If you restart Movicon NExT the problem is solved?
    Maybe there is some setting in the modbus gateway , anyway try to start by looking errors in the Movicon logs
    Regards
    Thom

  • 2 febbraio 2020 alle 12:57 pm #35498
    multilogic
    Partecipante

    Thanks Thomas, I’m using the last version of NEXT end i not remember this issue before. When i stop and restart server the tags are updated. If i change the value in the PLC by MODBUS SCAN, NEXT refresh the TAG and clear the error of timeout.

  • 3 febbraio 2020 alle 5:26 pm #35502
    Brian_73
    Partecipante

    Hi
    Any error in the logs? I’d say a detailed analysis starts here.
    It could be a timeout issue , timeout must be configured in a good way when using a gateway. I mean try to set an higher timeout in the GPRS gateway (e.g. 10seconds) and higher in the Movicon driver (e.g. 12 seconds) .

    BR
    Brian

  • 4 febbraio 2020 alle 8:43 am #35506
    multilogic
    Partecipante

    Hi Brian, were can i find the log for MODBUS connection?

  • 6 febbraio 2020 alle 10:27 am #35513
    Brian_73
    Partecipante

    Hi,
    You can view the driver logs directly by inserting the toolbox object Alarm Viewers > Historical Log Viewer.
    You can filter driver errors in the object properties , Filter Event Type > Drivers

    In addition all these information are automatically recorded in the SQL DB in the project table UFUAAuditLogItem.

    I hope to be of help!

    BR

    Brian

  • 6 febbraio 2020 alle 7:48 pm #35545
    multilogic
    Partecipante

    The error is: “ModbusTCP, Stazione STATION_3 in Errore : Timeout intervenuto. (ModbusTCP.Station=STATION_3|LinkType=0|FC=2|SA=41999|File=0)”. But the station and the TAG is alive and readable by any MODBUS READER, and the value of the locatio(INT32Bit) is stable and invariate.

  • 6 febbraio 2020 alle 8:31 pm #35546
    multilogic
    Partecipante

    Exscuse me i didn’t wrote before, the others TAGS of the same STATION ,with changed value, work fine, only the stable and invariate TAGS have this issue.

  • 11 febbraio 2020 alle 12:23 pm #35647
    MODERATOR
    Amministratore del forum

    Dear Sir,
    By considering the specificity of your request ( seems to be a problem due to the configuration of communication tasks & Controller memory areas ) I can suggest You to open a support ticket on our website so that You can interface directly with the Progea Technical Support Team.
    In this way we can technically investigate the problem at a higher level of detail. The Progea Technical Support Team will be happy to help you in solving the specific problem by analyzing the backup of the project, the logs and all the information they will ask you if necessary.
    Best Regards

Devi essere loggato per rispondere a questa discussione.

Topic Tags