Triggering problems with picoscope 3205 (LabView)

Hi.
I have a problem trying to trigger my signal in order to see it clearly. My target is to measure a periodic signal of hundreds of microseconds. I have used the program ps3000_runStream and changed all constants to control. But the point is that some of them doesn't work properly and I am a begginner with LabView. I have tried using Picoscope 6 (Picotech's software) and all works, but I need to have the same in LabView because I am going to add some components to measure at the same time. My program is attached to this message.
Thanks
Attachments:
ps3000_runStream.vi ‏46 KB

Maybe your error is due to a wrong indication of trigger channel with respect to acquired channels list.
I quote for you some help taken from a LV example (Cont Acq&Graph (buffered) Hard A-Trig.vi):
"...With E Series devices, if your analog trigger signal is connected to one of the analog input channels, that channel must be first in the scan list of channels. If you are using named channels, the trigger channel must be the first channel in the actual hardware channel order, which may or may not be the first channel in the channel string control. This restriction does not apply if you connect the analog trigger signal to PFI0..."
Roberto
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

Similar Messages

I have problem with concept in labview

i have project active noise control using loudspeaker to cancel the noise i have problem with the cancellation any suggestion i will apperciate that . the code attatched if u could see and tell me what is the wrong thanks in advance
Solved!
Go to Solution.
Attachments:
ali clustring 2011 labview.vi ‏192 KB

Hi Ali,
i have problem with the cancellation
What kind of problem(s)? Could you describe them a little bit more detailed?
what is the wrong
Definitely "wrong" is that part of your code:
Why dou you need 4 functions where a simple IndexArray will do the very same job? (That programming style is called Rube-Goldberg...)
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Triggering problems with IMAQ PCI 1411 using NI-IMAQ 2.6 drivers

I am having problems with the NI-IMAQ triggering mechanisms. I would like to use imgSessionWaitSignalAsync to register a call-back function to be repeatedly called on rising edges on the external trigger line. Now the external trigger line is connected to a photocell that is low when there are no objects in front of it and is high when there is an object in front of it. Unfortunately, when running my application, the callback function is not always triggered when an object moves in front of the photocell, and it is often triggered when no object is in front of the photocell. The callback function is not called anywhere else in the code.
An engineer at my company hooked up an oscilloscope to the trigger l
ine and we found that the photocell performs as expected. So I am looking for help to ensure that every time an object starts to pass in front of the photocell, the callback function will be triggered.
System Details:
Windows 2000 PC
Visual C++ 6.0
2x IMAQ PCI 1411 installed(one is revision A, the other is revision C.) I have the same problem even if I switch to the other card.
NI-IMAQ 2.60.0 drivers
Thanks in advance,
Michael

Bruce,
In fact that was my problem. The XC-73 operates at 30 Hz. My strobe
lighting was not triggered at 30 Hz. Once they matched, the
interlacing problem I described went away.
-Shehrzad
Bruce Ammons wrote in message news:<506500000005000000634D0000-1004225886000@exchange.ni.com>...
> Shehrzad,
>
> What kind of lighting are you using? I have seen variations like you
> describe when using fluorescent lighting, and also with incandescent
> lighting when the frame rate didn't match the power frequency. I
> suspect you are right about the lighting. I can't think of any other
> reasons for the problem you described.
>
> Bruce

Problem with combination of LabVIEW classes (dynamic dispatch), statechart module and FPGA module

SITUATION:
- I am developing a plug-in-based software with plug-ins based on LabVIEW classes which are instanced at run-time. The actual plug-in classes are derived from generic plug-in classes that define the interfaces to the instancing VI and may provide basic functionality. This means that many of the classes' methods are dynamic dispatch and methods of child classes may even call the parent method.
- Top-level plug-ins (those directly accessed by the main VI) each have a run method that drives a plug-in-specific statechart.
- The statechart of the data acquisition plug-in class (DAQ class) calls a method of the DAQ class that reads in data from a NI FPGA card and passes it on to another component via a queue.
PROBLEM:
- At higher sampling rates, an FPGA-to-host FIFO overflow occurs after some time. When I "burden" the system just by moving a Firefox browser window over the screen, the overflow is immediately triggered. I did not have this kind of problem in an older software, where I was also reading from an FPGA FIFO, but did not make use of LabVIEW classes or statecharts.
TRIED SOLUTIONS (WITHOUT SUCCESS):
- I put the statechart into a timed loop (instead of a simple while loop) which I assigned specifically to an own core (I have a quad-core processor), while I left all the other loops of my application (there are many of them) in simple while loops. The FIFO overflow still does occur, however.
QUESTION:
- Does anybody have a hint how I could tackle this problem? What could be the cause: the dynamic dispatch methods, the DAQ statechart or just the fact that I have a large number of loops? However, I can hardly change the fact that I have dynamic dispatch methods because that's the very core of my architecture...
Any hints are greatly appreciated!
Message Edited by dlanger on 06-25-2009 04:18 AM
Message Edited by dlanger on 06-25-2009 04:19 AM
Solved!
Go to Solution.

I now changed the execution priority of all the VIs involved in reading from the FPGA FIFO to "time critical priority (highest)". This seems to improve the situation very much: so far I did not get a FIFO overflow anymore, even when I move around windows on the screen. I hope it stays like this...

Triggering Problems with a SCB-68 Terminal

Hello
I nedd some suggestions about triggering with a SCB-68 terminal.
I would like to make a triggered aquisition. I need to use to poles? That is, I nedd to connect the high digital pole (+5V) to the PFI0 screw terminal and the low pole (+0V) to the pin# 44 or is enough to connect the sole high pole to PFI0.
If I measure voltage between pin#11 (PFI0) and pin#44 (GND) I get +5 V. Is that correct? How can I trigger my acquisition with a digital signal of +5V if the PFI0 already is at +5V?
I don't understand
Hope someone kindly help me.
Thanks
Moreno

Thank you so much for the answer.
There was a bad explanation maybe. I'm really using a trigger form +0V to +5V. The most important thing that I would like to know is: is correct the between PFI0 and the pin#11 (DGND) there are +5V without any external connection (at open circuit)
Thanks a lot
Moreno

Problems with CAMAC and LabView 6.0

I have a Lecroy 2249SG adc with a DSP6001 control board. I upgraded from LabView 5.0 to LabView 6.0 and now my Sub vi's for communicating with the CAMAC do not work. The drivers were from DSP and were for Windows NT and a previous lab member modified them to work with Windows 98. I'm new to LabView and would appreciate any insights you may have. Thanks

The drivers are .dll files. When I send a LAM to the CAMAC, I get a Q=0 and/or a X=0 back from the CAMAC - Q=0 means no response, and X=0 means command not accepted. My previous lab member explained the modifications like this: "I remember that I somehow looked at the code and besides a lot of unintelligable symbols I saw things that looked like the expected CAMAC commands except that they had a lot of really strange extra symbols attached to them. I then went into LabVIEW and replaced the expected command names by these slightly messed-up versions and - surprisingly - it worked."
The company who supplied the drivers in the past no longer sells the control board, but I am trying to contact them for original drivers.
I'm attaching the dr
iver(WINCAM32.dll) and the vi that is used to generate the calls.
Thanks.
Shaun
Attachments:
CAMO.VI ‏27 KB
WINCAM32.DLL ‏1000 KB

Communication problem with FP-2000 and Labview 7.1

I am using the FP-2000, DO-403 and TC-120 modules with Labview 7.1, being run on a host computer via an ethernet connection. The setup has operated flawlessly for ~2 years; recently, I have noticed that while a VI is running on my PC, connection to the FP module ceases. There is no pop-up "connection error" in my VI, and the all the power and status LEDs on the FP modules are normal. I can still interact with the VI on the front panel while it is running, but nothing is passed to the FP module. I have tried communicating with MAX when this occurs and receive a "no connection" message. Is there a simple solution here, such as rebooting the FP module? Or is it time to invest in new hardware?
Justin

I am having a very similar problem with my cFP-1804 and Labview 7.0. I have no problem initiating communication over ethernet, and the vi will run perfectly for hours or even days. Inevitably, however, at some point there is no longer communication with the cFP-1804. Data is no longer being passed either to or from the cFP-1804, and MAX will show that the device is not connected. I also will not see any pop-up error message that says the connection has been lost, either from Windows or from Labview. The vi will just continue to run as if nothing has happened. Turning the power to the cFP-1804 off and then on will always resolve this problem. Since I am using the cFP-1804 primarily for data logging, however, this behavior is particularly problematic as the system will record nothing but zeroes until I discover that the communication has been severed and perform the manual power cycling.
I have been unable thus far to determine the cause of this problem. Any help would be greatly appreciated.
Thanks,
Derrick

Problem with Roles and Triggers

I'm having a strange problem with Roles and Triggers in Oracle. It's a little difficult to describe, so bear with me...
I'm trying to create a trigger that inserts records into a table belonging to a different user/owner. Of course, the owner of this trigger needs rights to insert records into this other table. I find that if I add these rights directly to the owner of the trigger, everything works okay and the trigger compiles successfully.
However, if I first create a Role and grant the "insert" rights to it, and then assign this role to the owner of the trigger, the trigger does not compile successfully.
To illustrate this, here's an example script. I'm using Oracle 10g Release 2...
-- Clean up...
DROP TABLE TestUser.TrigTable;
DROP TABLE TestUser2.TestTable;
DROP ROLE TestRole;
DROP TRIGGER TestUser.TestTrigger;
DROP USER TestUser CASCADE;
DROP USER TestUser2 CASCADE;
-- Create Users...
CREATE USER TestUser IDENTIFIED BY password DEFAULT TABLESPACE "USERS" TEMPORARY TABLESPACE "TEMP" QUOTA UNLIMITED ON "USERS";
CREATE USER TestUser2 IDENTIFIED BY password DEFAULT TABLESPACE "USERS" TEMPORARY TABLESPACE "TEMP" QUOTA UNLIMITED ON "USERS";
CREATE TABLE TestUser.TrigTable (TestColumn VARCHAR2(40));
CREATE TABLE TestUser2.TestTable (TestColumn VARCHAR2(40));
-- Grant Insert rights on TestTable to TestRole...
CREATE ROLE TestRole NOT IDENTIFIED;
GRANT INSERT ON TestUser2.TestTable TO TestRole;
-- Add TestRole to TestUser. TestUser should now have rights to INSERT on TestTable
GRANT TestRole TO TestUser;
ALTER USER TestUser DEFAULT ROLE ALL;
-- Now, create the trigger. This compiles unsuccessfully...
CREATE TRIGGER TestUser.TestTrigger AFTER INSERT ON TestUser.TrigTable
BEGIN
INSERT INTO TestUser2.TestTable (TestColumn) VALUES ('Test');
END;
When I do a "SHOW ERRORS;" after this, I get:
SQL> show errors;
Errors for TRIGGER TESTUSER.TESTTRIGGER:
LINE/COL ERROR
2/3 PL/SQL: SQL Statement ignored
2/25 PL/SQL: ORA-00942: table or view does not exist
SQL>
As I said above, if I just add the Insert rights directly to TestUser, the trigger compiles perfectly. Does anyone know why this is happening?
Thanks!
Adrian

Hi Raghu,
If the insert rights exist only on TestRole, and TestRole is assigned to TestUser, I can do the INSERT statement you suggest with no problems if I just execute it from SQLPlus (logged in as TestUser).
The question is, why does the same INSERT fail when it's inside the trigger?

I have a problem with simulation in Matlab 6.5 and LabVIEW for PID controllers

I have a problem with simulation in Matlab 6.5 and LabVIEW. I have some methods for granting PID controllers in MATLAB to go but not LabVIEW. International Teams degree to transfer two but when I go past the fourth degree no longer work. We changed the formula for calculating the parameters for grade four and gave me some good values for Matlab award but when I put on LabVIEW have not settled. formulas are available in PDF and are. Please help me and me someone if possible. Thanks
lim.4 generation parameters in MATLAB program and comparison methods are for second-degree transfer function.
Solved!
Go to Solution.
Attachments:
Pt net.zip ‏2183 KB

This is the VIs what i try to make,but is not work. This pdf. document was used to create last VIs PID. thenk you for your colaboration.
Attachments:
PID create by me.vi ‏312 KB
tut_3782.pdf ‏75 KB

Problem with Vision Builder and LabView: Error -1074395995, File not found

I have created an inspection with Vision Builder AI 2009 SP1. In it I load some pictures from the HDD and run some checks over it. It works fine. Then I have migrated it to LabView 2010, I get a message that the migration is successfull, but when I run the VI on LabView I get a fail status. I have been checking my program and I have found and error when I try to load the picture from file: Error -1074395995 occurred at IMAQ ReadImageAndVisionInfo
Possible reason(s): IMAQ Vision: File not found.
But I am not sure which file it refers to. At first I thought it was the picture I wanted to load, but I have checked the path and it is correct, so maybe it refers to another thing. What puzzles me most is that it works perfectly on Vision Builder and I have changed nothing in LabView, maybe it is a problem with the migration. Any clues?

Here's a screenshot of what I'm talking about. Put a break point here and see what the path is and compare that with what Vision Builder AI is using (described where to find this in the previous post). You could find where this global is used to make debugging easier.
Hope this helps,
Brad
Attachments:
Generated Code.png ‏43 KB

Problem with an old version of LabVIEW 4.0.1

Hi,
I'm rather new to this, so I appreiciate any help that you can give me. Our lab has an old computer running Windows 95 and LabVIEW v. 4.0.1. I would like to take one of the progams on this computer and run it on a newer computer in a different lab. This newer computer is running Windows 2000. I installed LabVIEW 4.0.1 on the Win2000 machine, and then copied the needed file onto this machine. However, when I try to run the program, I get the following error messages:
Error 7 occurred at Open File+.vi: Open File
Possible reasons:
LabVIEW: File not found.
OR
NI-488: Non-existant Board.
after that error I get this one:
Error - 10401 occured at AO Group Config.
Possible reasons:
NI-DAQ:LV The specif
ied device is not a National Instruments product, or the driver does not support the device (e.g., the driver was released before the device was supported).
Now, there are a couple reasons that I can think of that would cause these problems. First, LabVIEW 4.0.1 is not compatable with Windows 2000. Second, I had to install the Windows 2000 driver for my PCI-MIO-16XE-10 board, and this driver is not compatable with LabVIEW 4.0.1. Third, that there is something else that I need to copy over from the old computer. Once again, thank you to anyone that can help me out.

Raven3182 wrote:
> Hi,
>
> I'm rather new to this, so I appreiciate any help that you can give
> me. Our lab has an old computer running Windows 95 and LabVIEW v.
> 4.0.1. I would like to take one of the progams on this computer and
> run it on a newer computer in a different lab. This newer computer is
> running Windows 2000. I installed LabVIEW 4.0.1 on the Win2000
> machine, and then copied the needed file onto this machine. However,
> when I try to run the program, I get the following error messages:
>
> Error 7 occurred at Open File+.vi: Open File
> Possible reasons:
> LabVIEW: File not found.
> OR
> NI-488: Non-existant Board.
>
> after that error I get this one:
>
> Error - 10401 occured at AO Group Config.
> Possible reasons:
> NI-DAQ:LV The
specified device is not a National Instruments
> product, or the driver does not support the device (e.g., the driver
> was released before the device was supported).
>
> Now, there are a couple reasons that I can think of that would cause
> these problems. First, LabVIEW 4.0.1 is not compatable with Windows
> 2000. Second, I had to install the Windows 2000 driver for my
> PCI-MIO-16XE-10 board, and this driver is not compatable with LabVIEW
> 4.0.1. Third, that there is something else that I need to copy over
> from the old computer. Once again, thank you to anyone that can help
> me out.
You pretty much summed it up. NI-DAQ which is compatible with LabVIEW
4.0 won't support Windows 2000 almost certainly. And NI-DAQ supporting
Windows 2000 won't have VI support for LabVIEW 4.0. There was a
significant change in the way LabVIEW interfaced to NI-DAQ between
NI-DAQ 5.x and 6.x which happens to be around LabVIEW 4.x as well. So
you are most probably stuck with either a LabVIEW
upgrade or downgrading
to a Windows 9x computer.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

I'm having an intermittent problem with my midi controllers triggering Mainstage 3. I'm using a PreSonus Firebox audio interface. It's been working fine for months, but now when I first turn on the computer in the morning , I'm not able to trigger Ma

I’m having an intermittent problem with my midi controllers triggering Mainstage 3.
I’m using a PreSonus Firebox audio interface.
It’s been working fine for months, but now when I first turn on the computer in the morning , I’m not able to trigger MainStage from the keyboard. I tried different midi controllers, different keyboards, different midi cords, and check midi preferences. The audio interface is working fine and is recogonized, but the midi doesn’twork. I re-started the computer several times and then finally it miraculously starts working again.
I’ve been having to this every day now. Any help or ideas is very much appreciated.

I Had the same problem with a FireStudio. Try unplugging the FireWire plug and the power plug. Wait for a few seconds, then plug both back in. The light on my FireStudio was flashing blue/red which means "not connecting." I did what I just described, and everything works again. Hope it works for you.

Problems with Labview and Windows XP with error -2147217865

Hello. Im a new beginner in Labview and am having a problem with a error message
I dont understand. Im running Labview on a pc-logger with windows XP.
The program is written by a guy on my university, and logs voltage from
a solar cell panel. He doesnt have the time to check in to it, so Im supposed to
find out what's wrong.
The error message is as follows :
Error -2147217865 occured at Cmd Execute.vi->DB Tools Insert
Data.vi->Solcelle.vi
Possible reasons :
Exception occured in Microsoft OLE DB Provider for ODBC Drivers,
[MySQL][ODBC 3.51 Driver][mysqld-3.23.38-log]Can't open file :
'solcelledata.MYD'. (errno: 145). in Rec Create - Command.vi-
>Cmd Execute.vi->DB Tools Insert Data.vi->Solcelle.vi
I really hope someone can tell me what's wrong and specifically what to do
with it, or possibly guide me to someone who could suggest a solution to this
problem.
Reguards
chrisdee

Hi Chrisdee,
(.. not to discount what TimoS has suggested, however...)
Embedded in the error information you provided:
... Can't open file : 'solcelledata.MYD'.
Sounds like the program needs this file? Has the program been moved to a new location?
just a wild guess!
Cheers
Message Edited by Dynamik on 10-06-2005 04:53 AM
When they give imbeciles handicap-parking, I won't have so far to walk!

Problem with two of my business rule triggers

Good morning every one,
I have a small problem with two of my business rule triggers.
I have these tables:
pms_activity
csh_cash
csh_integrate_leh
csh_integrate_led
and my process goes like this:
upon approval of a row in my pms_activity table I have a trigger that insert a row in my csh_cash - and in the csh_cash table I have a trigger that will insert in the csh_ingerate_leh and csh_integrate_led.
my problem is pms_activity does generate a row in csh_cash but the trigger in the cash does not fire to generate a row in the csh_integrate_leh and led tables.
I have generated in the following order after I created my business rule:
I have generated the table from the designer (server module tab)
I have generated the CAPI from the head start utility
I have generated the API from the designer
I have generated the CAPI from the designer
I have run the recompil.sql
I have checked that my business rule trigger is enabled and should run on insert and no where restriction
=== this is my business rule logic ======
l_rule_ok boolean := true;
begin
trace('br_csh001_cev (f)');
csh_gl_pkg.csh_gen_integ_jvs(p_id
,p_ref_num
,p_own_id
,p_trt_id
,p_value_date
,p_description
,p_amount
,p_cur_id
,p_gla_dr
,p_gla_cr
,p_gla_pl
,p_gla_rev
,p_gla_eqt);
return l_rule_ok;
exception
when others
then
qms$errors.unhandled_exception(PACKAGE_NAME||'.br_csh001_cev (f)');
end br_csh001_cev;
==== end =======================
Any help will be appreciated as I have struggled with this for two days.
Thanks

hmmm...
Try resetting it again and restoring with the same backup file...
Does the phone work properly once you've reset it before you try restoring? A lot of people here have experienced problems restoring from backups... could be worth forgetting about it and starting from scratch.
You could try contacting your nearest Nokia Service Centre (www.nokia.com/repair) and see if they can do anything - it may need the firmware reinstalling or upgrading... possibly... give them a call though and see.
Nokia History: 3110, 5110, 7110, 7110, 3510i, 6210, 6310i, 5210, 6100, 6610, 7250, 7250i, 6650, 6230, 6230i, 6260, N70, N70, 5300, N95, N95, E71, E72
Android History: HTC Desire, SE Xperia Arc, HTC Sensation, Sensation XE, One X+, Google Nexus 5

Problem with window repaint and scrollbars in edit mode (LabVIEW 8.0.1)

I am running LabVIEW 8.0.1 in Windows XP SP3. For my main VI, I ran into a strange problem about 5 months ago. The front panel window - in both edit mode and run mode - stopped repainting itself on the right side which is most visible when you scroll up and down, but also visible with overlapping windows. Coincident with the repaint problem, both scrollbars look disabled with greyed-out arrows and no boxes in the bars that you can click and drag to scroll the window. The scrollbars still partially work if you hover the mouse over them and roll the mouse wheel but clicking and dragging doesn't work.
The front panel has lots of controls and indicators including tab-control containers and is larger in the horizontal and vertical directions so both scrollbars should be active. But I deleted all elements on the front panel and everything in the block diagram and the problem persists. So the problem is not directly related to some control/indicator display.
I saved the simple VI with this problem (using a wide text line and a tall rounded box to test), then created a new VI and copied the two elements to the new VI. This new VI does not have the repaint and scrollbar problem. The two VIs differ slightly in memory usage and in revision number (the bad one is revision 1785 and the good one is revision 3), but otherwise the two VIs are identical. I attached both VIs to this posting. When you first open the bad VI, you'll see the disabled scrollbars whereas the good VI has active scrollbars. To replicate the repaint problem, scroll the window up and down with your mouse wheel. If it's fine when you first open the VI, click on another window, then click back on the VI window and try the mouse wheel again. This clicking-away-and-back always causes the repaint problem for me. I tried the VIs on two different computers both running Windows XP SP3 and LabVIEW 8.0.1 with identical results.
Here's what I discovered from troubleshooting with the simple VIs:
* scrollbars always disabled
* repaint problem in main window for window widths larger then 680 pixels
* repaint problem in main window menu toolbar for widths larger than 646 pixels
* entire window becomes disabled for window widths larger than 1348 pixels
* can repaint window by minimizing and restoring, but only repaints that one time
* scrollbar boxes sometimes flicker into view but then disappear
* scroll left and right by hovering mouse over horizontal scrollbar and using mouse wheel
I found something similar on this forum (thread: Problem with front panel refresh) - it might be related to the CAR about the panel being offset internally. I don't have access to LabVIEW 8.5 or later and don't plan to upgrade - I haven't tried the trial version as that user did. I could try to copy and paste my entire block diagram to a new VI but the VI is so large I'm afraid something would break, plus I don't want this to happen again in a few months. The problem seemed to occur after a certain number of saves (or revision number). I save backup copies often and when the problem first happened, I was able to go back to a previous version, make the missing changes and save it with no problems, but this only delayed the problem and it came up later. So maybe it's the revision number. It didn't seem related to a particular addition or modification in the front panel or diagram.
The image attached shows the repaint and scrollbar problems in the bad VI.
This brings up a question I have - if this problem is a bug and was fixed in 8.5 and later, is there a way to apply bug fixes to earlier versions? Or do I have to pay for an upgrade to fix such bugs?
Solved!
Go to Solution.
Attachments:
RepaintTest_Bad.gif ‏27 KB
Test Repaint - From Bad VI, scrollbar and repaint problems.vi ‏7 KB
Test Repaint - From Blank VI, no problems.vi ‏5 KB

Seems something got corrupted with this VI. Copy things over to a fresh VI and things should be OK.
See also this recent report of a similar issue.
LabVIEW Champion . Do more with less code and in less time .

Triggering problems with picoscope 3205 (LabView)

Similar Messages

Maybe you are looking for