Polling in CVI

I am trying to understand how to poll in LabWindows? My application does not require user interface, it will be separate application. If the application had user interface I was creating a new thread and use timer control. Timer control callback would then call the funciton that needs to be polled after specified time.
Are there any samples or suggestion to poll when the application has no user interface?
CLD,CTD

Hi,
You can still have threads even if you don't have a user interface.
There is no restriction about that.
In your thread, you can create a timed loop using functions like SyncWait.
See its help before using it.
Second, you can also create a UIR panel and put a timer control on it.
At runtime, load the panel but dont display it.
Your time should still run.
Third, you can use asyncronous timer. Its an instrument installed by default.
Search for the file "asynctmr.fp" in your CVI folder and add it to your project.
Read the related help documentation.
It is a much reliable timer than UI timer control.
Hope this helps,
S. Eren BALCI
www.aselsan.com.tr

Similar Messages

Lc8901a(Gpib) and 3512(ADC) fast polling repost. Labwindows CVI(on a win98 machine)

Okies I made a this lowlevel try to get a controlled
poll. I only pull 2 bytes but still its slow(around
60 polls per second). I also made some attempts with the IVI driver, which isn't workin that good either.
mabe i'm doing things in the wrong order, any poiters would be welcome.
---------8<------------- code
#include
#include
* This program initalizes and accesses the buffer data in the ADC 3512 by *
* CAMAC access. *
*Switch settings are equal to 4.1.2.2 in ADC manual with internal switch * *
* set for internal buffer mode. Rear jumper set LAM active with * *
* 2 bytes in buffer. *
#include
#include
#include
char GetSerialPollResponse(int);
int initalizeboard(void);
int initalizedevice(void);
void SetupADC(int);
short GetSRQ(int);
static int MyDev;
static int Myboard;
unsigned int MyRead[1] = {0};
unsigned int MyRetn[1] = {0};
int main()
int r, c,k=0,g,h;
short srqq;
unsigned int a;
double volts;
Myboard = initalizeboard();
MyDev = initalizedevice();
SetupADC(MyDev);
//srqq gets status of SRQ wait either 1 or 0
srqq = GetSRQ(MyDev);
g=time(0)+5;
//if srqq is not 1 there is no data to be read the program will end
if (srqq == 1)
do{
h=time(0);
if (srqq==1)
//if(1)
//initiates destructive read of 3512 buffer.
ibwrt (MyDev, "\x02\x00\x11", 3);
ibrd (MyDev, MyRead, 2);
k++;
//initializes LAM for 3512
// ibwrt (MyDev, "\x1a", 1);
// ibrd (MyDev, MyRetn, 2);
//gets status of SRQ signifing data is ready to be read.
srqq = GetSRQ(MyDev);
//If srqq is not 1 again the program will end
}while (h }
a = MyRead[0] & 8191;
// a = MyRead[1] & 8191;
printf("%d :: %8.3f\n",k,a*.0009884);
scanf("%d",&r);
return 0;
int initalizeboard()
//Initalizes the gpib board (not 8901a)
Myboard = ibfind ("gpib0");
ibpad (Myboard, 0);
ibrsc (Myboard, 1);
ibsic (Myboard);
ibsre (Myboard, 1);
//disables autoserial polling so the status of SRQ can be utilized.
ibconfig (Myboard, IbcAUTOPOLL, 1);
return Myboard;
int initalizedevice()
MyDev = ibdev (0, 2, NO_SAD, T10s, 1, 0);
//clear CAMAC
ibwrt (MyDev, "\x22", 1);
ibrd (MyDev, MyRetn, 2);
//assert inhibit (no data collection)
ibwrt (MyDev, "\x48", 1);
ibrd (MyDev, MyRetn, 2);
//set up for high speed block read 16bit
ibwrt (MyDev, "\x6A", 1);
ibrd (MyDev, MyRetn, 2);
//initalized CAMAC
ibwrt (MyDev, "\x21", 1);
ibrd (MyDev, MyRetn, 2);
return MyDev;
void SetupADC (int MyDev)
//clears LAM and buffer
ibwrt (MyDev, "\x0a\x00\x11", 3);
ibrd (MyDev, MyRetn, 2);
//enables LAM
ibwrt (MyDev, "\x1a\x00\x11", 3);
ibrd (MyDev, MyRetn, 2);
//writes control register settings (current 2120h)(least signif 1st)
ibwrt (MyDev, "\x10\x00\x11\x20\x21", 5);
ibrd (MyDev, MyRetn, 2);
short GetSRQ (int MyDev)
short e, f;
char d = 0;
//enables SRQ on occurance of LAM
ibwrt (MyDev, "\x41", 1);
//waits for SRQ (data is available)
WaitSRQ (0, &e);
//runs serial poll
//ibrsp (MyDev, &d);
//disables SRQ and clears Inhibit
ibwrt (MyDev, "\x40", 1);
//sends interface clear
ibsic (Myboard);
return e;
okies this polls, and works with SRQ/LAM but slow, very slow.
Ibspy log.
---------------------8<-------------
1. ibfind(gpib0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:15.810 Call Duration: 00:00:00.170
ibsta: 0x100 iberr: 0 ibcntl: 0(0x0)
2. ibpad(GPIB0, 0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:15.980 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 0(0x0)
3. ibrsc(GPIB0, 1)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:15.980 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 1 ibcntl: 0(0x0)
4. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:15.980 Call Duration: 00:00:00.050
ibsta: 0x130 iberr: 0 ibcntl: 0(0x0)
5. ibsre(GPIB0, 1)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.030 Call Duration: 00:00:00.000
ibsta: 0x130 iberr: 0 ibcntl: 0(0x0)
6. ibconfig(GPIB0, IbcAUTOPOLL (0x0007), 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.030 Call Duration: 00:00:00.000
ibsta: 0x130 iberr: 1 ibcntl: 0(0x0)
7. ibdev(0, 2, 0 (0x0), T10s (13), 1, 0x0000)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.030 Call Duration: 00:00:00.060
ibsta: 0x100 iberr: 0 ibcntl: 0(0x0)
8. ibwrt(UD0, """, 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.090 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 1(0x1)
9. ibrd(UD0, "#%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.090 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 2(0x2)
10. ibwrt(UD0, "H", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.090 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 1(0x1)
11. ibrd(UD0, "'%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.090 Call Duration: 00:00:00.050
ibsta: 0x100 iberr: 0 ibcntl: 2(0x2)
12. ibwrt(UD0, "j", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.140 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 1(0x1)
13. ibrd(UD0, "'%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.140 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 2(0x2)
14. ibwrt(UD0, "!", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.140 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 1(0x1)
15. ibrd(UD0, "#%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.140 Call Duration: 00:00:00.060
ibsta: 0x100 iberr: 0 ibcntl: 2(0x2)
16. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.200 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 3(0x3)
17. ibrd(UD0, "..", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.200 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 2(0x2)
18. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.250 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 3(0x3)
19. ibrd(UD0, "..", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.250 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 2(0x2)
20. ibwrt(UD0, "... !", 5 (0x5))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.250 Call Duration: 00:00:00.060
ibsta: 0x100 iberr: 0 ibcntl: 5(0x5)
21. ibrd(UD0, "..", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.310 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 2(0x2)
22. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.310 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 1(0x1)
23. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.360 Call Duration: 00:00:00.060
ibsta: 0x1168 iberr: 0 ibcntl: 1(0x1)
24. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.470 Call Duration: 00:00:00.000
ibsta: 0x100 iberr: 0 ibcntl: 1(0x1)
25. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.470 Call Duration: 00:00:00.060
ibsta: 0x170 iberr: 0 ibcntl: 5(0x5)
26. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.530 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
27. ibrd(UD0, "#%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.530 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
28. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.580 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
29. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.580 Call Duration: 00:00:00.060
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
30. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.640 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
31. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.640 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
32. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.690 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
33. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.750 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
34. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.750 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
35. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.800 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
36. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.800 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
37. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.860 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
38. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.860 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
39. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.910 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
40. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.910 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
41. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:16.970 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
42. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.020 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
43. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.020 Call Duration: 00:00:00.060
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
44. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.080 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
45. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.080 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
46. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.130 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
47. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.190 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
48. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.190 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
49. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.190 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
50. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.240 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
51. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.300 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
52. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.300 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
53. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.350 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
54. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.350 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
55. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.400 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
56. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.460 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
57. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.460 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
58. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.510 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
59. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.570 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
60. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.570 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
61. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.620 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
62. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.620 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
63. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.680 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
64. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.680 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
65. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.730 Call Duration: 00:00:00.060
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
66. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.790 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
67. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.840 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
68. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.840 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
69. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.900 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
70. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.900 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
71. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.950 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
72. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:17.950 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
73. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.010 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
74. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.060 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
75. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.120 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
76. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.120 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
77. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.170 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
78. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.170 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
79. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.230 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
80. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.280 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
81. ibrd(UD0, "%%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.340 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
82. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.340 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
83. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.390 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
84. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.390 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
85. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.450 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
86. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.500 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
87. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.560 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
88. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.560 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
89. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.610 Call Duration: 00:00:00.060
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
90. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.670 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
91. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.670 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
92. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.720 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
93. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.780 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
94. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.830 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
95. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.890 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
96. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.890 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
97. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:18.940 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
98. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.000 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
99. ibrd(UD0, "%%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.000 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
100. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.050 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
101. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.110 Call Duration: 00:00:00.050
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
102. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.160 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
103. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.220 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
104. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.270 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
105. ibrd(UD0, "%%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.270 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
106. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.330 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
107. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.380 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
108. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.440 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
109. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.440 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
110. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.490 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
111. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.550 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
112. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.600 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
113. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.600 Call Duration: 00:00:00.060
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
114. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.660 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
115. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.710 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
116. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.770 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
117. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.770 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
118. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.820 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
119. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.880 Call Duration: 00:00:00.050
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
120. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.930 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
121. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:19.990 Call Duration: 00:00:00.000
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
122. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.040 Call Duration: 00:00:00.000
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
123. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.040 Call Duration: 00:00:00.170
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
124. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.210 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
125. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.260 Call Duration: 00:00:00.110
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
126. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.370 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
127. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.430 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
128. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.540 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
129. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.590 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
130. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.700 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
131. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.810 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
132. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.870 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
133. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.920 Call Duration: 00:00:00.060
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
134. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:20.980 Call Duration: 00:00:00.100
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
135. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.080 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
136. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.190 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
137. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.250 Call Duration: 00:00:00.050
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
138. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.360 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
139. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.410 Call Duration: 00:00:00.060
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
140. ibwrt(UD0, "...", 3 (0x3))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.520 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 3(0x3)
141. ibrd(UD0, "$%", 2 (0x2))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.580 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 2(0x2)
142. ibwrt(UD0, "A", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.690 Call Duration: 00:00:00.050
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
143. WaitSRQ(0, TRUE (1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.800 Call Duration: 00:00:00.000
ibsta: 0x1168 iberr: 0 ibcntl: 0(0x0)
144. ibwrt(UD0, "@", 1 (0x1))
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.850 Call Duration: 00:00:00.060
ibsta: 0x900 iberr: 0 ibcntl: 1(0x1)
145. ibsic(GPIB0)
Process ID: 0xFFFC8A6B Thread ID: 0xFFFC8513
Start Time: 16:48:21.910 Call Duration: 00:00:00.050
ibsta: 0x160 iberr: 0 ibcntl: 1(0x1)
Well thats about it. I'm going nowhere in getting this crate working controlled and fast, so any help woul be
appriciated.
/Anders

It's to slow, I was expecting an output of atleast 20-50kHz, shure this code performance will increase somewhat if i pull the maximum of 1024 words but still the code is too slow. Is there any shortcuts you can make? What I want is to get data as fast as possible.
/Anders

Can anyone explain the odd behaviour of the CVI Operator Interface?

This is probably really related to CVI in general, but I think people should be aware of this behaviour. If tracing is enabled and a program executing, moving the mouse cursor over the Menu bar area of the Operator Interface program increases the execution of the test program dramatically. Anywhere else slows it down! Could this have any effect during critical test runs? Is there a way to force the fast execution. (i.e. to disable whatever message processing is going on when the mouse cursor is over the rest of the window?)

Brian,
You did not mention what is the CVI operator interface that you are using. In the Simple CVI OI, which is located at \Examples\OperatorInterfaces, the behavior you mentioned may occur.
It is mainly because it uses a CVI timer to poll UIMessages, and the Timer Control runs in the same thread as the User Interface (CVI Panels). Because they both run in the same thread, when you move your mouse Windows handles the mouse move and repaint any window if necessary. While doing this, it stops all the other tasks that is running in the same thread, which means, the timer stops to tick and UIMessages are not handled for some time. In addition, the TestStand Engine executes synchronously with UIMessage handling, so if msg
s are not handled the Engine pauses the execution.
Finally, there is an example that ships with CVI under
\Samples\Toolbox\AsyncDem.prj that shows how to use asynchronous timers. In other words, a timer that runs in a different thread different than User Interface. I also modified the Simple CVI OI to use this asynchronous timer, check the attached zip file.
Regards,
Roberto P.
Applications Engineer
National Instruments
www.ni.com/support
Attachments:
Simple_CVIAsync.zip ‏176 KB

Why do I get a return code of 4 from DS_GetDataValue( ) in CVI?

Using polling DSTP string variable to receive data transferred from localhost DSTP server, the server returns error code 4 not 0. Using DS_GetLibraryErrorString( ) to query the server on error number 4, the error message returned is "The operation completed successfully."
Since no error is usually returned as 0, I am a little surprised to see errorcode 4 being used to tell me that no error occurred.

Hi mpencke,
The DSTP uses the HRESULT information to determine its error codes, and you can find all of the documentation on those error codes in cvi\toolslib\datasock\dataskt.h and cvi\sdk\include\winerror.h. An actual Success code appears to be 0, while an error code of 4 appears to be the code for too many files being open. It could be other numbers are coming into place, or maybe a question of timing. Maybe we could take a look at the snippet of code in question and where it is located within your project, and what is going on we could look further into the issue.
Regards,
James W.
Applications Engineer
National Instruments

Solaris8 and 9 (possibly 7) /dev/poll driver bug report.

Hello,
I'd like to report a bug in the solaris 8 and 9 /dev/poll driver (poll(7d)).
As i do not have a support account with sun or anything like that, there
seems to be no other way to do that here (which is of course a very sad
thing).
Bug details:
The /dev/poll device provides an ioctl-request (DP_ISPOLLED) for checking
if a particular filedescriptor is currently in the set of monitored
filedescriptors for that particular /dev/poll fd set (open /dev/poll fd).
A quote from the documentation of the poll(7d) manual page taken from
Solaris9:
"DP_ISPOLLED ioctl allows you to query if a file descriptor is already in
the monitored set represented by fd. The fd field of the pollfd structure
indicates the file descriptor of interest. The DP_ISPOLLED ioctl returns 1
if the file descriptor is in the set. The events field contains the
currently polled events. The revents field contains 0. The ioctl returns 0
if the file descriptor is not in the set. The pollfd structure pointed by
pfd is not modified. The ioctl returns a -1 if the call fails."
It says that when you query for an filedescriptor which is currently being
monitored in the set, that it would return 1, and change the events field of
the pollfd structure to the events it's currently monitoring that fd for.
The revents field would be set to zero.
However the only thing which actually happens here, is that FD_ISPOLLED
returns 1 when the fd is in the set and 0 if not. When the fd is in the
set, when FD_ISPOLLED returns 1, the events field remains unmodified, but
the revents field gets changed.
A small sample code to illustrate:
#include <stdio.h>
#include <unistd.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <sys/devpoll.h>
main() {
struct pollfd a;
int dp_fd = open("/dev/poll", O_WRONLY);
a.fd = 0; /* stdin */
a.events = POLLIN; /* we monitor for readability, POLLIN=1 */
a.revents = 0;
write(dp_fd, &a, sizeof(a));
a.fd = 0;
a.events = 34; /* filled in with bogus number to show malfunctioning */
a.revents = 0;
printf("DP_ISPOLLED returns: %d\n", ioctl(dp_fd, DP_ISPOLLED, &a));
printf("a.fd=%d, a.events=%hd, a.revents=%hd\n", a.fd, a.events,
a.revents);
According to the documentation of /dev/poll and namely DP_ISPOLLED this
program is supposed to print the following:
DP_ISPOLLED returns: 1
a.fd=0, a.events=1, a.revents=0
However it prints the following:
DP_ISPOLLED returns: 1
a.fd=0, a.events=34, a.revents=1
You can take any number instead of '34' and it will simply remain untouched
after the DP_ISPOLLED ioctl-request.
I hope it's clear now that the solaris8 and solaris9 (and probably solaris7
with /dev/poll patch too) DP_ISPOLLED implementation is broken.
This bug is also easily illustrated by looking at the solaris8 kernel sourcecode:
<snippet osnet_volume/usr/src/uts/common/io/devpoll.c:dpioctl()>
case DP_ISPOLLED:
pollfd_t pollfd;
polldat_t *pdp;
if (pollfd.fd < 0) {
mutex_exit(&pcp->pc_lock);
break;
pdp = pcache_lookup_fd(pcp, pollfd.fd);
if ((pdp != NULL) && (pdp->pd_fd == pollfd.fd) &&
(pdp->pd_fp != NULL)) {
pollfd.revents = pdp->pd_events;
if (copyout(&pollfd, (caddr_t)arg,
sizeof(pollfd_t))) {
mutex_exit(&pcp->pc_lock);
DP_REFRELE(dpep);
return (set_errno(EFAULT));
*rvalp = 1;
</snippet>
its' clearly visible that the code writes the current monitored events to
the revents field:
'pollfd.revents = pdp->pd_events;'
and that it doesnt set revents to zero.
It's funny to see that this has been like this since Solaris8 (possibly 7). That means nobody ever used DP_ISPOLLED that way or people were simply to lazy to file a bug report.
Another funny thing related to this. is that Hewlett-Packard did seem to know about this. Since HP-UX11i version 1.6 they also support /dev/poll. From their manual page i ll quote some sentences from their WARNING session:
"The ioctl(DP_ISPOLLED) system call also returns its result in the revents member of the pollfd structure, in order to be compatible with the implementation of the /dev/poll driver by some other vendors."
Hopefully this will get fixed.
I also like to reexpress my very negative feelings towards the fact that you're not able to file bug reports when you do not have a support contract. Ridiculous.
Thanks,
bighawk

Have I mentioned how much i love my playbook now Great job on os 2.0

Restricting polling in sender file adapter

Hi friends,
I have a requirement where I need to poll a file from an FTP server. But, if the file is being edited (some other application is writing to it) I need to avoid picking that file. Plz tell me how i can achieve this...waiting for ur replies.
Regards,
Shilpa

Shilpa,
Check out this sap note :
[https://websmp230.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=821267|https://websmp230.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=821267]
File Locking / Incomplete Processing
Q: I sometimes observe that files are processed only partially, i.e., only a fragment from the file's start is converted into an XI message. Nevertheless, the file is usually archived completely. Does the File Sender Adapter honor if another process has locked a file for exclusive use?
A: Unfortunately, the J2EE 1.3 technology the File Adapter is built upon does not support file locking. This limitation affects the File Adapter's operation. Depending on whether the JRE implementation for the operating system under which the adapter runs uses mandatory file locking or advisory file locking, opening a file that is currently being written to by another process will fail or not.
If opening the file fails, no problem exists and the adapter will try to open the file each poll interval until it succeeds.
However, if opening the file is not prevented by the operating system, the adapter starts to process the file although it is still being modified. Since XI 3.0 SP11 / PI 7.0 there is a parameter named "Msecs to Wait Before Modification Check" in the advanced settings of the File Sender channel configuration to work around this issue. This setting causes the File Adapter to wait a certain time after reading, but before sending a file to the Adapter Engine. If the file has been modified (which is basically determined by comparing the size of the read data with the current file size of the input file) after the configured interval has elapsed, the adapter aborts the processing of the file and tries to process the file again after the retry interval has elapsed.
If this option is not available for the settings you would like to use, the following algorithm (to be implemented in your application) may be used to ensure that the File Adapter only processes completely written files:
Create the file using an extension, which does not get processed by the File Adapter, e.g., ".tmp"
Write the file content
Rename the file to its final name, so the File Adapter will notice its existence and pick it up
Hope this will help.
Thanks,
Nilesh

Poll: Development in ABAP Objects / Webdynpro vs. classical Dynpro

Hey there ABAP developers,
I just want to ask if you can give me one or two minutes of your attention for two poll questions.
At the moment I´m writing my master thesis about the development of a monitoring tool in ABAP. One of my bigger chapters is about the decision, which programming paradigm should be used for new development projects in SAP. And another important one is about WebDynpro vs. classical Dynpros.
Because of the fact, that I can´t create any polls in here, I just started this discussion and hope for many replies .
It would be very nice if some of you could give me an answer to the following questions (only 2 ), so that I can maybe use the result of this poll in my master thesis, if there are enough responses.
1. What percentage of new development projects are you developing in ABAP Objects? (Not to be considered small reports that just runs for only one time)
     A. 0 %
     B. less than 25%
     C. 25% - 49%
     D. 50% - 75%
     E. more than 75%
2. Which GUI technology do you prefer?
     A. Classical Dynpro
     B. WebDynpro
     C. Business Server Pages (BSP)
     D. others (please mention)
I want to thank you in advance for answering the questions,
Best regards,
Christoph

Hi,
Present SAP Implementation projects are very rare, maximum projects are support and up gradations only .
If they want Implement the SAP newly , defiantly they should creating ABAP Objects.
Why Because ABAP Objects are Object Oriented Concepts, so, for future reference and re usability..etc .
Now Come to the First Quetion.
if it is implementation project   ABAP Objects are 25% - 49%.
if it is Support project ABAP Objects are 25%
Now Come to the Second Quetion.
Depend upon Reqmnt, but Most of the Applications are Webdynpro . i.e 70%.
Remaining 30% All ( BSP and GUI ....Etc..)
This is my opinion.
Sambaiah.Paidipelli.

Logical Delete in DB Polling - OSB

Hello All,
I have a question in polling. I have a logical delete column with Read value as 'P and unread value as 'N', Unlike BPEL, OSB's polling, does not make a record to 'P' until the process completes successfully. My DB polling adapter polls the same records while the previous instance is under processing or the previous instance ended in error. Is there a way to logically delete the record immediately once the record is read?
To avoid this scenario, I added an error handler to make the record to 'E' if the instance encountered any error. By the time the error handler kicks in and updates the record, OSB polls the record a few times. I increased my polling frequency from 5 seconds to 30 seconds, but no luck. Any clue how to handle this scenario?
Thanks,
Dwarak

Is there a way to logically delete the record immediately once the record is read?Dont do any logic in db adapter proxy. Instead make the proxy to just write to a jms queue and then have your processing logic in the jms proxy service which reads off the jms queue.

A better way to poll

When my Start button is clicked it changes a member variable from false to true.
Here is a simplified version of my code:
public class gdvdhomevideo
   private boolean blnBegin;
   public static void main(String[] args)
      while(blnBegin == false){}
      //perform operations
   public void actionPerformed(ActionEvent e)
      String command = e.getActionCommand();
      if(command.equals("Start"))
         blnBegin = true;
}So when the user clicks start it exits the while loop and the program starts performing other functions. The problem is that this approach is 100% CPU intensive and I know that there must be a better way?

1) Code executed in the main() is NOT running on the event thread. Don't do any GUI code from the main thread... You know, stuff like showing windows, attaching event listeners etc.. You need to wrap all that stuff in a Runnable and pass that Runnable to SwingUtilities.invokeLater().
2) Assuming the stuff you're doing in the main() is actually thread safe and doesn't touch the GUI, you can simply startup a new Thread and put your code in there. (see below)
3) You class name is named badly. Please check out sun's java coding conventions. It is very nice to have coding conventions. Use them! ;-)
4) if you want to setup your program as a loop rather than simply relying on user actions to fire events, then I'd suggest you use a timer that notifies on the event thread every X where X is a non-zero polling interval. I think there's a class is called SwingTimer that does this sort of thing for you.
What you're attempting to do is non-trivial.. so.. ummm.. have fun..
public class gdvdhomevideo
   private boolean blnBegin;
   public static void main(String[] args) throws Exception
        SwingUtilities.invokeLater( new Runnable() {
              public void run() {
                   //setup stuff in here.
   public void actionPerformed(ActionEvent e)
      String command = e.getActionCommand();
      if(command.equals("Start"))
         new Thread(new Runnable() {
            public void run() {
                 //perform operations but don't touch the GUI.
          }.start();
}

Cannot display square root symbol in cvi

I don't understand why this would be an issue, but if I'm writing in the source window (with the default font of NIEditor), I cannot display a square root symbol "√" - every time I type alt+251, I get "v". Ok, not a huge deal in the source window, but it is a big deal if THAT is what's being stored in a string variable I'm writing out to a file. Additionally, if I use the following to format a string:
"Fmt(setpointUOM, "%s<W%cT/P3", 251);", then setpointUOM = "WüT/P3". If I display this variable in a string control, it displays as "W√T/P3", which is correct, but if I use it in a Text Box or save it to a sql database, it displays "WüT/P3" which is unacceptable.
I've tried changing the fonts but nothing works or I get even stranger results. I've been dealing with/ignoring this since CVI7 and I'm currently at CVI10. Thanks for any help.
Solved!
Go to Solution.

The difference in the display between W√T/P3 and WüT/P3 has to do with the character set that you select for the UI control. From what I can tell, only the OEM code pages map the √ symbol to character 251, so if you want to see √ for that character, you should pick the OEM character set, in that control.
Entering √ with the keyboard in a CVI window seems like a much more problematic task. When you type Alt+251 on a CVI window, the keyboard driver is converting the 251 to 118 (the letter v). I don't know why it does that, but I noticed that the code that it converts 251 to varies, depending on your input language (which you can change in Control Panel>>Region and Language>>Change keyboards or other input methods). When english is selected in the language bar, it converts it to 118. With other languages, it converts it to other codes. I tried entering the unicode value for √ directly, which is Alt+221A (to enter unicode characters using the keypad, you have to follow the steps described here). But it didn't work. It still converted it to 118. I suspect the keyboard driver is doing this because it tries to map 221A to some symbol that is valid in the code page that corresponds to the input language, isn't able to, and picks what it thinks is the closest match.
In lots of other applications (but not all) you can type Alt+251 or Alt+221A and it works just fine. This is because those applications accept unicode characters directly. Unfortunately, CVI isn't one of them. It uses code pages (a.k.a. character sets, or multibyte sequences) instead of unicode, and symbols don't have a universal meaning; they depend on the code page.
Even if all this were not an impediment, you'd still run into the problem that in CVI 2010 you cannot change the font of the CVI source window to use an OEM character set. So, you'd still see it displayed as a v or a ü. In CVI 2012 you can change the change it, and so if you were using CVI 2012 you could conceivably use the clipboard to paste the √, but there is a bug in CVI that is preventing OEM characters from being pasted correctly (I realize the description says that it affects tree tooltips, but it's also generally affecting clipboard operations of some less commonly used character sets).
So, to make a long story short, I think you should continue entering the code directly with the Fmt function, at least until this bug is fixed. And make sure that all UI controls that need to display this string are using the OEM character set.
Luis

A Poll for A New BB10 feature(Z10) Come All!

I have noticed in the pass couple weeks that the z10 virtual keyboard is awesome, but needs a 'GREAT' tweak.Do Not get me wrong the keyboard it one of the best, but the send button needs a new home.
The SEND button needs to have two options in text messages; or an option somewhere that someone can change the place of the send button. I have noticed that many other people are feeling my pain. I almost wanted to switch back to my cheap androi** phone. I have sent countless messages that were not finished(quite embarrassing) to people. Some messages contained rather 'awkard'() spelling errors.
More details:
The send button is right under the backspace and very easy to hit. Even if the Next Update!!! to the phone lets the users choose to move the send button into the bar next to the smiles is better or even on the top bar.
Anyways Onto the fact. I want you people to vote! I know for a fact that BB Dev's browse these forums.
I cannot find a Poll making button so I am doing it the old fashioned way!
I believe some people might like this but a majority of us have sent unfinished text messages. So an option to move the send button, or even just simply moving it would be nice.
Poll: Have an option to change the location of the send button in text messages?
Vote -> Yes
Vote -> No
This Poll will be counted every week. Unless a fellow awesome person would know of a Poll button on here?... ANYWAYS VOTE! LET THE DEV'S KNOW.

Not a problem. Download MPEG Streamclip (it's free) and if you don't already have it on your Mac, you will also need the Apple QuickTime MPEG2 Playback Component (which you can download from Apple for $20).
With them you can convert your video to DV or Apple Intermediate Codec for editing with FCE.
Here are some simple instructions for settings to use in MPEG Streamclip.

Create survey/poll with text fields

I want to create a survey in a meeting with text field type answers. How would I do this? I am using the hosted version of Connect and saw some reference to a Presenter add-in for PowerPoint, but don't seem have that. We would like to have fields such as:
Participant information (name, contact information
Suggested future topics
What should I use to do this since the Poll Pod obnly allows for multiple choice or multiple answer options and not key-in fields?
Karl

Adobe Presenter 7 is a product sold separately from Adobe Connect. Adobe Presenter can be purchased from many resellers. It is a plug-in for MS Powerpoint and has the ability to upload many times of quizzes and polls in lots of types of formats. You can download a 30 day trial from here:
http://www.adobe.com/cfusion/tdrc/index.cfm?product=presenter&loc=en_us
Adobe Presenter is only available for the Windows platform. MS Powerpoint for Mac does not allow third-party plug-ins like Presenter.

Using Excel with Visual C++ 6.0 (need a graph control that behaves as much like the one in CVI as possible)

I hate to beat this to death but I was unable to find a
clear answer to this question. Does NI provide Excel control from within
Visual C++ 6.0?
I read that NI supports the ANSI-C library only for Visual C++ 6.0 users:
Thread : "Re: Benifits of using measurment
studio for VC++ 6.0?"
NI REP : drohacek
Quote : "we made the decision to support Visual
C++ 6.0 users only through the ANSI-C interface and not through the Measurement
Studio MFC-based class libraries."
If there is a suggested way of controlling Excel from within Measurement Studio
for Visual C++ 6.0 then I’d love to know it.
If not, can a plain statement be made basically stating that if you want
to control Excel you can’t use a Visual C++ 6.0 environment even with Measurement
Studio support?
With .NET of course you can just decide to have Excel support added during
project creation. CVI can act as an ActiveX server and easily control
Excel just by building off the examples shipped with CVI. I see that
there is support, using the Measurement Studio for Visual C++ 6.0 Project Wizard,
for taking existing CVI projects and converting them to Visual C++ 6.0 projects
or for calling CVI libraries from a .dll from within Visual C++ 6.0. I suppose I could do the work
in CVI and then convert the project but I'm so deeply tied into all my MFC calls that I don't see
how I can cleanly include the CVI libraries into my existing VC++ 6.0 projects.
What I'm really after here is a visual graph control like the one in CVI that I
can use from Visual C++ 6.0. I purchased a 3rd party graph control for use
in VC++ 6.0 that works well but isn't really visual. I mean you can't
enter any values in it until you run the program and fill it out programmatically.
Then you can see which columns are two narrow, quit the program, adjust the
column width of your now empty control, and repeat, until you get the thing
looking the way you want. If I could call into Excel from within Visual
C++ 6.0 the way I do from within .NET
then I could use Excel to hold the table and just read in the values into my table
control at run time. Basically I'd use Excel as a visual development tool
for all my tables.
I do all my coding from within CVI and Measurement Studio for Visual C++
6.0. I'd use CVI for everything if I didn't depend so heavily on certain
outside controlled C++ .dll's. Could you please suggest then what I can
do to get Excel support for Visual C++ 6.0?
Last question :
Is there any plan to ever have a NI table control like the CVI table control for
use in Visual Studio? One that you can
completely set up before you do any compiling?
I imagine that the way Microsoft sets up their environment makes this idea impossible. Otherwise someone would
have come up with a truly “visual” table control before now.
Thanks,
Grant
Grant M. Johnson
Project Engineer
LECO Corporation

Hello Grant
You can most certainly use Excel with VC++ 6.0. Measurement Studio won't provided you with any classes to talk to Excel in VC++ 6.0. This is because Excel allows control via Automation and you can use its automation API to do anything you need with Excel. This is what CVI uses as well.
You can see this MSDN article on how to set this up. This mentions VC.NET, but it should work the same way.
Here is one that talks about VC 6.0 and Excel.
Here is a code project article about this.
Even with .NET, you have to do thru the Excel Automation support. Excel started shipping with Primary Interop Assemblies (PIA) which are .NET wrappers about the Excel Automation object model. C++ Automation is definetely not as nice as .NET, BTW
See this document for more information about the Excel object model.
I would not recommend using the CVI Excel libraries if all you want to use them for is Excel automation. You will end up creating un-necessary dependencies and go through extra layers that way. You can make calls straight to Excel from VC++ without requiring CVI.
One quick observation about your excel approach. If you decide to use Excel as your table, you might be requiring everyone who uses your application to have Excel installed on their machines. Just wanted to make sure this was acceptable to you.
Have you looked at the Datagrid Activex control, which is one of the common controls that ships with Visual Studio? You can add it to Visual Studio by right-clicking and picking it from the list of installed activex control. If you have not already, you should check it out.
Microsoft has made significant improvements in the number of controls they provide with .NET. They have a Datagrid control that seems to be what you need.
Measurement Studio did add some high level classes for Excel and Word Automation that simplify some common tasks, but these exists for VS 2003 C++ and VS 2005 C++, not for VC 6.0. Underneath, we end up using the same Excel automation classes, so you can easily setup something similar for VC 6.0. Plus you can find alot of references online on how to use the Excel Automation object model with C++.
We currently have no plans in Measurement Studio to create a table control unfortunately. I am assuming when you said graph, you actually meant table, since Measurement Studio already provides a ActiveX graph controls for VC++ 6.0 that is very similar to the CVI graph.
On a side note, VC++ 6.0 is really really old. Have you considered upgrading?
To summarize
- Yes, you can use Excel with Vc++ 6.0 without mstudio.
- Try using the Datagrid Activex control if you just need a table.
- Measurement Studio provides high-level excel and word classes for VC++ 6.0
- Measurement Studio provides a graph control for VC++ 6.0 which is very similar to the CVI graph.
- Measuremnt Studio does not have a table control.
- VC++ 6.0 is really really old. Have you considered upgrading?
Bilal Durrani
NI

Visual Studio or LabWindows/CVI?

I have a bit of a dilemma.
I currently own Visual Studio 2010, IMAQ Vision Development Module 2013, and Measurement Studio (not sure of version). I currently do all of my programming in VB.net. Because IMAQ VDM is stuck in .Net framework 3.5 and there will be no further .net development by NI, I need to plan for the future. My applications need run on Win 8, 9, 43, or whatever my company decides to migrate to from Win 7.
My understanding is that the NI modules I currently own will work with LabWindows/CVI. Correct? I also believe I can use them with C++ using the VS IDE. Is this also correct?
Within my applications I do a lot of interfacing with Excel, writing text files, and interfacing to non-NI devices (cameras, DAQs, scanners, etc). I am able to do these things pretty easily using VB.net using vendor-provided SDK's.
Therefore, my question is this...given the investment I have in software already, do I gain anything by migrating to LabWindows/CVI? What do I lose?
I should point out that regardless of the path I choose I will need to bone up on my programming skills in the corresponding language.
Thanks for all your help!

Hello Steverino!
Here are some advantages when using LabWindows/CVI over Visual Studio, which make the product more suitable for various industry-related applications:
You are correct, LabWindows/CVI integrates with the NI platform: NI hardware and software, like TestStand or LabVIEW (e.g. debugging source code from one software to another, seamlessly).
NI hardware and third-party hardware connectivity.
OpenMP support.
CVI integrates with intrument control.
CVI Run-Time benefits from User Protection.
Run-Time checking (e.g. for uninitialized variables).
Scientific User Interface Controls and GUI Editor.
Advanced debugging capabilities:
Remote debugging support from ADE.
Real-Time debugging support from ADE.
Memory leak detection using the LabWindows/CVI Resource Tracking Window.
Just-In-Time debugging.
Deployment: build custom installers and patches that you can ship as stand-alone easy-to-use installers.
LabWindows/CVI libraries: Advanced Analysis, Toolbox, Connectivity (Network Variables, Network Streams, DataSocket), etc.
Support for LabWindows/CVI Toolkits: SQL Toolkit, Vision, PID, RT.
Regards,
- Johannes.

XI file adapter polling faster than poll interval

Hi,
We are facing a issue with the file adapter/authorization of the FTPUSER.
We FTP a server and pick up a file from a particular folder.
My polling interval is 2 minutes
My retry interval is space.
Processing mode : ARCHIVE
We are archiving it on a Network attached server(NAS) mounted on our XI server.
When XI polls for the first time it picks up the file but the sender file adapter shows following error in RWB.
<b>2006-01-20 11:31:08 GMT: Error: Deleting of file 'ARUCSjnewb80.txt' failed - cannot proceed: FTPEx: ARUCSjnewb80.txt: Access is denied.</b>
The picked up file gets processed but at the same time just within 12-13 seconds of the first poll XI picks up the file second time and then in another 3 seconds for the third time.
After this the file gets archived thrice in the archive directory and then gets deleted from the source directory.
We are unable to understand why XI is polling again after few seconds of the first poll.(As per my understanding it should have polled after 2 minutes).
I am able to delete the file manually from the Ftp server.
Could anyone give a pointer towards what we are missing or what probable reasons could be?
authorization issue?( XIADM /ftpuser have full authorization)
Some adapter setting?
Regards,
Sulakshana

Hi,
Could you let me know how frequent the file gets loaded to the FTP server.
Is your file size too large to get loaded.. If so try to increase the polling interval. Also make sure that you have provided the polling time in sec and not in minutes...i.e for 2 minutes it should have been specified as 120 sec as polling interval
Regards,
Nithiyanandam

Polling in CVI

Similar Messages

Maybe you are looking for