Why SignalExpress is Unable to Recall User Assigned Scope Channel Names in STEPS After Saving Project?

[mander]

Why doesn't SignalExpress remember/recall assigned DPO4034B scope channel names in STEP window/program after saving Project? I am using two DPO4034B Tektronix Scopes connected to Win7 computer through ethernet connections. Though SignalExpress is able to communicate with scopes, upon SignalExpress software startup, it assigns incorrect scope channel names which subsequently corrupts STEPS in program/window. Also, this issue occurs with or without Tektronix scopes turned on. PLEASE ADVISE!

Regards,

Michael

[Philosophe]

Hey mander,

A few preliminary questions...

1) What version of SignalExpress are you using?

2) Can you post some screenshots of the issue as a whole? The results before and after the issue occurs.

3) Is there any error message or code that pops up?

4) Have you tried making a new project just to see if the project files were not corrupted in any way?

Feedback on these questions would be appreciated.

[mander]

Hello Rob,

Thank you for your response. FYI: I have already gone through some major trouble-shooting with Tektronix support (Morgan A.). It appears SignalExpress Software does not remember scope channel names I have assigend even after saving Project. With or without Tektronix scopes turned on, SignalExpress takes 3-5 restarts before it finally recalls correct channel name assignments.

Answers:

1) What version of SignalExpress are you using? Version 2.5.1

2) Can you post some screenshots of the issue as a whole? The results before and after the issue occurs. (see attached)

3) Is there any error message or code that pops up? Missing Input: “One or more of the inputs to this step are not selected . . " again due to SignalExpress not remembering assigned channel names corrupts subsequent STEPS.

4) Have you tried making a new project just to see if the project files were not corrupted in any way? Yes.

[Philosophe]

Michael,

Try creating the task in NI MAX as a workaround. From here you can manually assign the name for each task and each channel you are using. This article is a good starting point for trying to implement this.

http://digital.ni.com/public.nsf/allkb/F28C6BD62B0ED68F86257A6B00733E0E

Let me know if this works.

In addition, make sure you have the correct and up-to-date drivers installed as well.

[mander]

Hello Rob,

All drivers are up to date . . . If we had more time, we could try your workaround. Unfortunately, we are all now too busy packaging equipment (entire lightning simulation/generator facility) for upcoming export date. From your suggested workaround, does this mean that the issue of SignalExpress not remembering assigned channel names is a bug in the software? If it is a bug, will someone at NI or Tektronix ever fix it?

Regards,

Michael

[Dennis_Knutson]

I've never used SignalExpress z but I do know that a DAQmx task in MAX has nothing to do with a scope measurement.

[Philosophe]

That is quite possible. I am looking into this issue deeper and do more research to confirm the bug or not. In the mean time, are you using LabVIEW to interface with your readings? Or are you exclusively using signal express to read from the O-scopes?

I am also trying to see if there is any information from the Tektronix side that could be helpful as well. I'll keep you posted if I find out anything new.

[mander]

Hello Rob,

We are just using SignalExpress for scope communication.

Regards,

Michael

[Philosophe]

Ill keep you posted once I discover anything