Visa I/O error -107380729​8

Hi everybody! More VISA troubles, it seems.
I have a little module that goes a little something like this.
VISA write -> VISA read -> VISA flush -> VISA read again
This is because I send a message via a serial converter that loops back the request, so I have to flush it.
Now, I use this module (let's call it serial1) in another application that looks something like this:
VISA configure serial port > VISA serial break for 25ms > wait 25 ms > serial1 > do actions
OK. The thing is that serial1 works on it's own, but when used in the sequence above, I get an error -1073807298 from the first VISA read in serial1.
This is very puzzling and unexplainble to me.
Does anyone know why this might be?

Hi Jason! Thank you again for your answers and interest.
My answer comes later because I was assigned to another project this week and got back to my problem just today. I managed to solve that problem, it seems and I think I know the cause of it, too.
Long story short, the current, working solution can be seen in the attached image.
before I didn't use that while loop before doing the VISA read and I think the error was because, at the time it was trying to read, the required number of bytes was not present in the buffer. I think...
Anyways, that works now. I have another problem, though. After the sequence aabove, I perform another read using this sequence.
The problem is that it only reads up to 8 bytes. I know my messages are longer than this, but I can't explain why they are not received completely. Messages with 6 or 7 bytes are ok. Do you have any idea?
Message Edited by louis_nichols on 11-23-2006 09:12 AM
Attachments:
aaa.JPG ‏65 KB
bbb.JPG ‏27 KB

Similar Messages

  • Keep getting a pop up at the top of many websites I visit 'firefox security error content at *web address* may not load" I am using the most recent firefox and windows 7.

    Keep getting a pop up at the top of many websites I visit 'firefox security error content at *web address* may not load" I am using the most recent firefox and windows 7. This is happening at many sites, such as hotmail, google reader, and many others.

    Sorry, I don't think that is a message from inside Firefox, the wording doesn't sound correct - at least the beginning of that message. My "gut" thinks that is a MSN Live message to explain and compensate for their lack of security with a re-direct from a secure domain to an un-secure domain. ''(the end of that message)''
    {Ctrl + Shft + J} will open the Firefox Error Console - I'm curious what Firefox has to say about that situation. If you find the error message for that domain, you can right-click the message to '''copy''' it and then paste that error message here.
    Maybe '''TonyE''' or '''cor-el''' will be more familiar with the situation at Live and maybe at Google Reader, I don't use either of those services and have never seen a message like that myself.

  • I had a visit from General Error

    Not an army guy in uniform but a very 'uninformative' error message when doing media management.
    After 20 mins of creating files etc FCP 7 just stopped with this error "general error" message. So what was it telling me? "Sorry, computer says 'NO' so you will have to go and neck yourself"?
    Well I worked it out on my own and I live to tell the tale so as to save others from suicide.
    I made a copy of my original project and proceeded to dissect the one I was working on; I deleted the second half of the 1 hour timeline and proceeded with a media manage (clips 'off line' mode) and it worked. So this led me to believe there was some corrupt files or whatever in that part of the timeline.
    So I 'undid' that deletion and deleted the first half and proceeded with a media manage and it failed. So now I knew the corrupt clip was in the second half.
    I then dissected the second half as above until I got it down to about 10 clips. From there I just deleted 1 clip at a time until I got the offending item.
    I just reworked that item and was then able to do a complete media manage creating all necessary clips, bung it on a sata drive in a docking station and into the library it went; General Error would have been impressed, I guess you could say I "sorte'd it out.
    I have had similar problems in the past where there was more than one dodgy clip but using the procedure above and a little bit on 'logic' I was able to successfully get it done.
    I hope this technique helps others more than General Error.

    Sounds like you got it sorted out. Just be glad you didn't receive a visit from Colonel Panic ... which in itself can be a Major Pain.

  • VISA READ timeout error - multiple GPIB resources

    Hi,
    I am working on a 3 instruments GPIB network (optical attenuator, fiber amplifier, spectrum analyzer), controlled using VISA sessions in Labview. When run separately, the three corresponding VIs (which are located in three different Labview projects) work as expected. However, when they are ran simultaneously, one of them gives VISA READ -1073807339 timeout errors. These errors seem to happen when an other instrument is sending / receiving data / instructions at the same time as it is.
    The exact context for these error is either :
      -  an other VI is running, which includes sending several queries and reading the answers every 100 ms,
      - upon starting the failing VI, I get a  timeout error from one of the first subVI containing a VISA READ operation to be executed (sometimes initialize.vi (in state 1), sometimes one of the subVIs ran from the Idle state (state 0) upon timeout of the event structure).
    or :
      - the failing VI is running,
      - upon starting an other VI, which includes repetitively sending queries and reading answers, the failing VI throws an error from one of the first subVI containing a VISA READ operation to be executed (one of the subVIs ran from the Idle state (state 0) upon timeout of the event structure).
    What I tried :
      -  gradually increasing the delay between the VISA WRITE and READ operations for the relevant instrument (from 10 ms to 10s), to no avail. More puzzling is my obseration that, when this VI is run alone, increasing the WRITE / READ delay leads to the same timeout errors. I could not find any mention of such behavior through google and forum searches. Hopefully this can point to a solution to the main issue,
      - switching between synchronous and asynchronous VISA WRITE / READ operations,
      - reordering the GPIB network from a star topology to a linear topology (all three instruments do have different GPIB addresses in case anyone wonders).
    My thoughts :
    It seems to me that the error is related to a delay introduced between a VISA query and its associated read operation by the transmission of another query to another instrument in the same GPIB network. However I have no idea why transmitting a query to another instrument would introduce such a delay, or why this delay would lead to a timeout error (and only from one instrument, while the write / read VIs in each driver are basically the same). Hopefully a more experienced Labview-er will be able to shed some light on my issue.
    Included is the project containing the failing VI (main.vi) and the custom driver it makes use of. 
    Solved!
    Go to Solution.
    Attachments:
    Manlight EDFA Control - Failing VI.zip ‏73 KB
    EXFO FVA 3150 - Driver.zip ‏348 KB

    Thank you for your input crossrulz. This is indeed what I realized while looking into semaphores.
    Let me first make our architecture clear so that I'm 100% certain we are talking about the same thing. We have a NI GPIB-USB-HS GPIB Controller connected to a linear GPIB network of three instruments. I was convinced that a network allowing up to 15 instruments to be connected at the same time would allow for parallel operation, but it seems I was mistaken.
    I like how semaphores work, and I don't see any obstacle to gathering all these VIs into one project. My conception of a Labview project was that one Labview project was intended to gather subVIs, libraries and controls used in a more complex "main" VI, which would ultimately be made into a single standalone executable. It seems I was mistaken too and that a single Labview project should be used to gather several standalone VIs designed to work together, and their subVIs. Hopefully I got it right now.
    The other option that you suggest for accessing the same GPIB bus from different projects (having a TCP control interface running and controlling communications through the bus) might indeed be a bit overkill for what I'm tring to achieve, and I would need to spend too much time learning and developing it.
    A last option I looked into is the VISA Lock Async VI, but I don't understand yet if 1. locking the VISA session for an instrument in the bus would lock the entire bus ; 2. if it would be possible to use this approach with VIs running in different projects and 3. if it would not just yield errors when one VI is trying to access the locked GPIB bus instead of making it wait until the resource is available.
    I'll look further into these options today, but would appreciate any additional information / advice you might have. Thank you.

  • VISA read timeout error

    Good day to all,
    I have this problem with my LabView program. It is being used to interface with a Energy Meter to retrieve the data. I am able to execute "Open" and "Write" VISA, but am unable to execute "Read" VISA. Attached below is the screenshot of the error.
    EKI1521 is being used to interface serial connection from the meter to ethernet, connecting to the computer with
    labview program. Attached are the settings for the EKI1521.
    This is extracted from the main program after narrowing the problem down to the VISA Read function. The subVIs in this program are proprietary protocols of the meter and does not contribute to this Reading error.
    It might be interesting to note that I am able to run another program to interface with another meter using Modbus protocol. It also used the same EKI1521 with the correct VCOM settings. (This should free the EKI1521 from any faults). 
    Thanks & Regards,
    Andrew
    Attachments:
    1.png ‏169 KB
    2.png ‏210 KB

    Hi,
    Stop me if I make a mistake, but you don't set Visa properties in your Labview code (type, baudrate... etc).
    Best regards,
    V-F

  • GPIB locks up after about 15 minutes with a VISA Write Timeout Error

    I am using GPIB to control two electronic loads.  After about 15 minutes of runtime on the program, the GPIB communication locks up.  A probe reveals an error message about a Visa Write Timeout.  When this occurs, I have to stop the program, cycle the power on the two loads, and then restart the LabView program. When addressing the loads, I use the same routine every time.  1) Initialize communication, 2) Send command/request, 3) Close communication.  I thought I might have been overloading the GPIB bus, so that's when I added the close command after each sequence. However, it didn't seem to make a difference.  Could there be a compatability issue with the GPIB of the loads and the NI GPIB or Windows version? (I'm using XP and LV 10)  The electronic loads are older models, so I'm not sure how that impacts this scenario.

    Hi kcarbon80, 
    As this thread is over 2 years old, I do not know what solution was found for the previous problem being addressed, if any. However, if the device is locking up in the middle of your program, you may want to try clearing the device programmatically using the DevClear.vi that comes with the NI 488.2 driver. 
    I hope this helps. 
    Best Regards,
    Thomas B.
    National Instruments
    Applications Engineer

  • CRIO application works in interactive mode but broken VIs reported in error log when run built application on target

    I have been getting more than my fair share of grey hairs the past few days because of this. Over the past few months this almost never happened. Lately, after a seemingly minor change to some serial communications code, hardly a single build works without throwing errors like this:
    #OSVers: 6.3
    #OSBuild: Jun 6 2014, 09:14:16
    #AppName: /c/ni-rt/system/lvrt.out
    #Version: 14.0
    #AppKind: AppLib
    #AppModDate:
    InitExecSystem() call to GetCurrProcessNumProcessors() reports: 1 processors
    InitExecSystem() call to GetNumProcessors() reports: 1 processors
    InitExecSystem() will use: 1 processors
    starting LabVIEW Execution System 306708506 Thread 0 , capacity: 1 at [3507679466.00933790, (19:24:26.009337710 2015:02:24)]
    starting LabVIEW Execution System 306708507 Thread 0 , capacity: 1 at [3507679470.59560204, (19:24:30.595601929 2015:02:24)]
    starting LabVIEW Execution System 2 Thread 0 , capacity: 24 at [3507679481.25993776, (19:24:41.259937648 2015:02:24)]
    starting LabVIEW Execution System 2 Thread 1 , capacity: 24 at [3507679481.25993776, (19:24:41.259937648 2015:02:24)]
    starting LabVIEW Execution System 2 Thread 2 , capacity: 24 at [3507679481.25993776, (19:24:41.259937648 2015:02:24)]
    starting LabVIEW Execution System 2 Thread 3 , capacity: 24 at [3507679481.25993776, (19:24:41.259937648 2015:02:24)]
    Thread consumption suspected: 3 Try starting 4 threads
    starting LabVIEW Execution System 2 Thread 4 , capacity: 24 at [3507679515.59324312, (19:25:15.593243004 2015:02:24)]
    starting LabVIEW Execution System 2 Thread 5 , capacity: 24 at [3507679515.59324312, (19:25:15.593243004 2015:02:24)]
    starting LabVIEW Execution System 2 Thread 6 , capacity: 24 at [3507679515.59324312, (19:25:15.593243004 2015:02:24)]
    starting LabVIEW Execution System 2 Thread 7 , capacity: 24 at [3507679515.59324312, (19:25:15.593243004 2015:02:24)]
    Thread consumption suspected: 8 Try starting 1 threads
    starting LabVIEW Execution System 2 Thread 8 , capacity: 24 at [3507679515.73854351, (19:25:15.738543576 2015:02:24)]
    and 
    #Date: TUE, FEB 24, 2015 04:47:22 PM
    #OSName: VxWorks
    #OSVers: 6.3
    #OSBuild: Jun 6 2014, 09:14:16
    #AppName: /c/ni-rt/system/lvrt.out
    #Version: 14.0
    #AppKind: AppLib
    #AppModDate:
    InitExecSystem() call to GetCurrProcessNumProcessors() reports: 1 processors
    InitExecSystem() call to GetNumProcessors() reports: 1 processors
    InitExecSystem() will use: 1 processors
    starting LabVIEW Execution System 306708506 Thread 0 , capacity: 1 at [3507670087.84041262, (16:48:07.840412710 2015:02:24)]
    starting LabVIEW Execution System 306708507 Thread 0 , capacity: 1 at [3507670092.45153570, (16:48:12.451535843 2015:02:24)]
    starting LabVIEW Execution System 2 Thread 0 , capacity: 24 at [3507670103.11840487, (16:48:23.118404925 2015:02:24)]
    starting LabVIEW Execution System 2 Thread 1 , capacity: 24 at [3507670103.11840487, (16:48:23.118404925 2015:02:24)]
    starting LabVIEW Execution System 2 Thread 2 , capacity: 24 at [3507670103.11840487, (16:48:23.118404925 2015:02:24)]
    starting LabVIEW Execution System 2 Thread 3 , capacity: 24 at [3507670103.11840487, (16:48:23.118404925 2015:02:24)]
    VI_BROKEN (0): [VI "NC serial comms protocol.lvlibet Lower Temperature Limit.vi" (0x04667310)]
    VirtualInstrument:etOrClearBadVILibrary - now VI is bad on [VI "NC serial comms protocol.lvlibet Lower Temperature Limit.vi" (0x04667310)]
    this->flags=33563136, compilerError=6
    VI_BROKEN (0): [VI "Heater Control HAL.lvclass:Write Heater Control Active.vi" (0x058c4e98)]
    VirtualInstrument:etOrClearBadVILibrary - now VI is bad on [VI "Heater Control HAL.lvclass:Write Heater Control Active.vi" (0x058c4e98)]
    this->flags=50340352, compilerError=6
    VI_BROKEN (0): [VI "NI_LVConfig.lvlibave Config File.vi" (0x047b7e90)]
    VirtualInstrument:etOrClearBadVILibrary - now VI is bad on [VI "NI_LVConfig.lvlibave Config File.vi" (0x047b7e90)]
    this->flags=33563136, compilerError=6
    and so on.
    This is using a cRIO 9074 running CompactRIO recommended software set  14.0.1 .
    These errors happen right at startup. Memory use is steady in interactive mode, about 20 MB contiguous memory is unallocated out of 128 MB. I have taken pains to prevent allocation and follow cRIO besta practices non concatenated strings array building in loops etc). CPU is 50-60% when running interactive mode.
    Really at my whit's end here, I have tried the various combination of enabling / disabling debugging in the RTEXE, disconnecting typedefs etc. I have not noticed a pattern. 
    Regards,
    MarkCG

    Hello MarkCG,
    What minor changes did you make to the serial communication code? Posting the VI or a screenshot of the VI with the modifications which caused the RTEXE to stop functioning could be useful to troubleshoot the issue. 
    Regards,
    J_Bou

  • -1073807339 VISA Modbus Receive Error

    Hello ,
    I have been running this labVIEW program since the last 4 months. However, today as I run the same VI with same configurations and set up of PC, I am getting this error, see attachment.
     its a sub VI called Utility MODBUS RTU Receive Message.vi
    its strange that the error has cropped up from no-where. The entire VI is used to read temperature from a Eurotherm 3504 Device.
    Please help!
    Best Regards,
    Poulomi Das.
    Institute for Microsystems Engineering.
    University of Freiburg.
    Freiburg, Germany.
    Attachments:
    error.jpg ‏284 KB

    Please check these if it helps
    http://digital.ni.com/public.nsf/allkb/874B379E24C0A0D686256FCF007A6EA0
    http://digital.ni.com/public.nsf/allkb/E6DFA2B8D7E99F9886256C14005E82F7
    Thanks
    uday,
    Please Mark the solution as accepted if your problem is solved and help author by clicking on kudoes
    Certified LabVIEW Associate Developer (CLAD) Using LV13

  • Visa Resource Name in cluster passed to Network Stream writer causes error 42.

    If I try and pass this "motor data" cluster with an embedded VISA resource name:
    to a Network Stream Writer in this manner:
    Then I get this error from the "Write Single Element to Stream" VI
    If I change the motor data cluster TypDef so that a string control is used instead of the VISA reference, the error disappears and the data passes over the Network Stream without problem.
    Is this expected behavior? 
    I thought that the "data in" (type = "POLY"?) like the one found on the "Write Single Element to Stream" VI was supposed to accept pretty much anything...
    Solved!
    Go to Solution.

    Doug
    I would consider this a bug, as the memory location (more precisely the VISA refnum or session) of a VISA resource means nothing on a potentially remote system. Also I was under the impression that most streaming methods like binary file IO, but also the network streams would use the LabVIEW flattened format for data clusters and for that the VISA resource name would be the only logical choice instead of the underlaying VISA refnum, but I might be wrong in this specific case and the default behaviour for flattening VISA resources might always have been to the VISA refnum.
    Considering that the VISA control can resurect the VISA session from a VISA resource name if it is already opened, flattening to the VISA resource name instead would be more logical, but using a string control in the cluster type definition is a reasonable work around of course.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • I get a "vi is not executable" error when building an application.

    I have an ongoing project that has worked fine in the past when building an application. I have recently added some report generation toolkit vis(Excel) and get an error for some of the ni vis and some of my own that call lower level excel vis. The error is that he vi is not executable, however they run fine in the development environment. I do not get this error if I save all vi's into one llb with save with options command and then build. However, when I try to run the app, this error re-appears. Also, do I have to add the dynamically loaded vi's that are part of the toolkit in my build script? Could this be the cause of the problem? If so, what's the best way to find all of them? Any suggestions?

    You have hit in on the nail! You do need to add the dynamically loaded VIs when you are creating an executable from your VI. You need to add _wordsub.lib and _exclsub.lib as dynamically loaded VIs into your executable. Try this and let us know if you have any more problems with it.
    J.R. Allen

  • Error RW-50010 and RW-50004 - When try to install 11i on OEL5

    When i try to install oracle 11i on the OEL5, i have got the below error, can any one advice on this.......
    Below error in file :- 05061003.log
    Running Instantiation Drivers for /d01/Stage11i/startCD/Disk1/rapidwiz/template/adridb.drv
    instantiate file:
    source : /d01/Stage11i/startCD/Disk1/rapidwiz/template/adrun9i.sh
    dest : /d01/oracle/visdb/9.2.0/temp/VIS_oracleapp1/adrun9i.sh
    backup : /d01/oracle/visdb/9.2.0/temp/VIS_oracleapp1/adrun9i.sh to /d01/oracle/visdb/9.2.0/appsutil/out/VIS_oracleapp1/templbac/adrun9i.sh
    setting permissions: 755
    setting ownership: oracle:oinstall
    instantiate file:
    source : /d01/Stage11i/startCD/Disk1/rapidwiz/template/adrundb.sh
    dest : /d01/oracle/visdb/9.2.0/temp/VIS_oracleapp1/adrundb.sh
    backup : /d01/oracle/visdb/9.2.0/temp/VIS_oracleapp1/adrundb.sh to /d01/oracle/visdb/9.2.0/appsutil/out/VIS_oracleapp1/templbac/adrundb.sh
    setting permissions: 755
    setting ownership: oracle:oinstall
    Step 0 of 5
    Command: /d01/oracle/visdb/9.2.0/temp/VIS_oracleapp1/adrun9i.sh
    Step 1 of 5: Doing UNIX preprocessing
    Processing Step 1 of 5
    Executing: /d01/oracle/visdb/9.2.0/temp/VIS_oracleapp1/adrun9i.sh APPS APPS
    STARTED INSTALL PHASE : 9i RDBMS : Fri May 6 10:04:06 BST 2011
    runProcess_5
    Statusstring Executing Command: InstantiateFile -d addbtmpl.drv
    Cannot execute configure of environment for database ORACLE_HOME
    RW-50010: Error: - script has returned an error: 1
    RW-50004: Error code received when running external process. Check log file for details.
    Running Database Install Driver for VIS instance
    This error I got it in the file :- dbInstancecfg.log
    instantiate file:
    source : /d01/oracle/visdb/9.2.0/appsutil/template/adcctclean.sql
    dest : /d01/oracle/visdb/9.2.0/appsutil/install/VIS_oracleapp1/adcctclean.sql
    backup : /d01/oracle/visdb/9.2.0/appsutil/install/VIS_oracleapp1/adcctclean.sql to /d01/oracle/visdb/9.2.0/appsutil/out/VIS_oracleapp1/05061004/adcctclean.sql
    setting permissions: 600
    Executing script in InstantiateFile:
    /d01/oracle/visdb/9.2.0/Apache/perl/bin/perl -I /d01/oracle/visdb/9.2.0/Apache/perl/lib/5.00503:/d01/oracle/visdb/9.2.0/Apache/perl/lib/site_perl/5.005:/d01/oracle/visd
    b/9.2.0/appsutil/perl /d01/oracle/visdb/9.2.0/appsutil/scripts/VIS_oracleapp1/adchknls.pl
    script returned:
    Validating information needed for NLS........
    DATABASE version : db920
    No NLS specific checks required
    ERRORCODE = 0 ERRORCODE_END
    .end std out.
    .end err out.
    Executing script in InstantiateFile:
    /d01/oracle/visdb/9.2.0/appsutil/install/VIS_oracleapp1/afmkinit.sh
    script returned:
    afmkinit.sh started at Fri May 6 10:04:17 BST 2011
    The environment settings are as follows ...
    ORACLE_HOME : /d01/oracle/visdb/9.2.0
    ORACLE_SID : VIS
    TWO_TASK :
    PATH : /d01/oracle/visdb/9.2.0/Apache/perl/bin:/d01/oracle/visdb/9.2.0/bin:/usr/bin:/usr/sbin:/d01/oracle/visdb/9.2.0/jre/1.4.2/bin:/usr/ccs/bin:/bin:/usr
    /bin/X11:/usr/local/bin:/usr/bin:/usr/bin:/d01/Stage11i/startCD/Disk1/rapidwiz/unzip/Linux:/usr/bin:/usr/local/bin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X
    11R6/bin:/home/oracle/bin
    LD_LIBRARY_PATH : /d01/oracle/visdb/9.2.0/lib:/usr/X11R6/lib:/usr/openwin/lib:/d01/oracle/visdb/9.2.0/ctx/lib
    afmkinit.sh exiting with status 127
    .end std out.
    cp: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
    touch: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
    .end err out.
    Skipping INSTE8_PRF
    Skipping INSTE8_APPLY
    [AutoConfig Error Report]
    The following report lists errors AutoConfig encountered during each
    phase of its execution. Errors are grouped by directory and phase.
    The report format is:
    <filename> <phase> <return code where appropriate>
    [SETUP PHASE]
    AutoConfig could not successfully execute the following scripts:
    Directory: /d01/oracle/visdb/9.2.0/appsutil/install/VIS_oracleapp1
    afmkinit.sh INSTE8_SETUP 127
    AutoConfig is exiting with status 1
    Edited by: user9220213 on 06-May-2011 02:26

    HI,
    Please check below note:-
    Installation of 11.5.10.2 On OEL Fails [ID 747424.1]
    Thanks,
    JD

  • Encounter error when installing EBS R12.0.4.6 on OEL5.2

    Hi,
    I met a problem when I installed EBS R12.0.4.6 on Oracle Enterprise Linux 5.2.
    The installation was interrupted in the step 2 of 5. It showed RW-50004 error. Then when I clicked retry button, the installation continued until the post-instll checks. Only the Enviroment File and DBC File passed the check.
    Following is the error logged in the log file:
    ========================================================================================
    RC-50004: Fatal: Error occurred inApplyDatabase:
    Control file creation failed
    Cannot execute configure of database usingRapidClone
    RW-50010: Error: - script has returned anerror:
    1
    RW-50004: Error code received when runningexternal process.
    riwTDBup.sh exiting with status 2
    RW-50011: Error: - Apps ORACLE_HOME connection test has returned anerror:
    2Configuration Upload
    uploading config file at/d01/oracle/VIS/db/tech_st/10.2.0/appsutil/conf_VIS.txtAppsConfig : 'config.txt' uploading...
    ADX Database Utility
    getConnectionUsingAppsJDBCConnector()-->
    APPS_JDBC_URL='null'
    Trying to get connection using SID based connect descriptor
    getConnection() -->
    sDbHost
    : dbserv
    sDbDomain
    : company.com
    sDbPort
    : 1522
    sDbSid
    : VIS
    sDbUser
    : APPS
    Trying to connect using SID...
    getConnectionUsingSID() -->
    JDBC URL: jdbcracle:thindbserv.company.com:1522:VIS
    Exception occurred: java.sql.SQLException: Io exception: Got minus onefrom a read call
    Trying to connect using SID as ServiceName
    getConnectionUsingServiceName() -->
    JDBC URL:jdbcracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=dbserv.company.com)(PORT=1522))(CONNECT_DATA=(SERVICE_NAME=VIS)))
    java.lang.NoSuchFieldError: TDU
    AutoConfig completed with errors.
    runProcess_5
    Statusstring executing Service StartupScript on Apps Node
    Executing command:/d01/oracle/VIS/inst/apps/VIS_dbserv/admin/scripts/adstrtal.sh APPS/APPS
    You are running adstrtal.sh version120.13.12000000.3
    adstrtal.sh: Database connection could notbe established. Either the database is down or the APPS credentials suppliedare wrong.
    USAGE:
    adstrtal.sh<appsusername/appspassword>
    adstrtal.sh: exiting with status 1
    Cannot execute Service Startup Script onApps Node
    ========================================================================================
    Have you met this problem before? Do you know how to solve this problem? Please kindly give me some suggestions on it.
    Thank you very much.
    Best Regards，
    Vincent Yang

    Hi hsawwan,
    In adcrdb_VIS.log, I found the following errors. Could you please give me some suggestion? Thanks a lot.
    ==========================================================================
    Connected to an idle instance.
    ORACLE instance shut down.
    Connected to an idle instance.
    ORACLE instance started.
    Total System Global Area 1073741824 bytes
    Fixed Size 1265844 bytes
    Variable Size 432017228 bytes
    Database Buffers 629145600 bytes
    Redo Buffers 11313152 bytes
    Control file created.
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/d01/oracle/VIS/db/apps_st/data/sys1.dbf'
    alter tablespace TEMP1 add tempfile '/d01/oracle/VIS/db/apps_st/data/temp1_01.dbf' REUSE
    ERROR at line 1:
    ORA-01109: database not open
    alter tablespace TEMP2 add tempfile '/d01/oracle/VIS/db/apps_st/data/temp2_01.dbf' REUSE
    ERROR at line 1:
    ORA-01109: database not open
    ALTER DATABASE RENAME GLOBAL_NAME TO "VIS.company.com"
    ERROR at line 1:
    ORA-01109: database not open
    ORA-01109: database not open
    ==========================================================================
    Best regards,
    Vincent

  • "Error in the alert log file " - please help

    Hi ALL,
    I am getting following errors in the alert log frequently.
    My database version is:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
    PL/SQL Release 10.2.0.1.0 - Production
    CORE 10.2.0.1.0 Production
    TNS for IBM/AIX RISC System/6000: Version 10.2.0.1.0 - Productio
    NLSRTL Version 10.2.0.1.0 - Production
    Thu Aug 30 16:58:19 2007
    Memory Notification: Library Cache Object loaded into SGA
    Heap size 2172K exceeds notification threshold (2048K)
    KGL object name :select object_name from all_objects where object_name='TOAD_PROFILER' and object_type='PACKAGE'
    Thu Aug 30 17:09:36 2007
    ************************************************************************************

    Additionally you can visit here:
    Alert Error from trc files--Heap size 5236K exceeds notification threshold
    geting error in alert log file
    Adith

  • Allow required outputs in VIs

    I have probed the water for this suggestion in this thread and man, it is cold out there!
    The suggestion is to allow programmers to specify that a VI output connection is "required".
    Currently, the only options are "recommended" and "optional".
    For instance, the "Error Cluster From Error Code.vi" has a "recommended" error cluster output (that is, BTW, the only output of that VI):
    Does it make sense? I guess it does. It's like being able to drive without a seat belt or while drunk (on this last topic, I should mention that the French are actually going to require that all cars be equipped with a breathalyzer. French like legislating about anything and everything... I am sure people will still find a way to go around this).
    My use case is not based on this example, which I through in as a joke. As discussed in the thread I linked to, it will help prevent potential wiring errors such as this one:
     which hides this: 
    I think I am getting the mean and standard deviation but in fact get the mean twice. A nightmare to debug...
    I also think that it would be good to have this for error clusters in DAQ VIs (if automatic error handling is turned off, or at least, in this latter case, allow requiring error clusters to be connected to avoid catastrophic failures).
    Now you may ask, why is "recommended" not good enough?
    Answer 1: it does not break the VI calling that subVI and therefore, unless I turn on Warnings in the Error List and sift through all those I don't care about, it is difficult to find. Note that I am not asking anything from the existing VIs. I just want to be able to require this for MY VIs, so that *I* can protect myself from my own sloppiness.
    Answer 2: Breaking the VI forces you to think about the data flow. If for instance I require that some flag output is checked in the next processing step (handled by a downstream VI), it is because my experience is that this is pretty clever thing to do if you don't want to waste your time.
    Answer 3: Well, then why are there "Required" inputs? Would not "Recommended" be sufficient :-?
    As pointed out in the other thread, I am not the first one to suggest this. And there seems to be more vocal opponents to this concept than proponents (so I recommend checking that thread first before repeating the same arguments).

    Now that I looked back at it more carefully, it is not exactly the same as the other post had two (possibly confusing) suggestions in it. But admittedly, that very suggestion was there without much illustration and justification. In particular it did not link to the thread I am referring to in the first post. I'd favor keeping it separate (I linked back here from the thread Aristos Queue mentioned).
    @jmcarmody: I am afraid writing a quick drop function is beyond my ability (time wise mostly, but potentially as well due to my limited ability). But that's an interesting suggestion.

  • Modbus 6101 error

    Looking for advice/help with an issue.  I wrote an applicaton (LV2011) and built it with application builder for a customer. This project is out of the country and was working when I left ( around 2 hour test while I was there).  They are saying that now they are getting a 6101 time out error message after an hour or two of running and they have to close and then re-open the application to re-establish communication.  I am using the modbus library to communicate with 3 station addresses (plc and 2 vfd's).  Everything so far to me is pointing to noise distortion probably happening at the USB to serial converter.  I actually have a USB to RS232 converter then RS232 to RS485 converter attached to a USB port on the project.  The run is very short (less than 20 feet) and I did not use termination resistors at the beginning or end.  I am not to good with networking and am at a loss for what is happening.  I have read up on USB which seems to use 5V levels for communications which is much more suseptable to noise then the 12V levels of RS485.  At my facility when I connect a USB to RS232 converter and do not attach anything to the serial side I get a Modbus error not a general 6101 timeout error.  Now this could be because I am not intializing properly to begin with and they are but not sure and will run some more test with equipment hooked up to get past the initializing function and then simulate dropping the communication ( I think I remember that is also a specific modbus error not general 6101 error).  If that is the case where they are actual modbus visa read/write errors and not a general 6101 error then to me it is sounding like an error at the protocol level (i.e. RS485 or USB) and not at the application protocol level (i.e. modbus).  Excuse me if that terminology is off (not really good with networking and only know enough to be dangerous).  Anyway I am not sure where to go from here so any advice where somebody has seen an issue where it is working for over an hour and then loses communication would be extremely helpful.  Thanks in advance 

    Thanks for your reply.  I actually read your threads previously when looking up my issue.  I am trying to get more information from my customer now.  Of course when it failed my customer was not there and the maintenance guy just restarted Windows and the application to get it back up an running and does not remember what was on the screen at the time.  There is also a language barrier I am fighting through but after reading your old posts and some others I wanted to list a few things to see what your thoughts are.  
    -My customer mentioned that the incorrect serial communication port was selected for the VISA resource.  I only give my customer this option when the program starts up and then they do not have access to change it later and is required to restart the application to change it.  This could have been a result of the maintenance man trying to restart the application and selecting the wrong port but I did read your post where something similar happened with what you called MAX at the time (not sure what that is but figuring it may have been similar to the VISA resource).
    -I do not have any waits in my while loop that is doing the communications that is running in parallel with other code which seems to be an issue for others in the past?  Not sure why (although reading up on this seems to have to do with CPU usage) but the computer is meant to be dedicated to the application at hand so I am fine with as much of the CPU being delegated to the application as possible since they are not suppose to be using the computer for anything else.
    -With the change to only RS232->RS485 I am getting at least 2 or 3 days of working performance.  I am new to Labview and using Windows for industrial control but in my experience in the past with regular HMI's and PLC's if the code works for 2 days it will work indefinitely the same way until an outside influence affects it (i.e.. Generator starting up, lightening strike, ect).  For me this just seems like a very long time to work and then stop but again I am not really a fan nor am I used to using Windows.
    -Trying to trouble shoot this and using what I have found so far I am logically trying to think about what could be happening (not using the PC itself or Windows in the equation because it adds to many variables):
    First Item
    -USB converter in the equation was working for upwards of 2 hours and then dropped communication with a 6101 error and could not regain it no matter how many times the user clicked ok.  Basically went the specified timeout period and then throws the error again every time  once it fails.  Also when restarting the application after getting the error results in the program working but fails in significantly less time ( i.e.. 10 minutes).  
    First Conclusion
    -Trouble shooting tells me that the code I wrote is probably fine and noise eventually distorts the signal beyond repair.  This conclusion may be incorrect as I am used to dedicated hardware (i.e. plc's) that when it works once it works the same way every time.
    Second Item
    -Taking out the USB converter and use the on board serial port extended working time from 2 hours to 2 days.
    Second Conclusion
    Again leans toward noise being the culperate since the serial performed much better but still failed.  If it was simply a hardware problem with the USB converter then I would expect the system to run perfectly now and problem solved but since both methods eventually failed it now seems that the problem still exists but the Serial communication handles the problem better than the USB which higher voltage levels of serial communication probably allows for more signal distortion then lower voltage levels of USB.
    Anyway figured I would put down in words what I am thinking so that if my thought direction is not correct or I am not considering something that should be considered you may be able to explain to me other influences that need to be taken into account.  Thanks in advance for any help you can provide in corrected my thinking or advice on things to try.  For now on the next failure I plan on getting the time period between start and failure, checking what is required to get communications back (i.e. simply clicking ok on the error or restarting the application), possibly having them install the terminating resistor (120 ohm) at the end point to see how this affects the system.

Maybe you are looking for