Hello!

I am having problems with my VB Script not working as i want it to do, i am looking for suggestions on how to solve my problems

I am working on creating a test bench for our products and i need to log process values into datalogs.

I am able to run multiple products at the same time but my problem comes when im trying to save the datalogs. I am calling a script after my test is finished that goes as following:

If SmartTags("AC_1_Datalog_Enable") Then

StopLogging hmiDataLog, "Actuator1"

CloseAllLogs

ArchiveLogFile hmiDataLog, "Actuator1", SmartTags("AC_1_ActuatorNamn"), hmiCopy

ClearLog hmiDataLog, "Actuator1"

OpenAllLogs

ResetBit "AC_1_Datalog_Enable"

ElseIf SmartTags("AC_2_Datalog_Enable") Then

StopLogging hmiDataLog, "Actuator2"

CloseAllLogs

ArchiveLogFile hmiDataLog, "Actuator2", SmartTags("AC_2_ActuatorNamn"), hmiCopy

OpenAllLogs

ResetBit "AC_2_Datalog_Enable"

End If

The script works fine if i only run 1 actuator test at a time, but as soon as i try to run 2 tests at the same time it will only save 1 of the datalogs. I am not calling the script at the same time but with approximately 15 seconds difference. 

Whenever i start my test i do the following commands

OpenAllLogs 

StartLogging Actuator 1

I am suspecting that CloseAllLogs and OpenAllLogs are part of the issue but i do not know how to resolve this. Any suggestions?

I will have a look at the page you linked, i do not understand what you mean by waiting a little bit, maybe i explained it poorly but i am not calling the script at the same moment, there is a long time delay between calling the script. 

The test process for multiple actuators running goes as following:

Start test 1 button :

OpenAllLogs
StartLogging Actuator 1

I then start the next test with another button 

OpenAllLogs

StartLogging Actuator 2

When a test is finished i call for the script above.  

There is a time delay of approx 30-60 seconds between calling the script

I tried creating two different scripts for the different tests but that also seemed to cause problems with the 2nd log not saving properly.

I hope i explained it well enough for you to understand what im trying to achieve, any suggestions on how to solve my problem? 

If you are trying to log both a and b on same script it wont work ever. The else if wont never get executed if first one is.

Not related to the first point.

Those functions are asychronous, so like Murof mentioned you should wait before executing next function. 

You can use system events to fire next one, or create a function that waits (does nothing in a while loop for few seconds), I would not recommend to create waiting scripts because only one script can execute at time.

Prof. Frink

Hi uber123123,

when do you set "AC_2_Datalog_Enable" resp. "AC_1_Datalog_Enable"?

Please test you script without "elseif", with two separate IF.

Regards,

Frink

AC 1 and 2 are set with separate buttons on the HMI Screen (i set them when i start each test) 

I tried your suggestion, the 2nd datalog still does not seem to save correctly. 

This is what i do when i start my test

This is what i do when end my test and call the script. 

Why does it seem like the script is never executing saving the datalog for AC2 even when the first IF condition in my script is not true? Could there be something wrong with how i close and open logs?

K_Ohjus

If you are trying to log both a and b on same script it wont work ever. The else if wont never get executed if first one is.

Not related to the first point.

Those functions are asychronous, so like Murof mentioned you should wait before executing next function. 

You can use system events to fire next one, or create a function that waits (does nothing in a while loop for few seconds), I would not recommend to create waiting scripts because only one script can execute at time.

I noticed this seemed to be the issues that the logs would not close correctly before starting to archive resulting in bad log files. How do i "use system events to fire the next one"?

I tried to simply do the next command on the incoming event but that does not seem to work. 

I have never worked with system events before.  I checked with only 1 actuator to save log file by doing the following commands

StopLogging hmiDataLog, "Actuator1"

CloseAllLogs

ArchiveLogFile hmiDataLog, "Actuator1", SmartTags("AC_1_ActuatorNamn"), hmiCopy

ClearLog hmiDataLog, "Actuator1"

OpenAllLogs

It seems like the following system events are triggered when saving correctly

80026 (Log initialization ended. All logs OK)

80019 (All logs have been closed successfully.) 

80048 (The log '%1' was successfully exported to '%2')

Is there any way to use the system events in my vb script to trigger the next command or how do i set it up correctly in system events?

Some further help to troubleshoot. I understand the timing problem now with my initial script. Question remains how to resolve the issue with system events. 

The following script produce these messages when trying to save logs

Then use system function to archive your file. Put archiving in to the event

80019 All logs have been closed successfully.