Raw GPIB and VISA commands

Hi,
i have a software, written by an external company in labview 6, to
control several devices. But I dont have the block diagrams. This
software use VISA calls to communicate with a profile 800 mainframe.
Now I want to set an parameter of the mainframe via GPIB raw command.
I can integrate my own VIs in our software.
So I have written my VIs to send and read an GPIB-string (with GPIB
write and GPIB read) and within Labview all is running fine.
But if I use this VIs within our software, I get an GPIB-error 6. At
this time there is no other communication in background with this
device. But if I start Labview and communicate with my VIs once, then
my VIs work in our software too.
Do I have a problem with initialization?
What can I do to solve
my problem?
Regards,
Uwe Roessner

Hi Uwe,
It seems like it could be an initialization issue. Perhaps your VI does an initialization that the software doesn't do, but is necessary for your VI to run. I would definitely consider that. According to GPIB Error Codes document:
EABO (6)
Error Condition: I/O operation aborted.
Description: EABO indicates that an I/O operation has been cancelled for some reason.
Possible Cause: The EABO error is usually the result of a timeout during a read or a write operation, but it can also be caused by calling the ibstop function, the ibclr function, or similar functions while an I/O operation is in progress. You may receive a timeout during write operations with a PCI-GPIB board, if the PCI bus mastering (an option in the BIOS of your computer) is not enabled. You may receive a timeout during read operations, if the instrument you are reading from did not understand the previous command, so it has nothing to write to you. There are a few reasons why the instrument may not have anything to say:
The message to the instrument may have been misspelled. For example, "*IDN?" is a common identification query for IEEE 488.2 compliant instruments. It is easy to misspell this message as "*IND?", which the instrument will not understand, so it will not generate a message string for you to read from the instrument.
The message to the instrument may contain a command that the instrument does not understand. For example, the "*IDN?" message from the previous example is only understood by IEEE 488.2 compliant instruments. If your instrument is an older, non-IEEE 488.2 compliant device, then it will not understand "*IDN?", so it will not generate a message string for you to read from the instrument.
The instrument may use a particular EOS (end of string) character as its termination method, but you may forget to append this termination character to your message. For example, if your instrument expects a linefeed as the EOS character, then "ID?" will not work, but "ID?\n" (where \n represents a linefeed in IBIC) will.
You may expect to see EOI (end or identify, one of the five bus management lines) as the termination method, but if the instrument does not set the EOI line when it finishes sending its message, any read operation that you perform will time out.
Solutions:
Make sure that your messages consist of commands that the instrument understands. Check your device's user manual for a list of possible commands.
Verify that you are using the correct termination method for your instrument. Byte count (where you expect to receive a certain number of bytes in a message) is always used, but some instruments use EOS and byte count, some use EOI and byte count, and some use only byte count. Check your device's user manual for the possible termination methods to use with your instrument.
If EOS is the termination method, then be sure to append the termination character to the end of your message. You can specify the termination character in the GPIB Configuration Utility, but the NI-488.2 driver will not automatically append it for you!
Lengthen the timeout period for I/O operations using the ibtmo command.
If you receive all of the data and get an EABO error, then look for a particular end of string character (e.g., linefeed or carriage return) and configure the GPIB board to terminate the read on that character using the ibeos function.
Hope this helps.
Anu Saha
Applications Engineer
National Instruments
Anu Saha
Academic Product Marketing Engineer
National Instruments

Similar Messages

Output decimal number through GPIB or VISA

I was wondering if it is possible to output a decimal number, as in not a string, through the GPIB or VISA commands. I am trying to communicate with a machine that I think wants to get a number, and can't understand what I am sending when it is in a string format.
thanks

It is possible to transmit such a number over GPIB. I would double check the instrument manual for what it requires. I'm going to assume that you are using a long to represent a floating pont number. Here is some example code for how you would pass this number to the GPIB ibwrt() function.
int ud = ibdev(board,PAD,SAD,timeout,eot,eos);
long myNumber = 4.2;
ibwrt(ud, &myNumber, sizeof(long));
Essentially, the driver will break down the 32-bit number into 4 8-bit chunks.
Craig A.
National Instruments Engineer

When using GPIB hardware, do I need the exact driver[HP-3478a] or can I use simple raw GPIB-read or 488.2-read commands to take measurements?

If so, which would I use in order to take a reading from a lab instrument?
GPIB-read or 488.2-read commands to take measurements?

GPIB and 488.2 are the same thing, so the question if kind of moot. If you have a driver for the instrument then that's the best place to start, as it's quite likely to have been debugged and worked out. You can, however, code up your own communication. You would want to use VISA rather than the lower-level 488.2 commands, as this is the preferred API for programming. VISA is just a layer that sits on top of GPIB and allows you to write code so that you can communicate with a device via a serial or GPIB interface.
You should take a look at the examples that ship with LabVIEW as there's a couple that do basic communication using VISA functions.

NI VISA TekTronix RSA3408A "Free Run" and "Stop" Commands?

Hello
Is anybody clued up on the "FREE RUN" and "STOP" commands for TekTronix devices? Particularly the RSA3408A, if not, I'll try anything.
Thank you in advance!

well, Have you read the manual for that device?
Tektronics (for some reason) requires you to register to download the manual I'll leave that to you I get enough spam from Tek
http://www.tek.com/spectrum-analyzers/rsa3000/rsa3303b-manual/rsa3000b-series
Jeff

How do I correctly time while loops using SCPI and VISA/Ethernet communication to send DC current Values to a Power supply?

I'm rather new to using labview and I having an
issue with a test Data Aquisition lab I'm trying to setup using a
Keithley 6221 AC/DC current source and a basic PCI M-series NI-DAQmx.
First of all, I'm looking to update the current value on a power
supply at a rate of atleast 10Hz and I'm using SCPI commands and VISA
communication through ethernet to do so. Attached below is the VI I
have written.
The issue I'm having is this:
My VI will
loop through the values fine in software, or so it seems. I am unable
to get the Power supply to update sequentially if I don't set my loop
delay to anything greater than 130ms. If I try to run the loop faster
it starts skipping values instead of counting 1,2,3,4,5,1,2,...etc. it
goes 1,2,4,5,2,4,1,2 on the display of the power supply and my DAQ unit
also skips these values so I know that the number just isn't getting
read to the Power supply in time. I was wondering if this was due to
my sloppy programming or if it is a hardware issue, my computer or the
method of communication to the power supply? Is this due to the fact
that I'm using ethernet and VISA communication? Is there a faster way
to communicate or is GPIB faster? Any input at all would be extremely
helpful.
On a side note: Right now I'm using an pre-determined
array of values that I can update on the fly but in the future this
with be put into a closed-loop control system. The value for the
power supply output will be determined by the loop and sent that way.
Attachments:
basic DC loop 6221 Keithley.vi ‏145 KB

Also, one of the string constants is NOT set to '\' Codes Display. Here is an alternative method of calculating the index. I removed the DAQ and VISA stuff since I could not run it.
Lynn
Attachments:
basic DC loop 6221 Keithley.2.vi ‏16 KB

GPIB and RS232 communication problems

I've been having several "interesting" problems with GPIB and RS232 communications in LabVIEW VIs. Some I'll mention at the end for curiosity, but right now I'm facing a rather big problem. I'm essentially self-taught at doing LabVIEW (using 8.5.1 right now), but by now I've had a lot of experience as their either has not been any drivers or pre-made VIs for the instruments I've needed or I've not been able to get the available drivers to work and had to write my own anyway (such as with the HP 3458A), but nothing seems to be working right now. I'm not at work, but we typically find forum sites blocked anyway (I can't even download the NI drivers at work since they house them on a ftp server, go figures) so I can't give the VI itself (it wouldn't be easy to get approval even if I could) so the best I can do right now is in words describe everything I've tried. I will be happy to post follow-ups of specific details if I can if they would be helpful.
I've been working on a routine to read data from an MKS 670 Signal Conditioner/Display with a MKS 274 Multiplexer with 3 connected MKS 690A Baratrons. Previously I've worked on programs using other older displays and the analog outputs which were being read by a DAQ card, but for a new project it was decided to try and just read the data directly. I first worked with a unit with just an RS232 Serial Port which I managed to get to work, but had so much problems with garbage readings and having to add checks and re-reads that by the end no matter what delays I added between each reading and how simplified the command routine down to just 2 sequences and the read that it took at least 10 seconds to get 1 reading from each channel.
Figuring maybe it was a limitation of the serial communications for these instruments I tried to re-work it for a unit with a GPIB port with which I'm actually much more familiar. The problem is that I cannot get anything at all from the unit through GPIB. Everything even the bare-bones built-in GPIB CLR function times out with no response from the instrument no matter how long I set the timeout limit and it also freezes the entire GPIB bus as well. It isn't a waiting issue as it freezes on the very first command. The GPIB initialization function seems to work (I typically find this to be unnecessary), but the instrument itself doesn't even respond with a status code. I've also tried just the basic GPIB write functions with even just passing the <cr> and <lf> characters as well. In Measurement and Automation Explorer most of the time the instrument won't even appear when doing search for instruments and when it does it shows as not responding to the *IDN? command (yes I've messed with the EOI, EOS, etc settings and I've even changed the GPIB address even though when it gets this far it confirms that I have the correct address) and even tried manually doing the *IDN?, *RST, and *CLR commands even with <cr> and <lf> characters which the manual for these units clearly states are compatible commands and NI SPY and everything show no response at all. I've tried 2 different GPIB units, 3 different computers including several that are not online and haven't been updated for a while, and using older LabVIEW versions, extensive re-booting and resetting of computers and devices and still nothing. I'm using an NI GPIB-USB-HS GPIB to USB adaptor which I've used extensively on other systems and even re-connected to those systems and everything worked fine. When I hooked up equipment that I knew was working, it would either freeze the entire GPIB bus until well past whatever timeout setting I set at which point all the instruments would appear, but none responding to *IDN? queries or nothing would appear at all, or if I manually turned it off when frozen the other instruments would work and most even respond to the *IDN? queries. The same goes for both of the GPIB instruments of this type that I tried and again for different versions of LabVIEW, difference computers (all Windows XP though), and every GPIB configuration setting I can find to mess with in every combination.
Any thoughts or suggestions would be greatly appreciated. I've had all sorts of weird problems with equipment and LabVIEW (you've got to love undocumented design features) that have frustrated me before, but I've never had an instrument never respond at all especially a GPIB one. Getting garbage yes, no response at all, no.
The side side issues I'm just mentioning as they may be related, but I'm really interested in the above as I have working solutions for these:
One I've had is with a Hart Scientific (prior to being bought by Fluke) 1560 Black Stack that would continually stop responding to GPIB commands when on a continual read function taking readings just every 4 seconds with 250ms between each GPIB read or write command but for up to hours in total and the times it stops responding are random as far as I can tell. I even started sending the *RST command before and after every read or write command and still it freezes. The only thing is to manually turn it off and then back on or manually go through the menus and manually trigger the GPIB reset routine at which point it immediately starts responding. However, when I got sick of having to babysit it and just decided to try the RS232 serial port (as that is all it has without the extended communications module) it works fine no problem and I can even get readings slightly faster from it. Using a Hart Scientific 1529 Chub-e it could give me data on all 4 channels every second without problems. I just find it a bit odd.
When I couldn't get any of the HP 3458A driver packs to work to even give a single measurement reading and just made my own using basic GPIB read/write commands using the programming manual I still have a few interesting problems in randomly when reading off the full possible 256 bytes on the bus and clearing the bus I often find garbage partial readings on the bus every now and then. I've added a few routines to do some basic checks, but it is annoying. What is really weird is when just doing basic DC Voltage reads the "-" sign will randomly be dropped from some readings (started as about 1 out of every 5, down now to about 1 out of every 10). Fortunately I'm taking several readings and averaging and taking the standard deviation with limits on the deviations and basically added a routine to say if there is even 1 negative number take the absolute value of all then make all negative, but again I find it weird.
Thanks.
-Leif
Leif King
Metrology Engineer
Oak Ridge Metrology Center

Greetings Leif,
I understand you have completed extensive troubleshooting techniques to pin-point the problem with the GPIB communication. To begin, I want to ask you a few questions to help me understand your set-up and the issue at hand.
1) Is the NI GPIB-USB-HS cable the one which cannot communicate with your instrument?
2) When using the GPIB-USB-HS, does the GPIB interface show up in MAX?
3) If yes, does the instrument appear in MAX after scanning for instruments (from what I understand in your issue, it does so in an intermittent manner..)?
4) What driver version of VISA do you have installed in your computer?
5) Are you able to communicate to the same instrument using another GPIB cable?
Thank you for trying out some of these steps again, but we want to make sure we rule out other aspects in the systems which might be affecting the GPIB communication.
As for your other issues, please post seperate threads for each so we can help you accordingly. Thanks!
Sincerely,
Aldo
Aldo A
Applications Engineer
National Instruments

Programming Agilent N5242A throgh VISA command using LAN

hi,
I'm trying to program Agilent N5242A throgh VISA command using LAN with no success.
The connection to the N5242a is working but when I'm using the visaWrite command it doesn't response.
I used Agilent "connection Expert tool" and it worked.
I tried to use Measurment & automation but there is no LAN option there, I have version 4.5.
This is what I tried to do:
status = viOpenDefaultRM (&defaultRM);
   if (status < VI_SUCCESS)
      printf("Could not open a session to the VISA Resource Manager!\n");
      exit (EXIT_FAILURE);
   /* Now we will open a session via TCP/IP to ni.com */
   //status = viOpen (defaultRM, "TCPIP0::ftp.ni.com::21:OCKET", VI_NULL, VI_NULL, &instr);
   status = viOpen (defaultRM, "TCPIP0::169.254.73.18::5025:OCKET", VI_NULL, VI_NULL, &instr);
   if (status < VI_SUCCESS)
      printf ("An error occurred opening the session to TCPIP0::ftp.ni.com::21:OCKET\n");
      viClose(defaultRM);
      exit (EXIT_FAILURE);
   viSetAttribute (instr, VI_ATTR_TCPIP_NODELAY, VI_TRUE);
// status = viWrite (instr, "INIT:CONT ON", 13, &count);
      status = viWrite (instr, "*RST",4 , &count);
      status = viWrite (instr, "SENSe1:FREQuencyTARt 4000000000", 33, &count);
      status = viWrite (instr, "SENSe1:FREQuencyTOP 7000000000", 32, &count);
Best Regards
Israel
Best Regards
Boris

TCPIP SOCKET (or SCPI-Raw) connection normally requires termination code (Line Feed, 0x0A) being sent, but not found in your viWrite() call.
Write as like:
status = viWrite (instr, "*RST\n", 5, &count);
Also I think viPrintf() will be easier than viWrite() for ASCII write, because you dont have to specify the byte-length to send. Once you set buffer operation attributes like below:
status = viSetAttribute( instr, VI_ATTR_WR_BUF_OPER_MODE, VI_FLUSH_ON_ACCESS);
status = viSetAttribute( instr, VI_ATTR_RD_BUF_OPER_MODE, VI_FLUSH_ON_ACCESS);
then you can now use viPrintf() like below:
status = viPrintf( instr, "SENSe1:FREQuencyTOP %ld\n", (ViInt32)7000000000);

I want to edit my raw images on cs5 photoshop. But when I go to open the .CR2 file it says '' Could not complete your request because the file appears to be from a camera model which is not supported by the installed version of Camera Raw. Please visit

I want to edit my raw images on cs5 photoshop. But when I go to open the .CR2 file it says
'' Could not complete your request because the file appears to be from a camera model which is not supported by the installed version of Camera Raw. Please visit the Camera Raw help documentation for additional information. ''
When I go to updates in photoshop help i try to update photoshop and photoshop camera raw but it then says
'' Updates could not be applied the error log file may help you in identifying the problem. Then, try updating again. If the problems persist, contact customer support for further assistance.
Photoshop Camera Raw 8.7.1(CS6) There was an error installing this update. Please quit and try again later. Error Code: U44M1I216 ''
I dont know how to get around this please help

CR2 files from which Canon camera?
Supported cameras are listed here
Camera Raw plug-in | Supported cameras

After reinstalling CS6 the bridge photo downloader isn't able to read raw files and fails to convert the raw files to DNG. Previously downloaded raw files, now DNG, open up successfully in Camera Raw 7. How do I get the photo downloader to read and conver

After reinstalling CS6 the bridge photo downloader isn't able to read raw files and fails to convert the raw files to DNG. Previously downloaded raw files, now DNG, open up successfully in Camera Raw 7. How do I get the photo downloader to read and convert raw files. MacBook Pro with Snow Leopard. No such problem before this reinstallation.

You should install Camera Raw 4.6.
Visit this page and follow the instructions carefully:
PC: http://www.adobe.com/support/downloads/detail.jsp?ftpID=4040
Mac: http://www.adobe.com/support/downloads/detail.jsp?ftpID=4039
-Noel

CS5 RAW Could not complete your request because the file appears to be from a camera model which is not supported by the installed version of Camera Raw. Please visit the Camera Raw help documentation for additional information.

I rented a Nikon D600 & D610 and CS5 cannot open the RAW files, i do not have any issued with my D700 RAW files. I am getting this error message -
Could not complete your request because the file appears to be from a camera model which is not supported by the installed version of Camera Raw.
Please visit the Camera Raw help documentation for additional information.
Can anyone please help?

yellowmledbetter wrote:
Sorry, I am on a MAC. I downloaded the link you provided and it's giving the same error message as above. Running CS5.
The error message you gave is from Camera Raw. I thought you said that DNG Converter didn't work?
The link I gave you is an article on getting your raw files to open in Camera Raw. Did you read it? I lazily gave you the link because this is one of the most common problems in this forum, and I get tired of saying the same thing over and over again. I could break it down for your specific case, but I was hoping you could read through the article and work it out for yourself.
But, here goes:
Your cameras are newer than your raw converter, so it won't understand them.
CS5 comes with Camera Raw 6, which can only be upgraded as far as 6.7.1. You can find out which version of Camera Raw you are running in three ways: in the settings title bar (Cmd-K), in the plug-in title bar (press F to start/stop full-screen mode to reveal the title bar), or Photoshop's Help menu (About Plug-ins).
Downloading raw files from newer Nikon cameras with old versions of Nikon Transfer will actually make them unreadable in Adobe software. They can be fixed with a free utility. Again, it's all in the linked article. You should be using up-to-date Nikon Transfer, or Adobe Photodownloader to avoid this problem.
All being well, you have good raw files on your computer. You can convert them to dng using Adobe DNG Converter. IF you are on OSX Leopard or Snow Leopard, you CAN'T use the latest version, because Adobe stopped support. But, if you ARE on a later OSX, you can download DNG Converter 8.6.
DNG Converter is designed to convert FOLDERS of raw files at a time. You select a folder of raw files, and tell it to create DNG copies. BUT, you have to set up the converter before you start using it...
If you load up DNG Converter, you'll notice a button labelled "Change Preferences". Clicking this, you'll see the first option is "Compatibility". Here, you must select the appropriate setting for the version of Camera Raw you HAVE (see above). If you can't work this out, just pick "Camera Raw 5.4 and later". THEN pick a folder of raw files and convert them to DNGs.
All the above is already in the article, but I gave you a personalised response. If you still can't get it to work, please give us more than one sentence. Tell us exactly what you tried, and describe exactly what happened. Which version of OSX you're running, what device and software you downloaded your raw files with, how you used DNG Converter, and so on.
I really should be in bed.

Aperture 3: Deleting raw files and making the jpeg my new master-

Aperture 3 has made some great strides in making the following possible ( I posted this originally in 2007):
What I'd like to do is shoot everything in raw + jpg, and then keep the raw files only for the important shots.
I really like having the option of raw processing, but the storage demands are very heavy. If I could just make a selection of photos in a roll, and have a command to delete any unneeded raw files from the selected photos, while keeping the original jpgs as master, that would be great.
Also, it would be great to be able to manipulate a raw file, and then when I'm satisfied with the image, to render a high-quality jpg from that raw file & make the jpg the new master, and then delete the raw file to free up disk space.
Basically, I want the raw file safety net for everyday images, without gobbling up gigabytes of disk space <<<<<
With Aperture 3, I can finally change the master to the jpg file, which solves part of the problem. But I still want to be able to manipulate my raw file, and render a new high-quality jpg master.
Why don't Aperture / Lightroom do this? To me at least, it seems an obvious feature.

I had a chance to talk to product managers from both Apple & Adobe about this at PhotoPlus Expo in NYC a couple years back. Both seemed receptive, but here we are - years later - no progress.
I think part of the problem is that there's a purist mentality about RAW files. One should always shoot them - and then keep them forever- after all- they're your negatives!
But what about event photography? Or weddings, as you pointed out? It makes no sense to burden your workflow & backup system with 4GB of RAW files of people grinning into the camera. Once the adjustments have been made, the RAW files are just a ball & chain on your data management. And let's not forget, once you really know what you're doing, your jpegs should be good most of the time anyway.
I want RAW files as a safety net for errors in exposure and white balance. Once I know I have good photos, I don't need the safety net anymore- at least not at the price of all that hard disk space and transfer time for online backup. Of course, for my fine art stuff and important documentary work, I'll always keep the RAWs permanently. But not for routine parties/events.
You put your finger on the problem with re-importing jpegs as a solution. You lose your metadata- rankings/album memberships, etc. This is no solution!
What I want is simple, and it would be immediately useful to countless photographers:
1) Let me batch-delete RAW files when the jpegs are ok.
2) Let me do adjustments on my RAW file, render out a high-quality jpeg, and make the jpeg my new master.
Whoever does this first - Aperture or Lightroom - that's the product I'll use.

IPhoto not showing RAW pics, and crashing on Create New Library

hi there
i was just organising (tagging, deleting) pics in iPhoto 9.1 when the RAW pics started showing up as just blank placeholders - i'll clarify that: they were showing previously, however my perception of them 'disappearing' may have been between iPhoto sessions.
my iPhoto library is mostly JPEGs, with the RAW pics being a recent addition courtesy of a Canon EOS 5D MkII. the iPhoto library resides on a 500GB external harddrive. the iPhoto library was backed up by way of copying the entire iPhoto folder from the 500GB external harddrive to a separate 1TB external harddrive - this back-up process was done prior to the addition of more recent RAW pics, and the memory card from which all the RAW pics came from has been wiped several times since. some RAW pics taken in December 2011 are showing; none of the RAW pics taken in January 2012 are showing.
what i've done so far:
1. Option-Command-opened iPhoto and ticked all boxes to rebuild the library and the RAW pics are still not showing. this rebuild process has been done at least three times now.
2. opened the iPhoto Library (via Show Package Contents) and confirmed that the pic files are still there in the Masters folder. (they are identified by the date the photos were taken, the CR2, and can be viewed in Preview.)
3. installed the iPhoto 9.2.1 Update and the RAW Camera Update 3.9, with no change in the RAW pics' visibility.
4. Option-opened iPhoto and -
a. - created a new library (on the 1TB external HD, separate to the 'backup') into which i -
b. - tried to import the entire iPhoto Library from the 500GB external HD but -
c.   this import ended in an "iPhoto quit unexpectedly" message. unfortunately, i did not keep the error report for this.
5. Option-Command-opened iPhoto to create a new library on the 1TB HD but this has ended abruptly in an "iPhoto quit unexpectedly" message. this has happened twice, and i have kept one of the error reports.
6. downloaded and installed the latest iPhoto Library Manager and -
a. - tried to Rebuild the library but -
b. - iPhoto quit unexpectedly - i have kept this error report - while -
c. - iPhoto Library Manager gave the error message "'iPLM'/'ADDK' (returnID 3)".
interspersed with the above steps, i have run Disk Utility Repair Permissions after each crash.
so.
i know the files are still there. but iPhoto won't show them. i've trawled these forums and done - or tried doing - some of the fixes, all to no avail.
please can someone help.
david mamea

this is from the last error report (step 5 of my 22Jan12 1142 post above):
Process:
iPhoto [2588]
Path:
/Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier:
com.apple.iPhoto
Version:
9.2.1 (9.2.1)
Build Info:
iPhotoProject-628000000000000~3
Code Type:
X86 (Native)
Parent Process: launchd [2471]
Date/Time:
2012-01-22 11:11:23.578 +1300
OS Version:
Mac OS X 10.6.8 (10K549)
Report Version: 6
Sleep/Wake UUID: A5D90A7D-4923-4807-925C-7572A3FDC25F
Interval Since Last Report:
225 sec
Crashes Since Last Report:
1
Per-App Interval Since Last Report: 3 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:
9111BA25-4BC3-453F-8171-C05AFE66124B
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000058723f2f
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0   com.apple.ImageIO.framework
0x94afd4cb CFMutableDictAddProperty + 101
1   com.apple.ImageIO.framework
0x94a22aba CGImagePluginReadRawXMPProps + 60
2   com.apple.ImageIO.framework
0x94a823ac _CGImagePluginInitPSD + 1769
3   com.apple.ImageIO.framework
0x949e5334 makeImagePlus + 690
4   com.apple.ImageIO.framework
0x949eba0e CGImageSourceCreateImageAtIndex + 176
5   com.apple.iPhoto
0x00099e52 0x1000 + 626258
6   com.apple.iPhoto
0x00099d68 0x1000 + 626024
7   com.apple.iPhoto
0x009bb203 0x1000 + 10199555
8   com.apple.iPhoto
0x00069c0c 0x1000 + 429068
9   com.apple.iPhoto
0x00067dc8 0x1000 + 421320
10 com.apple.iPhoto
0x000664ce 0x1000 + 414926
11 com.apple.iPhoto
0x000663f9 0x1000 + 414713
12 com.apple.Foundation
0x98735409 __NSFireDelayedPerform + 537
13 com.apple.CoreFoundation
0x971c9a6b __CFRunLoopRun + 8059
14 com.apple.CoreFoundation
0x971c73f4 CFRunLoopRunSpecific + 452
15 com.apple.CoreFoundation
0x971c7221 CFRunLoopRunInMode + 97
16 com.apple.HIToolbox
0x952c2e04 RunCurrentEventLoopInMode + 392
17 com.apple.HIToolbox
0x952c2bb9 ReceiveNextEventCommon + 354
18 com.apple.HIToolbox
0x952c2a3e BlockUntilNextEventMatchingListInMode + 81
19 com.apple.AppKit
0x92e8d595 _DPSNextEvent + 847
20 com.apple.AppKit
0x92e8cdd6 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
21 com.apple.AppKit
0x92e4f1f3 -[NSApplication run] + 821
22 com.apple.AppKit
0x92e47289 NSApplicationMain + 574
23 com.apple.iPhoto
0x0001159a 0x1000 + 66970
24 com.apple.iPhoto
0x00010a29 0x1000 + 64041

Adpatch: Error running SQL and EXEC commands in parallel

Hi
I am applying R12 RUP2 to an instance at the moment. I had an OS crash (I'm running R12 on Linux on VMWARE) and on reboot attempted to restart the patch.
I now get an error as follows:
Error running SQL and EXEC commands in parallel
I must admit, I'm not a DBA, so if anyone has any ideas or has seen this before then it would be most appreciated!
Thanks
Chris

Hi Adith
The patch is 5484000, RUP 2 for E-Business Suite R12
Here's the adpatch output:
Start date: Wed Sep 12 2007 15:15:14
0 "left over" javaupdates.txt files uploaded to DB: Wed Sep 12 2007 15:15:14
0 patches uploaded from the ADPSV format patch history files: Wed Sep 12 2007 15:15:14
Uploading information about files copied during the previous runs ...
0 "left over" filescopied_<session_id>.txt files uploaded to DB: Wed Sep 12 2007 15:15:14
****************** E N D O F U P L O A D ******************
End date: Wed Sep 12 2007 15:15:14
Already asked for the name of the patch directory.
(The answer was: /oracle/patches/5484000)
Already asked for the name of the patch driver file.
(The answer was: /oracle/patches/5484000/u5484000.drv)
Reading release list save file...
Done reading release list save file
Log and Info File sync point:
Wed Sep 12 2007 15:15:15
Turning off actions that reference unrecognized products.
Log and Info File sync point:
Wed Sep 12 2007 15:15:15
End of unrecognized products checking.
(The number of parallel workers is: " 2 ")
AutoPatch will run in parallel mode.
Did not need to apply new applterr.txt.
Skipping...
Determine directories to create for Specified driver
since no such action is present for this driver file
Skipping...
Determine Oracle Reports libraries to generate for Specified driver
since no such action is present for this driver file
Skipping...
Determine if need to generate message files for Specified driver
since no such action is present for this driver file
Skipping...
Create Directories for Specified driver
since no such action is present for this driver file
Number of invalid objects: 31057
Running SQL scripts and EXEC commands...
Determining which SQL and EXEC commands to run...
Validating PL/SQL direct execute exceptions file ...
Done validating PL/SQL direct execute exceptions file.
SERVICE_NAME/INSTANCE_NAME : [VIS]
connect_string : [(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ebusr12.chriseebee.me.uk)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=VIS)))]
Done determining which SQL and EXEC commands to run.
Running SQL and EXEC commands in parallel...
Creating the AD_UTIL_PARAMS table...
Table AD_UTIL_PARAMS already exists, so dropping the table and recreating it.
Creating FND_INSTALL_PROCESSES table...
Already created fnd_install_processes table
Already created FND_INSTALL_PROCESSES_U1 index.
Already created AD_DEFERRED_JOBS table
Already created AD_DEFERRED_JOBS_U1 index.
Writing dependencies of jobs to run to appldep.txt file...
There are now 7569 jobs remaining (current phase=A0):
0 running, 5 ready to run and 7564 waiting.
Reading completed jobs from restart file (if any).
There are now 3474 jobs remaining (current phase=A18):
0 running, 1 ready to run and 3473 waiting.
Determining which java executables are supported by adJavaWorker...
Starting worker processes.
Worker process 1 started.
Worker process 2 started.
Checking if all jobs have their actual and symbolic arguments in sync....
Done.
Writing jobs to run to restart file.
Reading jobs from FND_INSTALL_PROCESSES table ...
Running: file adobjcmp.sql on worker 1 for product ad username APPLSYS.
AutoPatch error:
The worker should not have status 'Running' or 'Restarted' at this point.
Telling workers to quit...
************* Start of AD Worker session *************
AD Worker version: 12.0.0
AD Worker started at: Wed Sep 12 2007 15:15:34
APPL_TOP is set to /oracle/VIS/apps/apps_st/appl
************* Start of AD Worker session *************
AD Worker version: 12.0.0
AD Worker started at: Wed Sep 12 2007 15:15:34
APPL_TOP is set to /oracle/VIS/apps/apps_st/appl
All workers have quit.
AutoPatch error:
Error running SQL and EXEC commands in parallel
You should check the file
/oracle/VIS/apps/apps_st/appl/admin/VIS/log/adpatch.log
for errors.

Raw Device and ASM configuration

Can any body send me steps/commands to configrue Raw device and then ASM on top of it for RAC?

Try this:
http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14231/storeman.htm#i1021337
And this for installing 10g RAC on RH:
http://www.puschitz.com/InstallingOracle10gRAC.shtml
Daljit Singh

Winusb and visa device issue

I have a system I am working on that communicates with some custom hardware via USB. I used the NI driver wizard to create some visa drives, and perform USB RAW writes and reads, and everything was working great. Unfortunately, I just found out that there is a whole other application written in C++ by someone else that also has to communicate with the same hardware on the same system. Their application uses WinUSB to communicate with the device, so currently the only way I know of to switch between the two applications is to uninstall the VISA drivers, and install the WinUSB drivers, or vice-versa, depending on which application one wants to use. This obviously isn't going to work long-term.
I'm not sure how to fix this so that we can use both application on the machine without having to constantly change the drivers back and forth. I thought about trying to call WinUSB.dll using LabVIEW, but I'm afraid that might get a little complication. I figured I can't be the first one to run into a problem like this before, so before I start down the WinUSB road, I thought I would check to see if anyone has any better ideas. I'm afraid trying to get at the source, or in anyway changing, the C++ application is not an option.
Thoughts? Ideas? Is calling WinUSB in LabVIEW my best bet?

Thoughts? Ideas? Is calling WinUSB in LabVIEW my best bet?
Most likely. Unless you have access to the source code of your other application and can change it to communicate to your device using VISA Raw. NI-VISA has a C API so it is technically possible.
Technically it is not so much WinUSB which is the likely problem but probably something in the application installation which registers WinUSB as the driver handler for your USB device resource. Except for filter drivers, which are chained into the driver chain by Window and for which Windows has a configurablle maximum limit of active filter drivers in the system, Windows only allows one driver to register for a specific device resource. So it would be technically enough to just change that registration entry to point to the currently desired driver.
However this registration API (SetupDI API and its friends) is quite cumbersome and the whole process is rather brittle as it easily can break with every new driver update. Also it would never allow to run both application in parallel, even if you make sure that they do not communicate to the device at the same time.
So calling WinUSB in LabVIEW is probably your safest bet. It won't be trivial, the WinUSB API is somewhat involved but it is definitely doable. The most difficult part is the implementation of your device protocol anyhow which you seem to have tackled already for the VISA raw mode, so I do not see real road blocks ahead, just some botherings about correct Call Library Node configurations

Raw GPIB and VISA commands

Similar Messages

Maybe you are looking for