Host Engineering Forum

General Category => DirectSOFT => Topic started by: redman1 on August 09, 2010, 06:36:03 PM

Title: Need Help
Post by: redman1 on August 09, 2010, 06:36:03 PM
I am new to the Direct Soft program. I have a program that currently tests the state of a switch (X1) and measures the on and off valves. The code is getting long and I know there is an easier way to do this, along with the fact that I need it to test four separate units at once.
Title: Re: Need Help
Post by: b_carlton on August 09, 2010, 07:27:10 PM
Quote
valves

Do you perhaps mean the on and off times?

Zip the various files (there are about 10 with common base names) and post the zip file here. We'll take a look.
Title: Re: Need Help
Post by: redman1 on August 10, 2010, 06:13:58 PM
b_carlton,
           Thanks for the reply, I am stuck and need to get this working in the next few days. What I have is a program that tests one unit and I need it to test four of the same units, the same way at the same time. I have attached a schematic also if that helps. Thanks again for the help.
Title: Re: Need Help
Post by: redman1 on August 10, 2010, 06:15:28 PM
Sorry that was values not valves.  :D
Title: Re: Need Help
Post by: redman1 on August 16, 2010, 01:29:15 PM
b_Carlton

     Here are the two files.
Title: Re: Need Help
Post by: Controls Guy on August 16, 2010, 02:37:22 PM
What I have is a program that tests one unit and I need it to test four of the same units, the same way at the same time. I have attached a schematic also if that helps. Thanks again for the help.

You should be able to generate all the input signals once and input them in parallel to all four DUT's.  The outputs (clutch coil drive signals) will need to be monitored separately for the individual unit's reaction to the inputs.  The overcurrent status is an input as well, and would need to be simulated individually, but it's the current in the output line, which already needs to be separate.

So you need to create some kind of sequence that simulates all the variations in the input lines.  Then parallel code or a subroutine called four times with different addresses to monitor the DUT's reaction to the stimulus.  You could do it with stage but I'm not a big fan of stage.  I'd use a drum (DRUM, EDRUM, etc.) or some timers and other logic.

You might want to consider adding an automatic acceptor/rejector rather than pass/fail indicators, to eliminate the possibility that the operator will get tired and sort the outgoing parts incorrectly.  Plus maybe an MMI to show the totals count and percentages accepted and rejected and the distribution of rejection causes.  This can help in diagnosing the cause of a rash of failures and aid in process improvement and the tracking of it.