How to turn off the new LV7 error probe while debugging?

[pawel]

Hello All

Every time I restart LV7 and want to place a probe on error wire it places the new fancy (i.e. not working properly) error probe. In order to place old fashion (i.e. working great) error probe I need to right click select custom probe and choose generic probe.
Is there any way to make a generic probe to be the default one?
thanks in advance
Pawel

[KyleBryson]

Hi Pawel,

I do not believe that there is a method for changing the default error probe. Once you make the selection of the generic probe, LabVIEW will default to that, but does not remember this when closed and restarted. I apologize for the inconvenience.

If you have any more questions or would like to report a specific problem with the smart error probe, please reply with more information.

Thank you,
Kyle Bryson
National Instruments

[pawel]

Hello Kyle

Thank you for your answer, which BTW is not what I expected. The new smart probe is not so smart, I believe, since it must be placed before the data flow reach the probe. The old generioc probe will read the wire contents even though I placed it after the dataflow passes the wire.
That is my biggest problem which successfully prohibits from using the new probe.
Now every time I need to click three times more, if I rememeber. If I dont, I need to close smart probe and place a generic again. That takes time. In case of troublefull application, when I need to restart LV quite often this msart probe realy gives a lot of time lose.

Since I am complaning I must say that most of the inventions in LV7 does not work for me. Fancy icons for controls,
strange looking bad wires, completelly useless menu, etc. The only reason why I stick to LV7 is the dynamic events. Otherwise I will uninstall it ASAP. I guess that NI forgot about programmers which do LV for a living not for fun.

kind regards
Pawel

[Wiebe@CARYA]

Hi,

As I too program LabVIEW for a living, let me just say I just love every
thing about LV7.

The improved picture control, the grid, auto selection tool, custom probes,
just everything. Most new things can be turned off (Like "show red Xs on
broken wires" for the strange looking broken wires and "Place front panel
terminals as icons" for the large terminals).

A custom error probe can be made to look almost exactly like the old
(attachment). Only difference I could spot is the label. The generic probe
copies the label of the wire when created, the smart probe needs to be run
first.

> The new smart probe is not so smart, I believe, since it must be placed
before
> the data flow reach the probe. The old generioc probe will read the
> wire contents even though I placed it after the dataflow passes the
> wire.
I don't see what you mean by this. I've never noticed anything regarding
this.

Regards,

Wiebe.

"pawel" wrote in message
news:50650000000500000036640100-1077587809000@exchange.ni.com...
> Hello Kyle
>
> Thank you for your answer, which BTW is not what I expected. The new
> smart probe is not so smart, I believe, since it must be placed before
> the data flow reach the probe. The old generioc probe will read the
> wire contents even though I placed it after the dataflow passes the
> wire.
> That is my biggest problem which successfully prohibits from using the
> new probe.
> Now every time I need to click three times more, if I rememeber. If I
> dont, I need to close smart probe and place a generic again. That
> takes time. In case of troublefull application, when I need to restart
> LV quite often this msart probe realy gives a lot of time lose.
>
> Since I am complaning I must say that most of the inventions in LV7
> does not work for me. Fancy icons for controls, strange looking bad
> wires, completelly useless menu, etc. The only reason why I stick to
> LV7 is the dynamic events. Otherwise I will uninstall it ASAP. I guess
> that NI forgot about programmers which do LV for a living not for fun.
>
> kind regards
> Pawel



[Attachment SmartErrorProbe.vi, see below]

[pawel]

Hello Wiebe

I know most of those things can be turned off, so I did. The thing which cases my problem is the mentioned probe. I will try to explain it to you. See the enclosed picture.

In the picture You can see two error probes placed after the dataflow passed the wire and stop at the brakepoint. The new fancy (notworking) probe shows no error even though there is apparent one. The other generic probe placed also after the data passed the wire shows the current state of the wire, which is an error.
I hope now you understand my problem.

I am a little supprised you have not noticed it before, or maybe you thought that there is no error as the probe shows :)).

kind regards
Pawel

[Wiebe@CARYA]

Pawel,

Now I see it. I guess I just never used probes and brakepoint in a
combination like this!

So I guess making a probe look like the old one just complicate things,
since there is even less distinction...

Thanks for clearing it up!

Regards,

Wiebe.


"pawel" wrote in message
news:50650000000500000049640100-1077587809000@exchange.ni.com...
> Hello Wiebe
>
> I know most of those things can be turned off, so I did. The thing
> which cases my problem is the mentioned probe. I will try to explain
> it to you. See the enclosed picture.
>
> In the picture You can see two error probes placed after the dataflow
> passed the wire and stop at the brakepoint. The new fancy (notworking)
> probe shows no error even thoug
h there is apparent one. The other
> generic probe placed also after the data passed the wire shows the
> current state of the wire, which is an error.
> I hope now you understand my problem.
>
> I am a little supprised you have not noticed it before, or maybe you
> thought that there is no error as the probe shows :)).
>
> kind regards
> Pawel

[Wiebe@CARYA]

Pawel,

And now for a solution (there is one)...

It is so simple, it seems too easy. Just delete (don't rename, LV picks
through that, even if you rename the extension) or move the VI

C:\Program Files\National Instruments\LabVIEW 7\LabVIEW
70\vi.lib\_probes\default\ConditionalErrorProbe.vi

That worked for me! (But I tried some additional things first that might
have affected this.)

Regards,

Wiebe.



"Wiebe@CARYA" wrote in message
news:404864cd@newsgroups....
> Pawel,
>
> Now I see it. I guess I just never used probes and brakepoint in a
> combination like this!
>
> So I guess making a probe look like the old one just complicate things,
> since there is even less distinction...
>
> T
hanks for clearing it up!
>
> Regards,
>
> Wiebe.
>
>
> "pawel" wrote in message
> news:50650000000500000049640100-1077587809000@exchange.ni.com...
> > Hello Wiebe
> >
> > I know most of those things can be turned off, so I did. The thing
> > which cases my problem is the mentioned probe. I will try to explain
> > it to you. See the enclosed picture.
> >
> > In the picture You can see two error probes placed after the dataflow
> > passed the wire and stop at the brakepoint. The new fancy (notworking)
> > probe shows no error even though there is apparent one. The other
> > generic probe placed also after the data passed the wire shows the
> > current state of the wire, which is an error.
> > I hope now you understand my problem.
> >
> > I am a little supprised you have not noticed it before, or maybe you
> > thought that there is no error as the probe shows :)).
> >
> > kind regards
> > Pawel
>
>

[pawel]

Hello Wiebe again

You are perfectly right. I have removed the file you mentioned and my old generic probe came in the place.

Thank you very much,
I quess we should not mention it to Kyle :)))).

kind regards
Pawel

[Greg_McKaskle2]

> Since I am complaning I must say that most of the inventions in LV7
> does not work for me. Fancy icons for controls, strange looking bad
> wires, completelly useless menu, etc. The only reason why I stick to
> LV7 is the dynamic events. Otherwise I will uninstall it ASAP. I guess
> that NI forgot about programmers which do LV for a living not for fun.
>

Not completely forgotten, but there were a number of experiments to try
and make LV more friendly to new users. If you find that you don't need
the training wheel features -- as I like to call them -- you can turn
most of them, or hopefully all of them off in the Tools Options dialog.
If you poke around a little, you will find them, or you can ask, like
you did for the probe.

A
nd if it isn't in there, many things, like the probe are actually
written as VIs and can be disabled via other means.

Greg McKaskle

[KyleBryson]

> I quess we should not mention it to Kyle :)))).

Hello all,
🙂 It appears that I should have said that there is no supported way to change the default behavior. As you all have discovered, there is no setting for disabling the smart probe in the 'training wheels' options. I am a bit surprised the behavior when the file is missing is to revert quietly to the old one, but I'm glad that you found a workaround for your problem.

Thanks for the additional info on why you are not satisfied with the default probe. The 'smart' error probe does not work after the data has passed because the probe is actually a VI. The VI receives the error as an input when the error reaches the probe in the d
ataflow. The older probe is a simpler intrinsic structure that does not follow the behavior of a VI.

This issue has been documented, and change of the 'smart probe' behavior will be considered for future development. Thanks again for the information and the workaround.

Have a good day,
Kyle Bryson
National Instruments