Error 6 @ GPIB Write

Hello!
I'm currently working on a flash photolysis instrument using labview. Recently I have upgraded the computer and now have error 6 occuring randomly throughout the program. I've tracked the errors down to the GPIBwrite command which happens to be used throughout the program. After doing some reading and asking a few questions, I'm pretty sure its due to race conditions but have been unable to fix the problem (Probably due to me being a novice with Labview). Just wondering if any pros out there could lend some assistance, I've attached a jpeg of the problem area!
Thanks!
Attachments:
Helpme.jpg ‏63 KB

Updated my NI-488 driver and I've narrowed down this error a little more, but it is beyond my understanding. If I probe the Write error in, and Write error out the program will run fine for an indefinate amount of time(Pic1) but as soon as I remove the probes I'll be lucky to get 30 repetitions without Error6 coming back into my life(pic2). Really don't know what to make of this...
Attachments:
Error_1.jpg ‏202 KB
Error_2.jpg ‏193 KB

Similar Messages

GPIB write error code 6, how to do proper wait in GPIB comm

Hi!
I use a Keithley MUX and a DVM to measure different values in my system, including 4 wire resistance. My project runs for several hours without any problem, but last night I have got an error after approx. 8 hours runtime. My error out in the main vi shows the following error:
GPIB Write in A_4Wire_resMUX_2!1,2!3,2!5_new.vi Error code 6.
I have attached this subvi, as you can see, I have put a while loop in the subvi, to give enough time for the 4Wire measurement to be done. But of course maybe another GPIB write function crashes in the subvi, not the one after the while loop.
I have 2 questions:
1. what is the best way to do error handling in GPIB comm., so I could see on my final error out what element caused the problem in this certain subvi?
2. Can someone show me what I could do better in this subvi, to avoid possible GPIB errors?
Its just guessing, but I think the error comes from that I may not give enough time to the GPIB device to perform an action, so the next GPIB write crashes?
plus info: WindowsXP, LabView 2010 Full version
Thanks very much for advice and help!
Solved!
Go to Solution.
Attachments:
A_4Wire_resMUX_2!1,2!3,2!5_new.vi ‏35 KB

2001 driver
7001 driver
Now that you have a modern version of LabVIEW why are you not taking advantage of the instrument driver network? VISA is wonderful and the raw 488.2 primitives should be considered "obsolete".
Since you did not use the specific instrument driver vi's we can't tell which write to what device generates the error you are seeing.
So to specifically answer Q1. Use the Driver's found on the instrument driver network- they are tested and structured in ways that assist in debugging your application and take advantage of powerful features in VISA..
And 2) (see #1) and change the stacked sequence into a state machine
Jeff

PNA Guided Calibration: GPIB write error in for loop

Hi,
I have a LabVIEW program that creates a Guided Power Calibration on a PNA.
After initializing everything properly, I have a for loop that loops through all the manual steps that the user must go through (ex: Connect Channel A of Power meter to Port 1" "Connect male Short to port 1" etc).
The problem is, the program displays an error at the first command: sens:corr:coll:guid:acq STAN1
I says there is an error with the GPIB Write function.
Here are the commands I send:
SYSTRES
DISPlay:WINDow2TATE ON
CALCulate2ARameterEFine:EXT 'MyMeas',S21
DISPlay:WINDow2:TRACe1:FEED 'MyMeas'
CALC1AREL 'CH1_S11_1'
SENS:FREQTAR 2e9
SENS:FREQTOP 4e9
SENSWEOINTS 3
SENS:CORR:COLL:GUID:CONNORT1 'APC 2.4 male'
SENS:CORR:COLL:GUID:CONNORT2 'APC 2.4 male'
SENS:CORR:COLL:GUID:CKITORT1 '85056D'
SENS:CORR:COLL:GUID:CKITORT2 '85056D'
SENSe:CORRection:COLLect:GUIDedSENsor1 ON
SYSTem:COMMunicateSENsor gpib, "13"
SENSe:CORRection:COLLect:GUIDedSENsor1OWer:LEVel -20
sens:corr:coll:guid:init
sens:corr:coll:guid:steps?
//for loop from 1 to total_number_of_steps
sens:corr:coll:guid:desc? <step#>
sens:corr:coll:guid:acq STAN<step#>
The program quits right at the first step, when I send "sens:corr:coll:guid:acq STAN1", although the command is executed.
Also, the VBScript with the same commands works fine.
Can anybody help me? I've been stuck for a while now.
I attached the block diagram of the for loop.
Thanks in advance,
Nicolas
Attachments:
Guided cal for loop.vi ‏27 KB

Sending SENS:corr:coll:guid:acq STAN1 \n gives me a different error: -101 "Invalid Character".
From my different attempts at figuring this out, I thought the problem would come from LabVIEW, since the vbscript with the same commands works on the PNA.
I also modified the for loop because I thought each iteration should be linked to the previous one with the error wire (see attached).
I still have the same issue, only the first iteration is executed, then the program quits.
Attachments:
Guided cal for loop.vi ‏28 KB

Error 6 in GPIB Write

Hi
I have a LabVIEW code acting as a driver for an EG&G 5210 lock-in amplifier. Essentially I am using the GPIB write vi to send a string to the amplifier.
I have been trying to de-bug my code for a while.
The problem is, I have split the code into each constituent control and each separate part (e.g. changing phase or filter type etc.) works absolutely fine on its own. Also, when I combine several of these into one string it also works fine, apart from the addition of the very last part.
At this point I get error 6 "LabVIEW: Generic file I/O error. NI-488: I/O operation aborted."
I cannot then check any of the others parts work after this point since I only get the same error, even just testing one constiuent part (which had been working well beforehand)
I am using Labview 2011 with an NI GPIB-USB-HS with the previously mentioned EG&G 5210 amplifier.
Any help is greatly appreciated.
Please find attached my LabVIEW if required.
Jordan B
Attachments:
test 3.2.vi ‏28 KB

My guess is that when you are stringing the commands together, you aren't waiting long enough for at least one command to complete. I can't see the VI because of the ancient version of LV that I have at work, but if the instrument is SCPI compliant, consider appending ;*OPC? to each command that isn't already a query. This will turn that command into a query, so you execute a read (of a couple of bytes) and it will wait until the instrument has completed the command.
Read the instrument manual to make sure that the commands you are going to modify in this fashion are compatible with the *OPC? command.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Keithley 6517B GPIB Write Error 7

Hello,
I have a Keithley 6517B running and communicating with PC through GPIB. The program was initially running fine, and giving the current-noise signal against applied voltage (as programmed). But now when I run the program , it is giving an error that arises at the 6517 Reset/Preset.vi -
Error 7 occurred at GPIB Write in Keithley 6517A Reset / Preset.vi
How do I get rid of this error. I don't understand how suddenly an error arised when I changed nothing in the program or settings of the keithley. The keithley is configured at GPIB address 27.
I am attaching the main program and the sub.VI llb file .
Now when I run the main program, the graph does not show any current or noise signal, but it shows a straight line plotted along '0' along the x-axis (that is, against time or voltage)
Please help.
Best Regards,
Poulomi Das.
Institute for Microsystems Engineering.
University of Freiburg.
Freiburg, Germany.
Attachments:
VI Measurements_v4.vi ‏45 KB
kei6517v6.llb ‏1213 KB

Hello Mike,
I was on leave hence the late reply. I have attached the entire LV main vi with the sub VIs llb file to the very first message on this post. I have attached them again to this message.Do you mean something else?
Best Regards,
Poulomi Das.
Institute for Microsystems Engineering.
University of Freiburg.
Freiburg, Germany.
Attachments:
VI Measurements_v4.vi ‏45 KB
kei6517v6.llb ‏1213 KB

Labview error GPIB controller not adressed correctly

I get this Labview error: GPIB controller not adressed correctly (LV5.1, win NT4) when i try to send data to a HP4275A LCR meter. How ever it works on an older system running with LabView 5.0 (also NT)!!!
How can I get rid of this problem????

Hi Diego, thanks for the hints!
I tried to configure (GPIB) everything standard.
when I try a 488 command initialze, I get the controller conflict, when i don't do this I get atime out problem either by 488 write-command or by 488.2 send-command.
the differences between the systems where it works and where not are:
working: Win 95, LV 5.0, GPIB-card/TNT (plug & play)
not-working: WinNT, LV 5.1, GPIB-card/PCI
i tried to set baord config to the same parameters...
on the faulti system however I see the instrument with the MAX and I can send commands, without problems !!!!
Also the driver you posted does not work (but the NI-communicate program ;-)
i have no clue what else to do!
btw. how do I copy the spy output when running the program? I may provide
this to find errors.
Since MAX indicates the board is all right I guess it is not necessary to reinstall the boarddrivers?!

GPIB Write to multiple address

How do you write commands to multiple instruments? I get Error 6-GPIB
Controller not in charge when I use GPIB Write consecutively in block
diagram. Is there an easy way?
Attachments:
Multiple IO.llb ‏25 KB

Hi Rig
see attached llb
Its quick and 'dirty' it assumes you already know instrument addresess's!
Note use of sequence -this can be improved by either state machine or
simply by connecting vi in series using error connection as link.
No error detection coding has been added. This could cause problem with regard to time out etc.
Basically it should give you inspiration.
xseadog
Attachments:
Basicinstr.llb ‏204 KB

Gpib write or read sometimes hogs cpu

I have written a simple vi to communicate and
control a Stanford Research SR640 programmable filter. It does a
series of gpib writes and reads to get and set various controls on the
instrument, and it works very well. The problem comes when I try to
call it from a more complex vi that controls the entire experiment.
Once the sr640 vi is linked into the big vi, it takes 10-20 seconds for
the sr640 vi to return and it hogs the cpu, making even the mouse
unresponsive, Windows task manager stops updating, etc. This happens
even when running the simple sr640 vi directly from its front panel
with no other vi's executing. In "lightbulb" mode, I can see that
occassionally, the gpib write or read icons (from traditional gpib
pallette) take a long time to return, and the cpu goes to 100%.
If
I remove the complex calling vi from memory, the problem goes away, ie
the sr640 vi runs fine. If I load the big vi back into memory, I
reproducibly get the bad behavior when running the sr640 vi. Note that the big vi does not need to be running to cause trouble, only be loaded in memory. If I
delete the sr640 vi from the big vi, i.e. it is no longer called from
the big vi, the sr640 vi again runs fine.
Any idea what might be happening and how to go about debugging this?
Thanks,
Bob Shelby

Thanks for the reply.
Attached is the SR640 vi and a calling vi that works just fine.
Bob
Attachments:
srs_filter_setparms.vi ‏42 KB
test_sr640.vi ‏17 KB

Strange error: gpib error when using DAQmx

Hello
I try to out put a single puls using a counter on a PCI-6602 Board with the attached LabVIEW code.
Strangely I get the following error message:
"Error 3 occurred at an unidentified location
Possible reason(s):
LabVIEW: Internal error. Wrong memory zone accessed.
=========================
NI-488: GPIB Controller not addressed correctly."
Why do I get an GPIB-Error, although I don't even use a GPIB-Card?
Attachments:
ShortTrigger3.vi ‏23 KB
ErrorMessage.GIF ‏9 KB

Hello!
The problem is coming from the simple error handler.
The Simple Error Handler cannot decide if plots error + warnings, or only errors.
You cannot put your enumerator to the simple error handler, it works only with the general error handler.
In your program you are giving to the simple error handler a number 3 as error code. The VI convert this error number 3 with the error GPIB you received.
You should so replace the Simple Error Handler.vi with the General Error Handler.vi
Best regards
Ken

What is this error fatal: Write failed: Broken pipe in log of N7K

<186>: 2015 Mar 24 08:29:27 HKT: %DAEMON-2-SYSTEM_MSG: fatal: Write failed: Broken pipe .Client is 75.121.220.251,length of packet causing error 84 84 - sshd[684]
what is this error fatal: Write failed: Broken pipe in log of N7K
i find many brute force guessing login,
what can we do next?
[7m--More--[27m
iled for user root#02# from 222.186.30.115 - sshd[23714]
[7m--More--[27m
2015 Mar 24 07:17:25 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02##02# from 222.186.30.115 - sshd[23714]
[7m--More--[27m
2015 Mar 24 07:17:28 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root from 222.186.30.115 - sshd[23715]
[7m--More--[27m
2015 Mar 24 07:17:28 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02# from 222.186.30.115 - sshd[23715]
[7m--More--[27m
2015 Mar 24 07:17:28 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02##02# from 222.186.30.115 - sshd[23715]
[7m--More--[27m
2015 Mar 24 07:17:31 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root from 222.186.30.115 - sshd[23717]
[7m--More--[27m
2015 Mar 24 07:17:31 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02# from 222.186.30.115 - sshd[23717]
[7m--More--[27m
2015 Mar 24 07:17:31 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02##02# from 222.186.30.115 - sshd[23717]
[7m--More--[27m
2015 Mar 24 07:17:33 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root from 222.186.30.115 - sshd[23718]
[7m--More--[27m
2015 Mar 24 07:17:33 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02# from 222.186.30.115 - sshd[23718]
[7m--More--[27m
2015 Mar 24 07:17:34 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02##02# from 222.186.30.115 - sshd[23718]
[7m--More--[27m
2015 Mar 24 07:17:36 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root from 222.186.30.115 - sshd[23719]
[7m--More--[27m
2015 Mar 24 07:17:36 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa
[7m--More--[27m
iled for user root#02# from 222.186.30.115 - sshd[23719]
[7m--More--[27m
2015 Mar 24 07:17:36 xxxx %AUTHPRIV-3-SYSTEM_MSG: pam_aaa:Authentication fa

Restrict your vty line logins with an access-list to prevent Internet origin login attempts.

The "alsa audio output error: cannot write: Broken pipe" problem

[Solved]
(No place for this word in the Subject field, so I put it here.)
Hi Arch community!
I noticed I have this problem and not sure when in started. Several months ago I bought and installed new videocard "GeForce GT 630". Right after installation I lost sound in the system. Having internal sound card (in mainboard) and SB Audigy2 (PCI), I searched for solution and found I had to disable "snd_hda_intel" module to restore sound to work through PCI sound card. Did it.
echo "blacklist snd_hda_intel" >> /etc/modprobe.d/no-nvidia-sound.conf
After that sound was working as it should. And I noticed recently that during playing of any sound file the sound interrupts. If run VLC from CLI I get "alsa audio output error: cannot write: Broken pipe" message. And my system hasn't been upgraded since I don't know when. I still ran Firefox 26. So googled again and found it's a bug in a kernel or somewhere else.
==========================================
https://bugs.freedesktop.org/show_bug.cgi?id=69942 :
2013-10-01 01:39:40 UTC
I ran a system update last night, and this issue appears to have been corrected.
==========================================
And so I thought upgrade would fix my problem since mainstream bug is fixed. After upgrade sound interrupts again, maybe even more often.
Do you guys have this issue and does anyone have a solution?
Last edited by Mr. Alex (2014-06-26 18:55:59)

Not particularly wise to blacklist the module, since it probably is also used by the integrated sound card. With vid and pid you could just disable the nvidia card alone using parameter enable=0. Unless you do not mind having both disabled.
Where do I need to input "enable=0"? When I was searching for solution to make my Creative card work with new nVidia card I installed, the only way I found was blacklisting the module.
dmesg says:
[ 20.448086] nvidia 0000:02:00.0: irq 42 for MSI/MSI-X
[ 21.112331] NVRM: Your system is not currently configured to drive a VGA console
[ 21.112340] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[ 21.112345] NVRM: requires the use of a text-mode VGA console. Use of other console
[ 21.112349] NVRM: drivers including, but not limited to, vesafb, may result in
[ 21.112352] NVRM: corruption and stability problems, and is not supported.
Then:
lsmod | grep 'snd'
snd_ca0106 36242 0
snd_ac97_codec 114896 1 snd_ca0106
ac97_bus 1270 1 snd_ac97_codec
snd_rawmidi 20278 1 snd_ca0106
snd_seq_device 5244 1 snd_rawmidi
snd_pcm 83207 2 snd_ac97_codec,snd_ca0106
snd_timer 19294 1 snd_pcm
snd 60780 6 snd_ac97_codec,snd_timer,snd_pcm,snd_rawmidi,snd_seq_device,snd_ca0106
soundcore 5551 1 snd
I guess my card is "snd_ca0106". If yes,
# systool -v -m snd_ca0106
Module = "snd_ca0106"
Attributes:
coresize = "36242"
initsize = "0"
initstate = "live"
refcnt = "0"
taint = ""
uevent = <store method only>
Parameters:
enable = "Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y"
id = "(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)"
index = "-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1"
subsystem = "0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0"
Sections:
.bss = "0xffffffffa0814780"
.data = "0xffffffffa0813300"
.exit.text = "0xffffffffa0811a1e"
.gnu.linkonce.this_module= "0xffffffffa0814500"
.init.text = "0xffffffffa0817000"
.note.gnu.build-id = "0xffffffffa0811a30"
.rodata = "0xffffffffa0811a80"
.rodata.str1.1 = "0xffffffffa08123dc"
.rodata.str1.8 = "0xffffffffa0812130"
.strtab = "0xffffffffa0818c10"
.symtab = "0xffffffffa0817020"
.text = "0xffffffffa080d000"
__mcount_loc = "0xffffffffa0812f98"
__param = "0xffffffffa0812f18"
__verbose = "0xffffffffa0814460"
Where would I look for "max_buffer_size" parameter?

Error on write to control file

Hi all,
We are using the database sever version Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
working with windows platform. I saw an error in Alert log as follows,
ORA-00221: error on write to control file
Instance terminated by CKPT, pid = 4300
Few mins later the database opened without error.
Please anyone suggest me the cause and Solution for this error
Regards,
Jai.

hi,
Error: ORA 221
Text: error on write to control file
Cause: An error occurred when writing to one or more of the control files.
Action: See accompanying messages.
can you please post further errors.
Specific to windows is there any firewalls enabled & antivirus?
Thanks

Getting firmware update error. disk write error message

i installed the lastest ipod shuffle update and when I try to restore ipod shuffle I get the error message "firmware update error. disk write error" have no idea what to do. ipod does not show up in itunes

ok, someone else with similiar problem, I just opened the box 5 days ago, installed iTunes (the June 2005 version) that came on CD with it, ran iTunes, downloaded some music, plugged in Shuffle, goto download, fails, no device found, can see it under XP ok, goto apple.com to find support FAQ, I then ran up Ipod Updater, thinking that since it was new, firmware must be recent (little did I know ) so I thought do the Restore straight off, it started, then failed with the "disk write error" and havent been able to talk with iPod Updater since, then tried installing iPodUpdater to another PC, no luck, then downloaded later versions of iTunes and uPdater, installed on a 3rd PC, same deal, unable to communicate to Shuffle, rang phone support, spoken to two different support people, finally they agree its faulty (something I figured out 4 days ago) and suggest I return it to Apple for replacement, and fill out a Service Request form, which opened a can of new worms, like there is no "Warranty Replacement" option, lots of questions like Credit Card details and nowhere to actually define that I have a "faulty" or "dead" or Shuffle to return and they obviously did not read the comments, that were requested, as they simply sent docking station in the mail, so now back to square one, trying to lodge a Service Request to "replace" a brand new, dead shuffle. Not having a nice iPod experience here !!, but Itunes is good, although expecting it will take a couple weeks all up before I get a working Shuffle to actually download to. Tried again phone support, to sort out this mess, waited in queue, then line goes dead. Oh Well ... I blame my daughter for this heartache, she insisted on having an iPod.

L'erreur 3 s'est produite à : GPIB Write

Bonjour,
Je suis actuellement en stage et je viens, comme indiqué dans le titre, de rencontrer cette erreur : L'erreur 3 s'est produite à : GPIB Write.
Cette erreur apparaît dans un sous VI de mon programme principal. J'ai fait tourner un grand nombre de fois le sous VI en question seul avant de l'incorporer à mon programme principal et je n'ai jamais rencontré cette erreur auparavant.
Elle n'apparaît que depuis que j'ai couplé ce sous VI à mon programme principal.
L'appareil que je pilote et qui pose problème est un multimètre HP 3458A. J'ai bien vérifié l'adresse que je lui associe elle est correcte. Si vous jetez un coup d'oeil aux pièces jointes, l'erreur se produit lors de la dernière Visa session write ou j'envoie la commande MEM FIFO.
Encore une fois l'erreur ne se produit que dans mon programme principal, je pense qu'il est question de rapidité d'accès à la mémoire de l'instrument mais je ne suis pas sûr et je n'ai aucune idée de solution possible étant novice.
Si je n'ai pas été clair ou assez précis je m'en excuse d'avance et je tacherais de l'être davantage si vous prenez le temps de m'aider!
Merci d'avance.
Benjamin.
Pièces jointes :
Sous_VI.vi ‏161 KB
VI_Principal.vi ‏536 KB

Merci à toi de prendre le temps de me répondre
Je pense avoir trouver la cause du problème, je travaillais sur réseau (grosse entreprise etc.) au final j'ai copié tous mes fichiers sur disque et bizarrement il n'y a plus de temps de chargement du programme tout se fait instantanément... Et l'erreur ne se produit plus. Sachant que le réseau rame depuis 3-4 jours est ce que le problème pourrait venir de là?
Sinon oui je me suis effectivement donné beaucoup de mal ^^ et je sais que mon programme est loin d'être optimal c'est sur quoi il me reste à travailler =D
Je te renvoie les deux VI au cas ou, les deux sont indépendants l'un de l'autre.
Pièces jointes :
TEST_RELAIS_TEMPERATURE_CYCLE.vi ‏536 KB
Sous_VI.vi ‏161 KB

Mode meaning in GPIB write

Hi, All,
I have a question when I wanna use GPIB write function. I am not clear about what those modes meaning like EOI, CR or LF in the help.
0
Send EOI with the last character of the string.
1
Append CR to the string and send EOI with CR.
2
Append LF to the string and send EOI with LF.
3
Append CR LF to the string and send EOI with LF.
4
Append CR to the string but do not send EOI.
5
Append LF to the string but do not send EOI.
6
Append CR LF to the string but do not send EOI.
7
Do not send EOI.
In fact, I wanna increase voltage supply by 5V every 5s. I wrote a program in the attached files. Pls help me to see if it is logical.
Thanks.
Solved!
Go to Solution.
Attachments:
3631A power supply.vi ‏6 KB

The mode has to do with how a GPIB write is terminated. The standard for quite a few years has been to assert the EOI (End or Identify) management line when the last data byte has been sent. The other modes are there to support old instruments before the current standard was adopted. Some of them required a CR (carriage return), LF (line feed), both, etc. Your instrument manual should explain what, if any additional termination is required. The current standard was adopted in 1987 so your instrument would have to older than you is my guess if you need those special modes.
Your VI should work okay with the addition of the wait and wiring up the N terminal of the for loop but is not the most elegant. First, instead of the GPIB primitives, you should use the VISA functions. Instead of wiring the iteration terminal, you can use a shift register and a add function with an increment. You can use a while loop and stop it when it reaches a final value. Instead of the concantanate string function, I prefer to use the Format Into String function.
If you keep this code, get rid of the second GPIB address string control. Thetimeout function of the GPIB write is not related to a trigger and you can leave it unwired and just use the default.
Attachments:
3631A power supply_mod.vi ‏10 KB

I put more wrong passcodes and then write "Iphone is disabled | Connect to iTunes". When i connect to iTunes, appear a error where write that I can't connect iPhone to iTunes because must to put a password on iPhone . HEEEEELP !

I put more wrong passcodes and then write "Iphone is disabled | Connect to iTunes". When i connect to iTunes, appear a error where write that I can't connect iPhone to iTunes because must to put a password on iPhone ( but I can't connect iPhone to iTunes because is blocked) HELP me PLEASE ! And give you more details if you want .
Sorry for my english but I am from Romania and I don't know very good .

Forgot an iPhone Passcode? How to reset the iPhone passcode
iPhone and iPod touch- Wrong passcode results in red disabled screen
Please get the iPhone iOS 4 user guide.

Error 6 @ GPIB Write

Similar Messages

Maybe you are looking for