Run issues

[BOB64]

I have a worksheet that I developed that runs a single 400hp AC motor test stand and I am having issues with the program stopping, without warning. If I run the program but do not enable the motor it runs fine, goes thru all of the steps commanded by the Sequence generator, but as soon after I start the motor spinning it will stop.

The only thing that I can think of right now is that the sample rate is too high and the block size is too small. Running at 200hz w/ a block size of 16 for all of my other programs and it has been fine. I have even tried as slow as 50hz / 50 block size, and this has gone for a bit but eventually crashed the flow as well.

In the help files it states there is an option to “show the Dasylab system capacity usage (ratio of needed CPU time and Max available CPU time)”

I have not been able to find this option.

I am interfacing thru a IOtech Daqbook 2020

the attached program is one of 9

Thanks

[TomRizzo]

Hello,

Could you download a module withou the hardware interface?

I do not have the IOTech driver so I cannot open it.  A screenshot will be fine as well

In any case, when it stops, dos it with an error message?

[BOB64]

Tom,

As to when it stops – no it does not send an error code or any reason as to why it stopped.

Here is the flow in screen shots

There will be quite a few - sorry I wasn't able to remove the driver

the screen shots are

Main flow #1

Main flow #2

BlackBox00

An Input 1

An Input 2

Duty Cycle 1

Cycle Count

Controls

Dig Outputs

The main flow #1

 

 Main Flow #2 

 

Now for all of the Black boxes

 BlackBox00

 

An Input 1

 

An Input 2

Duty Cycle 1

 

Cycle Count

 

Controls

 

Dig Outputs

 

Thanks

[CJ_Butler__DASYLab_Pro]

There is a setting in the Options - Global Settings to turn on the performance monitoring.

Then, while running, go back to the Options menu, and select the display monitoring option. 

I'm not at a computer with DASYLab, so I cannot tell you the exact names for the option.

Also, check the setting for Blocked data -- also in global settings. You can view the state of the worksheet data on wires by activating both of the View - Animation options.  A lot of red on a module output is a diagnostic that tells you that data is not being processed downstream. 

Without having the hardware, I would check the following:

- are the computer power options disabled? 

- the status of the data wire animation (above)

- how long is the data filename? Does the location exist? 

- how much memory is on the computer? Use the Task Manager to monitor memory and CPU performance

[BOB64]

CJ ... my responses are in red

There is a setting in the Options - Global Settings to turn on the performance monitoring.

I am assuming you mean the “Global Setup” and “Compute module benchmarking”

Then, while running, go back to the Options menu, and select the display monitoring option. 

 Module benchmarking - when running I am getting a average loop time of 7ms and I ran the last flow at 100hz and a block size of 64

I'm not at a computer with DASYLab, so I cannot tell you the exact names for the option.

Also, check the setting for Blocked data -- also in global settings. You can view the state of the worksheet data on wires by activating both of the View - Animation options.  A lot of red on a module output is a diagnostic that tells you that data is not being processed downstream. 

 Do you mean “limit data flow FIFO size” I have checked this and it might make it go a little longer but it still crashes.

Without having the hardware, I would check the following:

- are the computer power options disabled? Yes

- the status of the data wire animation (above)

There is very little “Red” in any of the flow with the FIFO state on

- how long is the data filename? Does the location exist? 

C:\data\Duty Cycle\DEFWRITE_xxxxxx.ASC   is the path where I am writing to.

- how much memory is on the computer? 125GB Free

- Use the Task Manager to monitor memory and CPU performance

With the “Release CPU time if Idle”  checked I am getting between 2% - 6% used and without it checked ~ 50% used

Is 7ms too long of a compute time for each loop of the system, I did reconfigure my sequence generator black box to combine most of the action modules into two modules. this decreased the loop time to just over 2ms but the flow still crashed.

Any ideas appreciated

Thanks

Jason.

[TomRizzo]

Jason,

I hate to says this but you need to troubleshoot it on site.  The way you showing the problem, the solution could vary from a noise generated by the motor causing the computer or DAQ to go a litle crazy to a ptoblem with some drivers.

It is a problem that look difficult to troubleshoot in a forum.

[BOB64]

Tom

I was showing all of the different flows in my worksheet; sorry I wasn’t trying to make it look too complicated, just didn’t know if being so large would pose a problem.

The only difference between this flow and previous flows is in the Sequence generator black box

The main difference between the past and this current flow is that I have changed how I control the speed and pressure. Previously I used the analog out on the seq gen to control the pressure, now I have it controlling the motor.

I have re-run previous flows and they have run fine, this current flow crashes only when one switch enabling the motor turned on

I will be checking the physical wiring today, looking for a loose or frayed wire.

Any other ideas as to where to check?

Jason.

[TomRizzo]

One thing I would do is sync the switches with the relays input signals.  if you go to the option of the switch, use the sync as input instead of the driver and then connect it to any of the signals that go into the relays.

I would sugget to you to do it for all the switches that controll a relay