LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

NI-488 error connecting to driver or device

i m using "Legacy_get_historical_trend_info.vi" in my main vi it gives error out as defined in message subject.
this vi output goes to "Legacy_read_historical_trend.vi" which gives historical trend as output which is input for the
"Legacy_decimate_historical_trend.vi" that  which returns decimate trend as '0' and not giving correctly as time interval is 15 minute.
so plz kindly help me as early as possible for u.
thanks
dhanwanti
0 Kudos
Message 1 of 11
(6,635 Views)
Hello dhanwanti,

I couldn't find this vi neither in LV7.1 nor in LV8.0.1. So you should attach it here and we all will have a look at it.

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 11
(6,633 Views)
dear all
 already described vi are in following path of Labview 7.1 version
 
(Legacy_read_historical_trend.vi,Legacy_get_historical_Trend_info.vi,Legacy_decimate_historical_Trend.vi)
 
C:\Program Files\National Instruments\LabVIEW 7.1\vi.lib\lvdsc\historical\legacy.llb
 
these vi's i use in programming here i attach the  test sample of that.
so pls reply back why Legacy_decimate_historical_trend.vi always returns first timestamp as 0.
if any alternative of this problem is available then please reply
0 Kudos
Message 3 of 11
(6,621 Views)
Hello dhanwanti,

first: those vi's you are talking about seem to come with an additional toolset (DSC ?), which I don't have installed...

second: Can you give the error number for this error? I couldn't find it at a first test. Propbably this error number has two meanings, one for NI488, one for LabView internals. In this case maby the LabView internal error is the more important?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 11
(6,618 Views)
there is no error number for this problem but it shows warning after that system hangs up
warning message i attach here for your help please solve my problem as early as possible
 
 
 
 
0 Kudos
Message 5 of 11
(6,616 Views)
Hello dhanwanti,

does this trend has to start at Jan 1, 1904?
As I don't have those functions I cannot give you much more help...

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 6 of 11
(6,612 Views)

hi GerdW,

yes trend of  this vi starts from jan 1,1904 this is the main problem, if i gave start timestamp  as input then why should it take Jan 1,1904 as firstTime

and creates the memory problem for the system to hang.

pls help me as early as possible for u.

0 Kudos
Message 7 of 11
(6,604 Views)

hi GerdW,

if u don't know abt this problem much then pls tell me whom i contact for this.

it is ur company's reputation  question so pls  tell me the name of person whom i can expact that my problem can be solved.

thanks and regards,

dhanwanti

0 Kudos
Message 8 of 11
(6,602 Views)
Hello dhanwanti,

try to contact a local NI representative. At least here in Germany we can always call those guys by phone... And when they cannot help on their own, they should know who can help!

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 9 of 11
(6,598 Views)

Dear gerdW ,

can u pls give me the names and contact numbers of them or any email address of them .

i m very thankful to u .

so pls kindly help me

thanks

dhanwanti

0 Kudos
Message 10 of 11
(6,596 Views)