Erreur -1073807343 dans visa open

pour ouvrir une application (sur un systeme branche en serie) j ai regulierement l erreur  -1073807343 dans visa open==> les informations concernant la position sont insuffisante
ou peripherique absent....alors que celui ci est present
merci

Hi Akim_10,
This part of the Forum is in English; please refer to this part of the Forum
to write in French.
Concerning your question:
When entering
the VISA resource name input for the VISA Open function or the VISA Serial
Config function, do not use the standard port names (COM1, COM2, LPT1, etc.).
Instead use the VISA resource name for these ports: COM1 is ASRL1::INSTR, etc.
For example:
Place a VISA Open
function on your block diagram and use the wiring tool to right-click on
the VISA resource name input.
Select Create » Control
from the right-click menu.
Go to the front panel
and right-click on the newly created control.
Select Allow Undefined
Names from the right-click menu (if it isn't already selected).
Enter the VISA Resource
Name for your port. The name should look something like
"ASRL1::INSTR". Note: This name can be found in the Measurement
& Automation Explorer (MAX) under Devices and Interfaces » Ports
(Serial & Parallel). For example, click on COM1 and you will see its
VISA Resource Name in the right-hand portion of the MAX window.
Benjamin R.
R&D Software Development Manager
http://www.fluigent.com/

Similar Messages

  • Erreur 1073676294 dans VISA READ

    Bonjour,
    comme l'indique le titre, j'ai une erreur (1073676294) dans mon VISA Read.
    Lorsque j'execute mon VI principal, mon sous VI contenant ce VISA apparaît.
    Comment faire pour qu'il n'apparaisse plus?
    Cdt
    Résolu !
    Accéder à la solution.
    Pièces jointes :
    Test Machine à états.vi ‏31 KB

    J'ai effectué les configurations indiquées, mais malgré ça, mon sous VI s'affiche toujours..
    Pièces jointes :
    Ecriture_T_Consigne.vi ‏29 KB
    Visa_écriture.vi ‏20 KB
    Cadencement Maître_Esclave_.vi ‏42 KB

  • Old visa open, error code 1073807343, using VISA with a GPIB device, and VISA resource names

    Hi everyone,
    I'm trying to get a SRS model SR720 LCR meter (manual on this page) working with LabView, connecting it to my PC with an Agilent 82357A GPIB/USB interface (manual on this page). I'm running MAX version 14.0, and NI-VISA version 14.0. I'm running LabView version 13.0f2, 32 bit.
    I followed the directions on this page, and I'm pretty confident I can communicate with my LCR meter, because I can go to NI MAX->GPIB0::17::INSTR under "devices and interfaces", then go to the VISA test panel, go to the I/O tab, and I can enter a few commands from the SR720 manual, like changing the frequency, and I see the light on the LCR meter change to what I just told it to do. Here is a picture, just to illustrate it:
    Also, if I do the *IDN? command, it returns "
    9: Write Operation (*IDN?)
    Return Count: 5 bytes
    10: Read Operation
    Return Count: 41 bytes
    StanfordResearchSystems,SR720,08087,1.03\n
     So, that's good too. I also made the alias of this device "MyLCRmeter", but that shouldn't matter for now.
    Now I'm trying to get it to work in a more usable way. The SR7xx drivers that LabView found for me came with a couple sample programs, one called "Getting Started.vi". I tried to just simply see if it worked, changing the "instrument descriptor" field to "GPIB0::17::INSTR", since that's the one that seemed to be the right device in MAX. Here is a picture of the front panel of "Getting Started.vi":
    Trying to run it like this gave me this error (code -1073807343):
    Old VISA Open in SR715/720 Initialize.vi->SR715/720 Getting Started.vi
    Doing a bit of searching on these forums, I found these few threads (1 2 3), which seem to tell me that, since this program was written, the way you open VISA has changed. In the 2nd of those links, one guy said:
    You just have to replace the Old VISA Open function with the VISA Open that is on the Instrument I/O>VISA>VISA Advanced palette. When you do that, the wire to the string that was used for the resource name will be broken. Delete the string and make the actual VISA Resource Name visible on the front panel. Wire the VISA Resource Name control to the connector pane where the string control was (upper left connection).
    So, I went into the sub-VI Initialize.vi, and did that. Here is a picture of what the front panel and block diagram of the sub-VI Initialize2.vi (I changed the name in case I screwed things up, but I'm pretty sure the new one is the one being called by Getting Started.vi) looked like before I changed anything (you can see the Old VISA Open):
    and here it is after replacing that with the regular VISA Open, deleting the instrument descriptor string and replacing it with a VISA resource, and connecting that to the VISA Open:
    However, as you can see in the image above, and it seems like someone else had this problem in the 2nd thread linked above, I don't see my device listed in the drop-down menu (even if I refresh), only "LPT1" (I don't even know what that is):
    No, I wasnt able to select the visa resource from the pull down menu. somehow it seems disabled or something.
     If I just enter the VISA resource name from MAX manually, GPIB0::17::INSTR, and save and try running that, I get the error(code -1073807346):
    VISA Open in SR715/720 Initialize2.vi->SR715/720 Getting Started.vi
    So I'm not sure where to go from there, or why it's not in the drop down menu to begin with. I'm sorry if I've missed something but I've searched about as far as I can go. If I had to guess, maybe one thing could be that in MAX, under Tools->NI-VISA->VISA Options->My System->Conflict manager, I have both Agilent VISA and NI VISA enabled; I know sometimes problems arise from conflicts between different software fighting over the same hardware. Is this okay, or do I need to change it?
    Thank you and please let me know if there is any other code/screenshots I could provide that could help!

    Hi, I did indeed enable NiVisaTulip.dll under MAX->Tools->NI-VISA->VISA Options->My system->Passports->List of passports. Sorry, I should have mentioned that explicitly.
    By install as primary, do you just mean as it is here, where it is selected as the "Preferred VISA"?
    Or somewhere else? I installed NI-VISA first I believe, and then the Agilent one, and during the installation of the Agilent one, I'm pretty sure I made it not the primary. Here's what I have in the Agilent (it's called Keysight now) Connection Expert software:
    I also have this under the "Keysight 488 options" tab:
    Should that be checked? I don't actually know the role of VISA vs 488 here...
    What could I try?
    Thank you!

  • Visa erreur -1073807343

    Bonjour
    J essai d interfacer un controleur de temperature LakeShore 331S avec labview en RS232
    J ai bien trouvé sur ce site le programme pour mon model mais quand j essai de les utiliser j ai l erreur suivante
    -1073807343
    Nœud de propriété (arg 1) dans VISA Configure Serial Port (Instr).vi->LSCI 331 Acq12.vi
    Es ce quelq un pourrait m eclairer sur cette erreur svp
    Je ne trouve pas a quoi correspond l erreur -1073807343
    Merci d avance

    […] il y'a un problème avec votre carte / contrôleur RS232 [..] Par exemple le port COM n’est pas valide. Vérifier dans le panneau de configuration > gestionnaire de périphériques > les ports COM
    Luc Desruelle | Voir mon profil | LabVIEW Code & blog
    Co-auteur livre LabVIEW : Programmation et applications
    CLA : Certified LabVIEW Architect / Certifié Architecte LabVIEW
    CLD : Certified LabVIEW Developer / Certifié Développeur LabVIEW

  • Bonjour, j'ai une erreur 1009 dans DPS APP Builder

    bonjour, j'ai une erreur #1009 dans Folio App Builder, lors de la création d'une application Ipad, au moment ou j'ai sélectionné les certificats Apple et que je veux passer à l'étape suivante. Quelq'un a-t-il une solution?

    You will likely get better program help in a program forum
    The Cloud forum is not about using individual programs
    The Cloud forum is about the Cloud as a delivery & install process
    If you will start at the Forums Index https://forums.adobe.com/welcome
    You will be able to select a forum for the specific Adobe product(s) you use
    Click the "down arrow" symbol on the right (where it says All communities) to open the drop down list and scroll

  • Visa Open and Close on every iteration of loop

    I have noticed that when you open the front panel of the Instrument I/O Assistant, the diagram starts with a visa session open, sets timeout property, writes, reads, parses data and ends with a visa session closed.  If I were to place this into a while loop the visa session would open and close on each iteration of the loop. 
    Is it common practice to open and close the visa session on each iteration?

    No you would not want to open and close that often. If you want to use the Instrument I/O assistant what I would do is configure it the way you want and then save it under another name so you can open the block diagram. Pull the VISA open and close outside of your loop.
    Using LabVIEW 2010SP1 and TestStand 4.5

  • When trying to work with Agilent 34401A multimeter (serial RS-232 connection), HP34401A Getting Started.vi gives always the message: "Error 1073807369 occurred at Old VISA Open ".

    Baud rate and parity are set correctly, RS-232 cable is also connected correctly. My QuickBasic program has no problems to read and write to the Multimeter. It is obviously a software problem: the same error is persistent if I disconnect RS-232 cable.
    I downloaded NI-VISA 2.6 for Windows 95/98/NT/ME/2000/XP frorm digital.ni.com and installed it. But it did not help.
    Thank you in advance
    Best regards
    Alexei Soloviev

    Hi Steve
    I have problems with the 34401A and serial communication. Do you remember
    where the error was in the code ?
    Thanks
    Klaus
    wrote in message
    news:[email protected]..
    > Alexei,
    > This may or may not help, I was tasked to do something similar
    > recently and found an error in their driver. The GPIB VISA worked
    > fine, but when I tried it on serial it played up. There was an errant
    > carriage return (or CR/LF I can't remember). GPIB liked one and Serial
    > liked the other. It always amuses me that we never have problems with
    > Quickbasic!.
    > If you want me to dig deeper give me a shout.
    >
    > Steve Watts
    >
    > On Thu, 24 Jan 2002 06:16:55 -0800 (PST), "Alexei V. Soloviev"
    > wrote:
    >
    > >When trying
    to work with Agilent 34401A multimeter (serial RS-232
    > >connection), HP34401A Getting Started.vi gives always the message:
    > >"Error 1073807369 occurred at Old VISA Open ".
    > >
    > >Baud rate and parity are set correctly, RS-232 cable is also connected
    > >correctly. My QuickBasic program has no problems to read and write to
    > >the Multimeter. It is obviously a software problem: the same error is
    > >persistent if I disconnect RS-232 cable.
    > > I downloaded NI-VISA 2.6 for Windows 95/98/NT/ME/2000/XP frorm
    > > digital.ni.com and installed it. But it did not help.
    > >Thank you in advance
    > >Best regards
    > >Alexei Soloviev
    >

  • Visa open problem

    Hi 
              I'm using  labview2009. I've connected 8593E spectrum analyzer using GPIB interface to my PC.The problem is the instrument address is not coming automatically in the VISA open function input when I connect the instrument to my PC. can anyone sort it out. I've installed Agilent IO libraries suit15.0 and NI device drivers.
    Regards
    RobinHood

    Hi,
     If you are using Agilent GPIB then i guess u need passport tulip. Steps to do it i will attached here the manual.I guess it should work. 
    Attachments:
    Steps_for _Installation_of Intru_Labview.pdf ‏712 KB

  • Apparition de nombre 12288 dans visa read

    Bonjour,
    Je suis actuellement en stage où je doit réaliser un programme labview qui doit acquérir des données de différent appareil dont un MaxiGauge de Pfeiffer vacuum. Sur ce MaxiGauge j'aquéri trois jauge en même temps le MaxiGauge est relier a mon ordinateur  grâce à un USB 232 de NI. Lorsque je lance l'aquisition le premier de mes visa read qui me donne une mesure m'indique relativement souvent le nombre 12288. Je n'arrive pas trouver ce que cela signifie.
    Merci d'avance pour toutes réponses.
    Cordialement,
    Altanahaz
    Pièces jointes :
    mgt.vi ‏29 KB

    Bonjour Altanahaz,
    D'après les recherches que j'ai pu faire le nombre 12288 correspondrais à la taille maximum du buffer de lecture en octet dans VISA Read ce qui pourrais expliquer l'apparition du nombre 12288 mais pas à chaque itération du programme. Initialise tu les buffer en début de programme ? Si non utilise la fonction Flush I/O buffer http://zone.ni.com/reference/fr-XX/help/371361J-0114/lvinstio/visa_flush_i_o_buffer/ qui pourrais peut être réspoudre ton problème.
    Cordialement
    Louis
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    Travaux Pratiques d'initiation à LabVIEW et à la mesure
    Du 2 au 23 octobre, partout en France

  • Labview/excel: erreur -2147352567 dans Set Cell Value.vi

    Bonjour à tous,
    Je suis face à un problème insoluble.
    Je n'arrive plus à écrire dans une cellule excel.
    J'ai développé mon programme sous labview 2009 et fait des tests sur deux pc différents.
    Sur un, l'écriture cellule fonctionne  sur l'autre j'ai toujours l'erreur -2147352567 dans Set Cell Value.vi.
    J'ai changé de pc et je suis passé de XP à Seven, installé labview 2009, mon programme bloque toujours sur le vi Set Cell Value.
    Comment puis je solutionner mon problème? recompiler le programme?
    Tous vos retours seront les bienvenus.
    Cdlt
    Solved!
    Go to Solution.
    Attachments:
    test-ecrire-excel.pdf ‏139 KB
    essai_ecrire_excel.vi ‏29 KB

    Bjr à tous,
    Le problème vient des modes de compatibilités d'excel entre 2003 et 2007-2010.
    Vous ne pouvez pas gérer des fichiers en .xls ou .xlsx sur la même application.
    Cela peu fonctionner un temps mais cela ne dure pas.
    La solution ensuite est de convertir tous vos fichiers en extension .xlsx et tout rentre dans l'ordre.
    Tout ceci est la joie d'excel et des logiciels à licence.
    A+ pour un autre sujet de discussion.

  • NI-VISA 5.1.2 exits/closes right after launching it on a Linux CentOS 6.2 PC, also crashes LabVIEW when trying to create VISA ref constant for VISA Open.

    After installing LaBVIEW 2011 and NI-VISA 5.1.2 on a CentOS 6.2 PC, I had noticed a problem with trying to use the VISA vi's in LabVIEW, basically it's not working for me, LabVIEW crashed when trying to create a control or constant for the VISA Open vi.  Tried to launch the VISA tools, they all start and then close abruptly.  NI I/O Trace only shows one line.
    I did read though many threads and decided to collect the NI system.log, which is attached. (system.log.gz).  I did notice a strange message in here about nivisaserver:
    /usr/bin/tail --lines=25 /var/log/messages:
    May 22 11:18:48 localhost abrtd: Package 'nivisaserver' isn't signed with proper key
    May 22 11:18:48 localhost abrtd: Corrupted or bad dump /var/spool/abrt/ccpp-2012-05-22-11:18:48-3258 (res:2), deleting
    Thanks!
    Solved!
    Go to Solution.
    Attachments:
    system.log.gz ‏621 KB

    MountainMan12 wrote:
    After installing LaBVIEW 2011 and NI-VISA 5.1.2 on a CentOS 6.2 PC, I had noticed a problem with trying to use the VISA vi's in LabVIEW, basically it's not working for me, LabVIEW crashed when trying to create a control or constant for the VISA Open vi.  Tried to launch the VISA tools, they all start and then close abruptly.  NI I/O Trace only shows one line.
    I did read though many threads and decided to collect the NI system.log, which is attached. (system.log.gz).  I did notice a strange message in here about nivisaserver:
    /usr/bin/tail --lines=25 /var/log/messages:
    May 22 11:18:48 localhost abrtd: Package 'nivisaserver' isn't signed with proper key
    May 22 11:18:48 localhost abrtd: Corrupted or bad dump /var/spool/abrt/ccpp-2012-05-22-11:18:48-3258 (res:2), deleting
    Hi MountainMan,
    Thanks for attaching the system report log -- I believe I have a solution for you :-) Let's look at a few of the lines:
    890: /proc/meminfo:
    891: MemTotal: 3894712 kB
    1726: /proc/iomem:
    1784: 100000000-12dffffff : System RAM
    1807: /bin/dmesg:
    1820: BIOS-provided physical RAM map: 2576: [nipal] More than 4GB of addressable memory detected.
    1838: BIOS-e820: 0000000100000000 - 000000012e000000 (usable)
    2576: [nipal] More than 4GB of addressable memory detected.
    2577: [nipal] This configuration is not supported. Check the release notes for more information.
    Starting at the bottom at lines 2576..2577, dmesg had more than just the NI-VISA server signing notification. At system boot, the NI kernel modules refused to load because they detected more than 4 GB of addressable memory. But, if you look towards the top at lines 890..891, meminfo says you have less than 4 GB of system memory, which makes it seem like the NI modules don't know what they're talking about. However, if you look at the report from iomem a little further down on lines 1726..1784, system RAM has been re-mapped above the 4 GB boundary. While your system doesn't have more than 4 GB of RAM, some of its memory has addresses above 4 GB, which the NI modules cannot use and so they refuse to load. How did that happen? Your system BIOS provided a physical RAM map with usable addresses above the threshold (line 1838).
    The fix here is simple -- you need to tell the kernel to reserve addresses above 4 GB [1] so that it won't remap the RAM to higher memory. Once all of the RAM has addresses below the 4 GB threshold, the modules should load and VISA/LabVIEW/et al should stop misbehaving.
    It seems to me that LabVIEW is not handling this situation very gracefully, and maybe you can work with Kira to file a bug report.
    [1] Re: Successful SUSE linux and DAQmx install; nilsdev and other utilities missing.
    http://forums.ni.com/t5/Multifunction-DAQ/Successful-SUSE-linux-and-DAQmx-install-nilsdev-and-other/...
    Joe Friedchicken
    NI VirtualBench Application Software
    Get with your fellow hardware users :: [ NI's VirtualBench User Group ]
    Get with your fellow OS users :: [ NI's Linux User Group ] [ NI's OS X User Group ]
    Get with your fellow developers :: [ NI's DAQmx Base User Group ] [ NI's DDK User Group ]
    Senior Software Engineer :: Multifunction Instruments Applications Group
    Software Engineer :: Measurements RLP Group (until Mar 2014)
    Applications Engineer :: High Speed Product Group (until Sep 2008)

  • LV5 VISA Open vs LV6 VISA Open

    Currently have TestStand feeding the VISA Resource Name (string) into a LV5 VISA IO Open. We have upgraded to 6i and would like to re-use our current VI's. How do I mimic this same interface using the LV6i VISA IO Open. Specifically, how do I convert the TestStand string into the VISA Resource Name, such that it is controlled thru TestStand.

    In my LV5 VIs I wrote for TestStand, I had string constants wired to the VISA Open and when I converted to LV6, it used a new function called Old VISA Open. However, I have no idea where to find this function on any of the pallettes. I've had to do a copy and paste for new VIs when I've wanted the same functionality.

  • NI I/O Trace VISA Open question

    Hello,
    I have a big application which has quite a few threads (timed while loops). One of the while loops is communicating on a specific COM port with a timed wait of 100 ms. This is the only loop which uses this specific COM port. When I look at NI I/O Trace, I see VISA Opens to this COM port every 2 ms. I have NI MAX closed. I tried changing my timed wait to 5000 ms but it had no effect.  I am trying to see if something is slowing down my application and would like to reduce these number of calls. Is NI MAX or something else trying to communicate via this COM port?
    Thanks

    In IO Trace, if you navigate Tools >> Options >> View Selection, you can select the ProcessID and ThreadID Column headers to see which process and thread the calls are being made from.
    Also, to verify the results of IO Trace, you could run a Portmon scan while the application is running.
    'Portmon for Windows v3.03'
    https://technet.microsoft.com/en-us/library/bb896644.aspx

  • Firefox v33 - Verified by Visa (opens in separate frame) is now blocked without an opportunity to bypass the 'untrustworthy connection'.

    With the latest version of Firefox (running on Windows Vista Business), the separate frame which is opened by 'Verified by Visa' after a purchase transaction, is now blocked saying that I am trying to connect to an untrustworty site. I guess this is because Firefox is now hypersensitive to mixed content. However there is no opportunity to used the 'continue' option.
    The easiest workaround is to use Chrome which doesn't have these problems.

    Among the alternatives not mentioned... Using a TiVo DVR, rather than the X1; a Roamio Plus or Pro would solve both the concern over the quality of the DVR, as well as providing the MoCA bridge capability the poster so desperately wanted the X1 DVR to provide. (Although the TiVo's support only MoCA 1.1.) Just get a third-party MoCA adapter for the distant location. Why the hang-up on having a device provided by Comcast? This seems especially ironic given the opinions expressed regarding payments over time to Comcast. If a MoCA 2.0 bridge was the requirement, they don't exist outside providers. So couldn't the poster have simply requested a replacement XB3 from the local office and configured it down to only providing MoCA bridging -- and perhaps as a wireless access point? Comcast would bill him the monthly rate for the extra device, but such is the state of MoCA 2.0. Much of the OP sounds like frustration over devices providing capabilities the poster *thinks* they should have.

  • L'opération n'a pas pu s'achever. (OSStatus erreur -54)DANS IPHOTO

    IMPOSSIBLE D'OUVRIR LES VIDEOS CONTENU DANS IPHOTO AVEC L'ERREUR L’opération n’a pas pu s’achever. (OSStatus erreur -54)
    MERCI D'AVANCE.

    j ai se soucis sur mon macbook depuis se matin 13 sept 2012   erreur 1100 impossible de chercher mises a jours apple store j'ai changer dns rien ni fait et bizarement sur mon imac aucun soucis pas de message d'erreur quelqu'un peut t'il m'aider suis en france NANTERRE (NSURLErrorDomain Erreur -1100)

Maybe you are looking for

  • Date and Time on Menu Bar

    Up until now the date and time has been displayed on the menu bar as... Tuesday, November 28, 2006 8:09 AM Now, for some reason, it's being displayed as... Tue 8:09 AM Here's what I've tried in trying to restore the format... 1) System Preferences >

  • Preview & TeXShop print PDF's incorrectly on HP printer

    Since upgrading to: Mountain Lion (10.8.3), an iMac and new HP printer, I cannot get either Mac's Preview or TeXShop to print PDF's correctly on my HP Laserjet 600 M601 printer (this by the way is a brandnew printer so I cannot compare with how it wa

  • Seeking advice on a heavy hash join

    We have to self-join a 190 million row table 160 times. On our production 9i database we give "RULE" hint and it finishes in about an hour using nested loop join, On our test 10g database, since "RULE" is not available any more. The optimiser chooses

  • I am unable to delete history - this started yesterday

    I have tried all options that I am aware of - checked your FAQ's and tutorials. I am unable to delete - system can't handle my FB traffic. what have I missed? up until yesterday, even after deleting by your options, I have had to manually delete. Ple

  • Checking  Whether Physical Standby is in Sync with the Primary

    I writing script to alert dba if primary and standby database are not in sync. I use article - How To Check Whether Physical Standby is in Sync with the Primary? ID 861595.1       It suggests comparing Last Sequence Generated on primary and Last Sequ