Support Forum: Neosoft DQMH TestStandifier

[CyGa]

You could rename your own built PPL.

I never advise to a code module both in LV and TS. If you build a TS UI in LV and call a VI in your sequence that is also used in yout UI, you'll have a collision (VI already reserved by your UI).

It will work as long as you are using the Sequence Editor but not anymore if you build your own TS UI.

[python007]

Hey thanks for your fast reply

I don't want to use the DQMH Module parllel in TestStand and LabVIEW. We develop our Hardware Drivers as DQMH Modules.

And this Modules can be used in TestStand and also in LabVIEW Standalone Applications.

So for this case I need two PPL's?

Best regards

[CyGa]

You could use only one PPL, the one you already build.

But you'll face all caveats described in my presentations.

If you want to tailor a specific experience with TS, then using the TSifier makes it easy to do so.

In that case you would have one PPL for LV and one PPL+seq for TS.

The TSifier does not modify your Main.vi, so everything you tested with LV is left untouched.

[python007]

Hey CyGa

---

@CyGa wrote:

In that case you would have one PPL for LV and one PPL+seq for TS.

---

 So I would try it like you said.

Thanks for your support.

[bienieck]

Ok the termination monitor injection explanation seems reasonable. However, 30 sec timeout is a bad design IMHO. But that is a separate subject.

[CyGa]

30sec ? Which 30sec timeout?

The R&Rd are modified to include the Termination Monitor but the timeout set in the request is kept from the DQMH design. So if you have a 30sec timeout it means you set that value in your design.