15" ADC to Performa?

I assume there is no way to use a 15" Apple Display with ADC cable with a Performa 630CD or a Mac IIvx, correct? There is likely no adapter and/or the video cards don't support?
Thanks for any input.....

LBJ1251 wrote:
I assume there is no way to use a 15" Apple Display with ADC cable with a Performa 630CD or a Mac IIvx, correct? There is likely no adapter and/or the video cards don't support?
Thanks for any input.....
Unless you can change the cable to a DB 15, no sorry you are out of luck. I don't recall ever seeing any adaptors for such a gender change.
For the cost of an adaptor it's probably better to just find a 14" monitor there were many types but the first version was the best as it had a Sony tube later Apple monitors were made with cheaper parts. I think the one's you should avoid are the Performa and Performa Plus.
Kevin

Similar Messages

Automotive diagnostic command set and periodic messages on same can port - CVI

Hello everybody,
Is it possible, using Labwindows / CVI, to use NI AutomotiveDiagnostic Command Set to communicate with a MCU with KWP2000 protocol and simultaneously send periodic CAN messages on the SAME CAN interface (CAN0 or else ) and also using this port port to do some CCP communication ?
Thank for your support.

Hi,
I find myself also in this position. My current project only has LabVIEW 2009 and the ADCS from a few years back available to use.
We want to be able to:
- read in a CANDB file (.dbc) into the Channel API, to send general CAN messages (note you cannot use the Frame API to read in the dbc files unfortunately)
- using the same CAN interface, use the ADCS to perform diagnostics activities
Can you please elaborate on some of the hoops, and how long it might take? If its too much of a hack, a third CAN port might be the easier option.
Any light shed would be appreciated.
Christopher Farmer
Certified LabVIEW Architect
Certified TestStand Developer
http://wiredinsoftware.com.au

In terms of performance. Which adapter works better ? ADC-VGA or DVI -VGA

Or are parameters different ? Presently my CRT 20" Sony requires an adapter
for my G4. My graphics card suggest that I can add another monitor. It will be a LCD with DVI output. Is the performance better from the ADC-VGA option for the CRT ?
Thanks

ADC is a digital output so you will get the best performance from a digital panel LCD. An adapter will always costs a little on performance, but if you go VGA you lose quality by default in some area.

Mini with 22" ADC Cinema Display w/ADC-DVI

Greetings...
I've been playing with my new 1.4Ghz mini and the display I happen to have free right now is an original 22" Cinema Display. I have the ADC to DVI adapter for this display and it's rock solid on my old G4 Sawtooth. Anyway on the mini it works very nicely exept for one problem. I get a flicker that seems to tie to system activity. May be voltage variations effecting the internal video DVI drivers. OK my question it. 1) Has anyone else out there tried this combination? (Apple's monitor compatibility chart says it's supported so I know somone at Apple tried it). 2) Do you have any image stability issues like flickering. I'm asking this because I'm now wondering if maybe my little guy is a bit faulty in the video department. I'll try my new 20" display tomorrow to see if it has the same problem.
Anyway this is an amazing little box. BTW mine currently has the minimum RAM but that will change as soon as I put this video issue to bed. Hope to use it in my studio because it's so quiet... Very nice in the sound department.
Enjoy,
--Bryan

Good news...
Well I managed to locate a rev B version of the DVI-ADC adapter. First good news is the price is now down to $99 from the original $150. Second good news is that the /B version seems to work. No more flicker!!
Hey Michael L... Thanks for the suggestion it worked!!
So while this isn't the cheapest solution, it does seem to work so far and considering the cost of a new 22 or 23" monitor vs. using my excellent 22" ADC Cinema Display I'm feeling OK about it.
So John you might want to give a rev. /B version of the adapter a try. BTW the actual adapter is absolutely identical to the REV /A version on the outside the only difference it the serial number is in a different range. If you buy an open box make sure the serial number matches on the box that shows the /B revision matches the actual unit.
Happy Hunting... They are not easy to find. Yeah I know this $600 Mac is starting to rack up the bucks but hey considering it has better performance than my original G4 Sawtooth that I paid like 5X as much for I can't complain too loud...
This will hold until Apple can produce a new truly drool worthy high end machine. The bar just went up with the introduction of the mini. The new once has got to be small, it's got to be silent and it goes with out saying it's got to be so fast it will make you cry. Until then I'll use what I have right now...
Next I need to track down a good 1GB stick of ram for the Mini...
Enjoy,
--Bryan

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

ADC for Domestic Purchase not flowing in MIRO for particular MIGO Document

Hello Experts,
    We've a scenario in which we pay ADC to domestic vendor. The procedure we follow is as below:
          1. Condition record for JAOP with 0% rate maintained in FV12.
          2. PO created with JMOP 10%, 2% ECS, 1% SECS & 4% VAT.
          3. During MIGO (also excise invoice capture), AED value is maintained
          4. After J1IEX, at the time of MIRO this ADC along with other duties flows in simulation
    Now in my case, there are number of GR documents for which MIRO is performed, but for particular GR, ADC is not flowing in MIRO and also excise duty is incorrect, it's not flowing from GR.
   So what is the probable solution for this, I've already checked MIGO & excise invoice documents & found to be ok.
Thanks in advance
        Amit

Hi,
Have you maintained material price including AED price??
If yes then check whether you have maintained JAX1-100% or not?
I think this should be treated as a dealer purchase as you are maintaining 0% amount for JAOP.
Regards,
Piyush

Quicksilver 2002, best AGP card that I can use ADC port?

I currently have a 2002 QS 933mhz, and would like to add Core Image support. However, I am kind of on a budget, and need to still be able to use my 17'' ADC studio display. I'm okay with having to tape pins 3 and 11 if necessary, but I need the card to be able to power my display. Any suggestions?

For budget performance increases, and for overall system performance enhancement, with minimal effect from Leopard, I would stick with the Radeon 9800.
For more serious gaming, skip the Radeon, and get the Geforce 6800 GT.
Processors have a lot to do with video playback.
A "budget" upgrade, would be the OWC 7455 based 1.467 GHz processor (1.5 GHz in a 100 MHz system).
That processor has a 2MB L3 cache, and would help a lot with video applications and total system performance.
A 7447 processor upgrade doesn't have a L3 cache, but a larger L2 cache, and higher clock speeds make for a good upgrade. A 1.7 GHz processor will provide video performance equal to/ or better the 1.467GHz, and perform better on other apps because of the increased clock speed. 7447 processors are also cooler running, and have lower power requirements, as compared to 7455 processors.
The top processor family, and upgrade, a 7448 2.0 GHz processor, is really a performance buy. A 1MB L2 cache is faster than any L3 cache, and the architecture of the 7448 processor provides great increases in processor performance as compared to either the 7447 or 7455 processors.
The 7448 is also the coolest running, and has further reductions in power requirements as compared to the 7447 processor.
For all processor upgrades, check OWC.

Differentiate between DC and ADC

Hi,
How can I differentiate that which machine in my domain is DC and which one is ADC?
Best Regards, Parveen Chauhan [email protected] Mobile: +91-9811629793

In Active Directory, all DC can perform read and write operations – except RODCs in Windows 2008. In general, all DCs are same.
Some DCs will hold FMSO roles.
FSMO Role:
http://support.microsoft.com/kb/197132/en-us
RODC:
http://technet.microsoft.com/en-us/library/cc732801(WS.10).aspx
Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.

ADCS Remove child table is not working

Hi
The AD out-of-box adapter ADCS Remove from child table is not working correctly.
when i remove data from child table the task status shows completed, but the description inside the task shows that the GROUP HAS BEEN REMOVED ALREADY FROM TARGET.
But on checking the AD I found the groups were not removed actually.
In the log i found this error
Running Remove User From Group
DEBUG,03 Nov 2009 10:21:06,099,[OIMCP.ADCS],tcUtilADTasks::removeUserFromGroup() Enter
DEBUG,03 Nov 2009 10:21:06,099,[OIMCP.ADCS],tcUtilADTasks::getLookupCodeValue() Enter
DEBUG,03 Nov 2009 10:21:06,115,[OIMCP.ADCS],tcUtilADTasks::getLookupCodeValue() Exit
DEBUG,03 Nov 2009 10:21:06,115,[OIMCP.ADCS],tcUtilADTasks::getObjectByObjectGUID() Enter
DEBUG,03 Nov 2009 10:21:06,115,[OIMCP.ADCS],tcADUtilLDAPController::search() Enter
DEBUG,03 Nov 2009 10:21:06,115,[OIMCP.ADCS],tcADUtilLDAPController::getPath() Enter
DEBUG,03 Nov 2009 10:21:06,115,[OIMCP.ADCS],tcADUtilLDAPController::getPath() Exit
DEBUG,03 Nov 2009 10:21:06,115,[OIMCP.ADCS],tcADUtilLDAPController::connectToAvailableAD() Enter
DEBUG,03 Nov 2009 10:21:06,115,[OIMCP.ADCS],tcADUtilLDAPController::hashTableEnvForDirContext() Enter
DEBUG,03 Nov 2009 10:21:06,115,[OIMCP.ADCS],tcADUtilLDAPController::hashTableEnvForDirContext() Exit
DEBUG,03 Nov 2009 10:21:06,115,[OIMCP.ADCS],tcADUtilLDAPController::hashTableEnvForLDAPContext() Enter
DEBUG,03 Nov 2009 10:21:06,115,[OIMCP.ADCS],tcADUtilLDAPController::hashTableEnvForLDAPContext() Exit
INFO,03 Nov 2009 10:21:06,115,[OIMCP.ADCS],SSL option is not selected in ITResource
DEBUG,03 Nov 2009 10:21:06,131,[OIMCP.ADCS],tcADUtilLDAPController::connectToAvailableAD() Exit
DEBUG,03 Nov 2009 10:21:06,334,[OIMCP.ADCS],tcADUtilLDAPController::disconnect() Enter
DEBUG,03 Nov 2009 10:21:06,334,[OIMCP.ADCS],tcADUtilLDAPController::disconnect() Exit
DEBUG,03 Nov 2009 10:21:06,334,[OIMCP.ADCS],tcADUtilLDAPController::search() Exit
DEBUG,03 Nov 2009 10:21:06,334,[OIMCP.ADCS],tcUtilADTasks::getObjectByObjectGUID() Exit
DEBUG,03 Nov 2009 10:21:06,334,[OIMCP.ADCS],tcADUtilLDAPController::getPath() Enter
DEBUG,03 Nov 2009 10:21:06,334,[OIMCP.ADCS],tcADUtilLDAPController::getPath() Exit
DEBUG,03 Nov 2009 10:21:06,334,[OIMCP.ADCS],tcADUtilLDAPController::connectToAvailableAD() Enter
DEBUG,03 Nov 2009 10:21:06,334,[OIMCP.ADCS],tcADUtilLDAPController::hashTableEnvForDirContext() Enter
DEBUG,03 Nov 2009 10:21:06,334,[OIMCP.ADCS],tcADUtilLDAPController::hashTableEnvForDirContext() Exit
DEBUG,03 Nov 2009 10:21:06,334,[OIMCP.ADCS],tcADUtilLDAPController::hashTableEnvForLDAPContext() Enter
DEBUG,03 Nov 2009 10:21:06,334,[OIMCP.ADCS],tcADUtilLDAPController::hashTableEnvForLDAPContext() Exit
INFO,03 Nov 2009 10:21:06,334,[OIMCP.ADCS],SSL option is not selected in ITResource
DEBUG,03 Nov 2009 10:21:06,349,[OIMCP.ADCS],tcADUtilLDAPController::connectToAvailableAD() Exit
DEBUG,03 Nov 2009 10:21:06,349,[OIMCP.ADCS],tcADUtilLDAPController::modifyAttributes() Enter
*ERROR,03 Nov 2009 10:21:06,349,[OIMCP.ADCS],The error occured in tcADUtilLDAPController::modifyAttributes():null*
DEBUG,03 Nov 2009 10:21:06,349,[OIMCP.ADCS],tcADUtilLDAPController::disconnect() Enter
DEBUG,03 Nov 2009 10:21:06,349,[OIMCP.ADCS],tcADUtilLDAPController::disconnect() Exit
DEBUG,03 Nov 2009 10:21:06,349,[OIMCP.ADCS],tcUtilADTasks::removeUserFromGroup() Exit
Any thoughts would be grateful
TIA,
Manoj

Hi Manoj,
The error message below is performed when the connector tried to remove the user from a user group removeUserFromGroup() (ADCS Remove User From Group), so the user group will not be removed. To delete a group, you have to run the delete group task of AD Group process.
When the user has already been removed from the group, the connectors shows null to the tcADUtilLDAPController::modifyAttributes():null
Renato.

Hello ~ I bought a G4 Hello ~ I bought a G4 Power Mac & had used it with a standard monitor. Somebody gave me a M8536 23" Cinema Display. I think they should be compatible. My G4 seems to be missing what I think is called an ADC connection.

Should I just buy a video card with an ADC connection?

Hi Mark,
I didn't check your link on your original post. Sorry.
There is one other model that is a 400 MHz model that will accept cards with an ADC connection port.
That's the Gigabit Ethernet model.
You do not have this model Mac.
The table in the link we both have show you what video connections the and locations for those on the back panel.
Clearly, your PowerMac doesn't have an ADC connector for the card that is already installed.
So, you can conclude that you have the AGP sawtooth model that only uses VGA or DVI connection.
You can give me your PowerMac's model number to be sure.
It's located on the back panel somewhere near all of the connections.
That'll clinch, for sure, which model you do have.
You will have to purchase an ADC to DVI adapter when you decide which card to update to per JapanMac's suggestion.
The adapter doesn't affect video performance.
Just allows for a connection change at the computer.
This is about as straightforward as this gets.
The absence of an ADC connection port means you have a Mac with a VGA and/or DVI connection instead.
An adapter will be needed to use the 23 inch monitor you have with the card you have installed now or any future video card upgrade.

ADCS Enable User is not getiing Initiated

Hi All,
ADCS Enable user is not getting initiated, when ever OIm user gets enabled. I am assuming, If we enable OIm user, then Oim will enable all resource accounts of that particular users by default. Am I correct? In that case, OIm is not initiating Enable ADCS user adapter, when I enable oim user
(User is having account on AD). Do I need to perform any thing here to initiate that adapter?
Please suggest
Thanks.

Rajiv,
We have not used any event handlers in our implementation, but some how, getting the following error, when ever, we modify any user.
<Nov 9, 2011 4:44:23 PM EST> <Warning> <oracle.iam.callbacks.common> <IAM-2030146> <[CALLBACKMSG] Are applicable policies present for this async eventhandler ? : false>
How can I find it out this event handler and delete? please suggest.
Thanks.

Best Upgrade to Improve Performance?

I'm looking for the most economical way to boost Aperture's performance. The specs on my equipment are as follows:
Dual 2.0 ghz G5 Tower (first generation)
160 gb internal HD (where my current projects and masters are stored)
320 gb external Lacie HD (for backup, and where I move older master files)
ATI Radeon 9600 Pro 64 mb (stock)
2 gb RAM
OS X 10.4.9, just reformatted and reinstalled over the weekend
20" Apple Cinema Display (ADC)
All photos are from my Nikon D80, which is 10 mp, so 2888x3600 pixels.
In a nutshell, Aperture really chokes on these files. It can handle 10 mp JPEG's OK, or 6 mp RAW files OK, but 10 mp RAW files are just a bit too much for it. Loading an image can take a long time, and as adjustments add up it really bogs down. I basically can't use sliders for anything, I just have to type in a value or click along the slider bar and let it jump there. Rotate is completely unusable. It still WORKS, but it's just slow and inefficient. Exporting JPEGs for uploading to my website takes painfully long.
I bumped my RAM up to 2 gb a few months ago, and it hasn't made as much of an improvement as I'd hoped. Of course Aperture and OSX have the tendency to gobble up whatever RAM they can, and I suspect the machine will still end up paging out at some point no matter how much RAM I add.
Hard drive access doesn't seem to be too much of a problem, at least until the memory starts paging anyway. I have an ok amount of capacity so far, but my gut is telling me that this isn't the bottleneck. From everything I've read on the forum here, I suspect it's my lame graphics card. While I wouldn't mind having 4 gb of RAM and 1 tb of hard disk, I doubt that's going to help me as much as a Radeon X800 XT would in the near-term. Do you all agree with that? Is that the only real solution, this being an AGP Mac with an ADC monitor?
As much as I'd like a new Mac Pro, I just don't see that happening. What I'd want would be in the $3,000-4,000 range, and some of my workhorse programs are not universal yet. I still use Photoshop 7, Illustrator 10, and GoLive 6, so I'd need to up to CS3 for full compatibility. $$$ I do some CAD work with PowerCADD, and that's not scheduled to go universal for a while yet. Then there's my one favorite game, SimCity 4. I did download a beta universal binary from Aspyr, just to see if they'd fixed any of the other long-standing bugs in the program (they haven't). SimCity is really the only other place where I've been disappointed in my computer's performance. I think it's more processor bound than Aperture is in this case, but a better video card should certainly help it some. I do also have a few classic programs that I need to access from time to time (namely ArcView), which are pretty processor intense. Thus it doesn't look like taking the plunge to an Intel Mac would be a good idea just yet. Maybe in another year or so.
I did have a chance to play with Aperture on a Mac Pro at the Apple Store a month or so ago. While it wasn't glass smooth with the 10 mp files on the machine, it was certainly a lot better than my computer, just not worth the price of a whole new machine. Does it look like I'm on the right track here, or might there be a different area I can optimize performance?
Thanks

I agree, if you can find a video card, that would help a lot.
On the other hand, You might consider getting a iMac 20" and selling your current machine. I have a iMac 20" with 2 gig of ram and it runs Aperture very well. You can get a deal on one of Apple's Refurbished units too. The 24" has the better video cards and 800FW. But, if money is the issue, I would buy the 20" and upgrade your software. Again, with Aperture, buy the best video card that you can. You will love Photoshop CS3.
I hope this helps.
Kevin Hawkins

NI Digital Electronics Board DAC and ADC access from Multisim

Is it possible to use the ADC and DAC functionality of the NI Digital Electronics Board from a circuit designed in Multisim?
I would like to have my students be able to digitally sample an audio input, perform transformations on the data stream, and listen to the effect. Nothing particularly fancy.
Thanks,
-Bret Wood

Hello,
In order to use the ADC/DAC you need to define a protocol and this goes beyond the scope of the PLD schematic in Multisim.
LabVIEW can be used to accomplish this, there are some examples that you can use as reference, they can be found in the NI Example Finder.
Regards,
Fernando D.
National Instruments

Question about myRio Hardware (ADC/DAC)

Hi!
I'm interested in new myRIO product. But there is one unclear question:
What is the ADC-DAC responce time on myRio platform ?
I mean experiment like this:
ext signal (meander) -> (ADC-myRIO-DAC) -> ext scope chan1
ext signal (meander) -> ext scope chan2
What's the difference (ms/us)?
Is it a constant value?
I found (USER GUIDE AND SPECIFICATIONS
NI myRIO-1900) that ADC is 500Ksps capable and DAC is 345Ksps capable.
Does it mean that 1/500K+1/345K responce time is achievable ?
Is ADC/DAC connected to PS (Processor Subsystem) or PL (Programing Logic) parts of Zynq IC in myRIO ?
I can little explain what I mean:
PL part is FPGA fabric and ADC-DAC transformation has relatively small constant time,
PS is ARM core and ADC-DAC transformation has undetermined delay because of OS/interrupts/etc.
thanks a lot!

Then I connected AI to AO inside one Loop in sequence manner.
And I got 4 us time which is smaller (about 1 us) than expected (2 us + 2.8 us = 5 us).
What kind of optimizations was performed ? It is a little bit strange time.
ADC-DAC-seq-1 picture represents signal transfer through myRio.
Attachments:
AI-AO_seq.png ‏28 KB
AI-AO-seq.jpg ‏1597 KB
ADC-DAC-seq-1.jpg ‏1514 KB

Quote Report - Performance

I have created a quote report with narratives around the opportunity, opportunity-product, and account information. The report contains a pivot table.
I'm getting very hit or miss performance results on the report. Sometimes the report runs faster for all opportunities compared to when its prompted with an opty id from a web link.
Any thoughts? There doesn't seem to be one column that makes a difference.
Also this is not an analytical report as the quotes need to be generated same day.

Hi Shaik,
Please remove all the join select queries and use 'for all entries' varaiant of the select query. Check whether you can create and use indexes in ur queries.
Thanks and Regards,
Saurabh Chhatre

15" ADC to Performa?

Similar Messages

Maybe you are looking for