DAQmx wait failed 100ms

Similar Questions

• DaqMX wait the next sample causing slow down Clock.vi

  Hello

  I have a question about the proper use of DaqMX wait for next sample clock.

  I read channels analog voltage on a map or pcie-6259.

  I would like to read as soon as possible make your comments between each of these points of single data points.

  I wish I had an error generated if I miss a data point.

  From reading the forums, I've gathered that the best way to do it is using the Timed Single Point material.

  A simplified program that I use to test this is attached.

  If I remove the DaqMX wait for next sample Clock.vi, my program seems to work.

  I added a counter to check the total time is as expected.

  For example, the program seems to work at the speed appropriate for 120.

  However, without that vi, it seems that the program does not generate a warning if I missed a sample.

  So I thought that the next sample clock waiting vi could be used to determine if a single data point has been missed using the output "is late."

  However, when I add inside as shown in the joint, the program seems to slow down considerably.

  At high rates as 120000, I get the error:-209802

  14kHz is the approximate maximum rate before you start to make mistakes.

  My question is: is this the right way to check a missed sample? I don't understand why the wait next sample Clock.vi is originally a slow down. Without this vi, the program does just what I want except that I do not have strict error control.

  My confusion may be based on a lack of understanding of real-time systems. I don't think I do 'real time' as I run on an ordinary pc, so maybe I use some features that I wouldn't.

  Thank you

  Mike

  Mike,

  You should be able to read to return delays errors and warnings by setting the DAQmx real-time-> ReportMissedSamp property.  I think that if you enable this, you will see errors or warnings (according to the DAQmx real-time-> ConvertLateErrorsToWarnings) in the case where you use read-only.  I'm a little surprised that you have measured your application works at 120 kHz without waiting for next sample clock (WFNSC), although I'm not surprised that it would be significantly faster.  I think if you call read-only, you'll read the last sample available regardless of whether you would of missed samples or not.  When you call WFNSC, DAQmx will always wait for the next, if you are late or not sample clock.  In this case, you will wait an additional sample clock that is not the case in read-only.  Once again, I expect that, in both cases, your loop would not go to 120 kHz.

  Features real-time DAQmx (hardware Timed Single Point - HWTSP) are a set of features that are optimized for a one-time operation, but also a mechanism to provide feedback as to if a request is following the acquisition.  There is nothing inherently wrong with using this feature on a non real-time OS.  However, planner of a non real-time OS is not going to be deterministic.  This means that your app 'real time' may be interrupted for a period not confined while the BONE died in the service of other applications or everything he needs to do.  DAQmx will always tell you if your application is to follow, but can do nothing to guarantee that this will happen.  Thus, your request * must * tolerant bet of this type of interruption.

  There are a few things to consider.  If it is important that you perform the action at a given rate, then you should consider using a real-time operating system, or even with an FPGA based approach.  If it is not essential to your system, you might consider using is HWTSP, where you do not declare lack samples (DAQmx simply give you the most recent example), or you could avoid HW timing all together and just use HAVE request to acquire a sample at a time.  What is appropriate depends on the requirements of your application.

  Hope that helps,

  Dan

• DAQmx installation fails on openSuSE 11.1

  Hello

  I've been test driving openSuSE 11.1 today, and I discovered that DAQmx will not install correctly. It looks like the /lib/modules/2.6.xx/source for headers instead of lib/modules/2.6.xx/build. openSuSE install the headers for the construction and the packets from the kernel to the source source.

  John

  I've never understood how the modules version, so I just rebuilt the kernel with management module disabled versions. Now, it works fine.

  # CONFIG_MODVERSIONS is not defined
  # CONFIG_MODULE_SRCVERSION_ALL is not set

• How to insulate the wait at some of the code function

  I'm building a system to applaud ecg with an external Stimulator using TTL of programming impulses to work along the side of the information obtained from the ECG. The most important of these features is the heart rate. However, whenever I activate my pulse trains in the code, the function DAQmx wait until Done.vi made a break measure everything in the code, including the part of my code that monitors heart rate, which uses time to for. What I would like, is the wait function only affects the pulse train generators without a break anything else in the code. Is this possible? And if so how can I get there?

  I will attach my vi

  Your problem is that everything is in the same loop.  If the longest operation is going to determine the flow of the loop (and therefore rates of treatment).  What you really need to do, is to separate tasks on separate loops.  Use of queues or notifiers to communicate your data and commands between the loops.

• Failed Patch workders

  Hello
  
  I am applying patch 7660107 on our EBS 11i, but I got the error ff.:

  There are now 3 jobs remaining (current phase=A6):
      0 running, 3 ready to run and 0 waiting.
  
   Assigned: file invmsg.ldt   on worker  1 for product inv username APPS.
   Assigned: file invtable.ldt on worker  2 for product inv username APPS.
   Assigned: file invview.ldt  on worker  3 for product inv username APPS.Spawned Process 5714
  Spawned Process 5717
  Spawned Process 5720
  
     FAILED: file invmsg.ldt   on worker  1 for product inv username APPS.
   Deferred: file invmsg.ldt   on worker  1 for product inv username APPS.               (Deferment number 1 for this job)
   Assigned: file invmsg.ldt   on worker  1 for product inv username APPS.Spawned Process 5723
  
     FAILED: file invmsg.ldt   on worker  1 for product inv username APPS.
   Deferred: file invmsg.ldt   on worker  1 for product inv username APPS.               (Deferment number 2 for this job)
   Assigned: file invmsg.ldt   on worker  1 for product inv username APPS.Spawned Process 5726
  
     FAILED: file invmsg.ldt   on worker  1 for product inv username APPS.
  Completed: file invtable.ldt on worker  2 for product inv username APPS.
  Completed: file invview.ldt  on worker  3 for product inv username APPS.
  
  ATTENTION: All workers either have failed or are waiting:
  
             FAILED: file invmsg.ldt   on worker  1.
  
  ATTENTION: Please fix the above failed worker(s) so the manager can continue.

  How can I fix these workers failed?
  
  
  Thank you very much
  
  MsK

  Hi yxes;

  You can explain your problem to your boss if he or she can understand this cant patch complete today.

  In order to check please if you want to upgrade db 9.2.0.6 to 9.2.0.8 Hussein snoussi previous largest post:

  upgrade from 9.2.0.6 to 9.2.0.8 in Apps 11i db

  Respect of
  HELIOS

• Card nvidia, Linux Mint and W520?

  I'm on a W520 possessing a videocard of nvidia Quadro 1000 m, running Linux Mint 17 xfce (64-bit)

  Recentley, I came across a situation that required OpenGL 3.3. Best I can tell, my card intel integrated can support above 3.1!

  So I went to try to get the nvidia card work. Note to all the world at this point... Installation of the nvidia proprietary drivers directley Apparentley is the worst thing to do.

  I went to install the drivers of bumblbee (https://wiki.ubuntu.com/Bumblebee) and have since been frusterated with an nvidia card not working.

  I went to the cat bourdon, scourd the web for my problem, tried to re - install on a fresh USB... Nothing works.

  Has ANYONE else been in this situation? What are the steps that you took to get a functional nvidia card?

  Heres a dump of information from my problems. Basically, running glxgears optirun does not work.

  $ uname - a
  
  3.13.0 - 24-generic Linux sean-ThinkPad-W520 #47 - Ubuntu SMP Fri may 2-23:30 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
  
  ----
  $ optirun - vvv glxgears
  
  Reading file [DEBUG] [15874.859557]: /etc/bumblebee/bumblebee.conf
  
  [15874.860504] [INFO] configured driver: nvidia
  
  [15874.861018] [DEBUG] optirun version 3.2.1 from...
  
  [15874.861098] Setup Active [DEBUG]:
  
  Configuration file [15874.861134] [DEBUG] bumblebeed: /etc/bumblebee/bumblebee.conf
  
  [15874.861172] X [DEBUG] display: 8
  
  [15874.861207] [DEBUG] LD_LIBRARY_PATH: / usr/lib/nvidia-304: / usr/lib32/nvidia-304
  
  [15874.861245] Socket [DEBUG] path: /var/run/bumblebee.socket
  
  [15874.861281] [DEBUG] Accel/display Bridge: virtualgl
  
  [15874.861318] [DEBUG] VGL Compression: proxy
  
  [15874.861353] [DEBUG] VGLrun additional options:
  
  The LD of Primus [DEBUG] [15874.861389] path: / usr/lib/x86_64-linux-gnu/primus: / usr/lib/i386-linux-gnu/primus
  
  [15874.898691] [INFO] response: No - error: [XORG] (EE) NVIDIA (0): failed to initialize the NVIDIA GPU to PCI:1:0:0.  Please
  [15874.898733] [ERROR] can't access secondary GPU - error: [XORG] (EE) NVIDIA (0): failed to initialize the NVIDIA GPU to PCI:1:0:0.  Please
  [15874.898748] [DEBUG] Socket closed.
  
  [15874.898790] [ERROR] abandonment because the backup is disabled.
  
  [15874.898803] [DEBUG] kill all other processes.
  ----
  $ dmesg | tail
  
  [15687.546400] NVRM: rm_init_adapter (0) failed
  
  [15754.954991] NVRM: impossible to copy vbios for system memory.
  
  [15754.956859] NVRM: RmInitAdapter failed! (0 x 30: 0xffffffff:867)
  
  [15754.956868] NVRM: rm_init_adapter (0) failed
  
  [15873.990268] NVRM: impossible to copy vbios for system memory.
  
  [15873.992196] NVRM: RmInitAdapter failed! (0 x 30: 0xffffffff:867)
  
  [15873.992205] NVRM: rm_init_adapter (0) failed
  
  [15885.811425] NVRM: impossible to copy vbios for system memory.
  
  [15885.813323] NVRM: RmInitAdapter failed! (0 x 30: 0xffffffff:867)
  
  [15885.813332] NVRM: rm_init_adapter (0) failed
  ----
  $ sudo bumblebeed - debug
  
  [16077.147754] [DEBUG] bbswitch has been detected.
  
  Method of switching [INFO] [16077.147856] 'bbswitch' is available and will be used.
  
  [16077.147896] Setup Active [DEBUG]:
  
  Configuration file [16077.147932] [DEBUG] bumblebeed: /etc/bumblebee/bumblebee.conf
  
  [16077.147968] X [DEBUG] display: 8
  
  [16077.148021] [DEBUG] LD_LIBRARY_PATH: / usr/lib/nvidia-current: / usr/lib32/nvidia-current
  
  [16077.148062] Socket [DEBUG] path: /var/run/bumblebee.socket
  
  [16077.148098] [DEBUG] pidfile: /var/run/bumblebeed.pid
  
  Xorg.conf file [DEBUG] [16077.148134]: /etc/bumblebee/xorg.conf.nvidia
  
  [16077.148172] [DEBUG] xorg.conf.d dir: /etc/bumblebee/xorg.conf.d
  
  [16077.148207] [DEBUG] ModulePath: / usr/lib/nvidia-current/xorg, / usr/lib/xorg/modules
  
  [16077.148243] name [DEBUG] GID: Bumblebee
  
  Method of power [DEBUG] [16077.148278]: auto
  
  [16077.148314] [DEBUG] stop X to the output: 1
  
  [16077.148349] [DEBUG] Driver: nvidia
  
  [16077.148383] [DEBUG] Driver module: nvidia_304
  
  Stop State [DEBUG] map [16077.148418]: 1
  
  [16077.148673] [DEBUG] Process/sbin/modprobe started, 5234 PID.
  
  [16077.148791] [DEBUG] hide stderr for execution of/sbin/modprobe
  
  [16077.152464] [DEBUG] SIGCHILD received, but the wait failed with no child process
  
  [16077.152571] [DEBUG] Configuration test passed.

  
  [16077.152786] [ERROR] Daemon, already running, pid 2256

  ----

  modinfo nvidia_304 $
  file name: /lib/modules/3.13.0-24-generic/kernel/drivers/char/drm/nvidia_304.ko
  alias: char-major - 195-*.
  version: 304.117
  support: external
  License: NVIDIA
  alias: pci:v000010DEd00000E00sv * sd * bc04sc80i00 *.
  alias: pci:v000010DEd00000AA3sv * sd * bc0Bsc40i00 *.
  alias: pci:v000010DEd * sv * sd * bc03sc02i00 *.
  alias: pci:v000010DEd * sv * sd * bc03sc00i00 *.
  depends on:
  vermagic: 3.13.0 - 24-generic SMP, modversions mod_unload
  parm: NVreg_EnableVia4x:int
  parm: NVreg_EnableALiAGP:int
  parm: NVreg_ReqAGPRate:int
  parm: NVreg_EnableAGPSBA:int
  parm: NVreg_EnableAGPFW:int
  parm: NVreg_Mobile:int
  parm: NVreg_ResmanDebugLevel:int
  parm: NVreg_RmLogonRC:int
  parm: NVreg_ModifyDeviceFiles:int
  parm: NVreg_DeviceFileUID:int
  parm: NVreg_DeviceFileGID:int
  parm: NVreg_DeviceFileMode:int
  parm: NVreg_RemapLimit:int
  parm: NVreg_UpdateMemoryTypes:int
  parm: NVreg_InitializeSystemMemoryAllocations:int
  parm: NVreg_UseVBios:int
  parm: NVreg_RMEdgeIntrCheck:int
  parm: NVreg_UsePageAttributeTable:int
  parm: NVreg_EnableMSI:int
  parm: NVreg_MapRegistersEarly:int
  parm: NVreg_RegisterForACPIEvents:int
  parm: NVreg_RegistryDwords:charp
  parm: NVreg_RmMsg:charp
  parm: NVreg_NvAGP:int

  I have no experience with anything else that Fedora works on my W520, but before installing dual boot linux partition, I turn it on discrete rule. It is a bit of annoyance to have this go in the BIOS before the OS, but it of the only way I got everything to go smooth and figures.

• Why is-DAQ-200714 fatal error?

  I'm having a problem where a system that works well for a while, with a good margin (rate of 1 kHz loop, 300uS PCL loop duration), suddenly throws the error-200714 and stops. I have the filter DAQ errors on, and it's performance that are linked, so why this closure of the system rather than increment on behalf of HP?

  Thank you

  The explanation of the error is "Acquisition has stopped because the driver could not transfer the data from the device to the computer's memory rather quickly. This was due to limitations of the computer system.

  Reduce your sample clock rate, the number of channels in the task or the number of programs on your computer that runs at the same time. »

  Hello Stephen,

  You get this error is because the program is not keeping up with the sample clock.

  I recreated this (outdoor VeriStand) by running the example of shipping single HW-Timed Point LabVIEW and increasing speed until I got this error. I actually got error-209802 several times before to do-200714. The first error is recoverable and I could ignore it and continue, the second execution stops when it is thrown.

  Error-209802:

  «DAQmx wait the next sample clock detected one or more examples missed clock of the device since the last call to wait for the next sample clock that indicates that your program is not keeping up with the sample clock.»

  To remove this error, slow down the sample clock, or else modify your application so that it can follow the sample clock. Alternatively, consider conversion errors affecting true property warnings and then assigned to the case of the appropriate warning. »

  Error-200714:

  "The acquisition has stopped because the driver could not transfer the data from the device to the computer's memory rather quickly. This was due to limitations of the computer system.

  Reduce your sample clock rate, the number of channels in the task or the number of programs on your computer that runs at the same time. »

  Based on what Jarrod mentioned above, the original error might be filtered by VeriStand judging by the part highlighted in blue to the first error. I suspect that the error-200714 is fatal because of the part highlighted in red above; the acquisition has ceased.

  If you monitor the DAQ system channel error, you see error-209802 so? Slow down the rate PCL resolve these errors?

  I hope this helps!

  Trent

• How to clear the output buffer, possibly resize and burn again, before you begin the task of output

  I use PyDAQmx with a USB-6363, but I think the question is generic to DAQmx.

  I have an output buffer that I want to be able to (re) write to without starting the task output.

  More specifically, I have a graphical interface and a few sliders, the user can move.  Whenever the slider changes, a new set of values is loaded into the buffer output through DAQmxWriteAnalogF64.  After you set the value, the user can click on a button and start the task output.

  In some cases the change in cursor does not require a change in buffer size, only a change in the data.  In this case, I get the compalint following DAQmx as they tried writing:

  The generation is not yet started, and not enough space is available in the buffer.

  Set a larger buffer, or start the generation before writing data more than content in the buffer.
  Property: DAQmx_Write_RelativeTo
  Value: DAQmx_Val_CurrWritePos
  Property: DAQmx_Write_Offset
  Corresponding value: 0
  Property: DAQmx_Buf_Output_BufSize
  Corresponding value: 92

  In other cases the change in cursor requires both change in the size of the buffer and data modification.  In this case, I get the following, but only after that do a few times each time increase the size of the writing.

  DAQmx writing failed because a previous writing DAQmx configured automatically the size of output buffer. The size of the buffer is equal the number of samples written by channel, so no additional data can be written before the original task.

  Start the generation of before the second writing DAQmx or set true in all instances of writing DAQmx Auto Start. To gradually write to the buffer before starting the task, call DAQmx Configure an output buffer before the first writing DAQmx.
  Task name: _unnamedTask<0>

  State code:-200547
  function DAQmxWriteAnalogF64

  I tried to configure the output via DAQmxCfgOutputBuffer buffer (in some cases, by setting it to zero or a samples, then save again, in an attempt to clear it) but that doesn't seem to do the trick.

  Of course, I can work around the problem by loading data only when the user clicks the end button, but not what I'm asking here.

  Is it possible to "remake" the writing of output before you begin the task?

  Thank you

  Michael

  Today I have no material practical to validate, but try unreserving task before writing the new buffer:

  DAQmxTaskControl (taskHandle, DAQmx_Val_Task_Unreserve);

  With a simulated device, he made the error go away in case the buffer is the same size.  You will need to validate if the data are in fact correct, but I think it should be (unreserving I would say reset the write pointer so the old buffer are replaced with the new data).

  I always get errors when you try to change the size of buffer if (on my 6351 simulated).  I posted some similar mistakes about the reconfiguration of the tasks here, I guess it is possible that this issue has also been set at 9.8 (I always use 9.7.5 on this computer).  If the behavior is still present in the new driver, and also appears on real hardware (not just simulated), then it seems that this is a bug of DAQmx someone at OR should be considered.

  I wrote a simple LabVIEW VI that captures the error in order to help people to NOT reproduce it:

  

  The best solution at the moment would be likely to re-create the task if you need to change the size of the buffer (or avoid writing data until you are sure what will be the size of buffer).

  Best regards

• detection of task over DIO

  Hello

  How can I know that triggered external DIO out of finite samples have completed execution?

  I see there is a 'DAQmx is task performed?', but it means that I have to constantly monitor the task. Is there a way to generate an event or declaring that the task is completed?

  Also, if I use the "Start.Reftrggerable" correctly and task arm iteself once it fires, how I know how often the task is completed, that is the same question as above, how know exactly if the task is accomplished and don't miss not events of the?

  Thank you

  There are the DAQmx wait until what Done.vi.  It is in the pallets, right next to Scripture DAQmx.

  I'll have to do some digging to see if there is a number of triggers property hides somewhere in the DAQmx API.

• Error 229789

  Hello

  I have a problem with the DAQmx Assistant failing out and back, an error Code - 229789.

  I am new to this programming, I have only used your program for a few weeks or.

  I bought a USB-6211 box to connect an analog only to produce a graph of production.

  And as a first step, every thing worked fine, after the third day to try different things in the program.

  The VI was developing I Started failing when I said Run. It started when I rebooted the computer for the day.

  And continued vulnerabilities.

  I reduced the Rafale program down to the components a graph and an analogue to the entry on the VI using the DAQ Assistant, and he always fouls out. It still gives Me the same fault. "Error-229789 VI DAQmx create task: 1" "internal software error has occurred in the MIG software.

  I uninstalled and reinstalled all the LabView programs components (3) times. This last time, I upgraded to the Ni DAQmx Device Driver 8.9.0F4

  I'm using LabView 8.6, I read of your forms related to this issue and check the NIMXS. EXE, it is running, I also check to see if my firewall was blocking it and it isn't. And I use a computer Stand-A-alone and I am the administrator.

  Because it worked for a few days, the only thing I can think is that I have change a few Y A_ somewhere it another way to program The USB-6211 if we Cant Figure this problem Out.

  Thanks Mark

  Please help Mark

  Hi Mark-

  Looks like you have the MAX database (Measurement and Automation Explorer).  Have you tried opening MAX to see if your device appears under the devices section and Interfaces?  Do you see any abnormal activity to the MAX?

  It is probably best to follow this section of the knowledge base on removing the Corruption of database of MAX.

  Let us know how it goes.  Good luck to you!

• How do I detect when a write of correlated digital output is completed

  Hi LabGurus

  I'm trying to synthesize a SPI signal on the output lines digital stamped usin a M - Series USB Daq (6225, 6229).

  I wrote most of the code and have developed the following problems:

  When I use 'finished samples' to the clock mode, the waveform it is limited to the size of the buffer on board. There is no specific error, but the output waveform is strangely truncated States 1027. The nidaq buffer is fixed and changing the buffer on Board has no effect.

  When I use continuous samples, there is no way to detect when the task is finished 'Really' (I can clarify in the last round of data is transferred to the device, but not when he was timed out of the unit).

  "Task Daqmx is over" and "Daqmx Wait for completion" give no idea.

  I detect when the last USB device transfer is completed using a write property node Dqmx and comparing 'written total samples' at the 'current write Position.

  The function works as much as I leave long enough so that the task is completed. In almost a fixed delay is not acceptable.

  Timmar,

  For the finite method, have you tried to change the value of "samples per channel" on the VI of Timing DAQmx?  It's what you define for your task to know how many points to wait at the exit.  The default value is 1000.  I hope this helps.

  Kind regards

  Brian T

  Technical sales engineer

• Integrate the outputs analog with analog inputs

  I have a program that displays 2 analog output waves and a separate program that captures the analog data through several materials of NEITHER. I need to integrate the program outputs analog in my analog input program.

  The program of analog output is fixed as "AO_Triggers_LowLevel.vi" and the analog input is fixed as "ExperimentDAQ.vi". When I try and integrate these programs I get 'error-200560 occurred at DAQmx waiting until the Done.vi' to my function to wait until it makes my task of analog input (background of the program). I think it is my mistake in the order that I'm wiring to the top of my son of error but I'm not sure. I watched several tutorials (Timing and synchronization features of DAQmx) but I'm totally stuck.

  Any suggestions are greatly appreciated. Thank you!

  Alberto M.

  I think I've fixed this problem. I extended my flat sequence structure to include the lines of task and error of my task outputs analog and things seem to work.  I'm still not sure about what caused my error and why it has solved the problem...

• The sticky engine

  I have a very funny bug (?). In the extract which is attached when the condition for both cases structures become TRUE, I am turning off an engine power of 22KW, bit, he wrote to a function of writing DAQMX and goes to the next case. 3 of the 10 times that the engine cuts, leading to a messed up the machine sequence. I don't know that I'm passing to the next case as changes in Message string as expected. In fact this can occur only if the BAU changes before the cluster of output is written to. But I'm sure that it can happen that both are updated in the same case?

  What can be wrong in such a situation the DAQMX write failed to refresh at times? And being a random faultr, I am unable to conceive any trap the error.  Going nuts on the issue. Any tips? Or is there is a fundamental flaw in the approach? (The TimedLoop turns to 10ms without warning 'Finished' later).

  Thank you

  
  

• Defective 9239090 patch on windows server 2008

  Hi I am applying patch 9239090 on windows server 2008
  
  He gave me below error: -.
  

  ATTENTION: All workers either have failed or are waiting:
             FAILED: file ce8509466.sql on worker  1.
  ATTENTION: Please fix the above failed worker(s) so the manager can continue.

  I say keep... .and where to look for the error.
  
  Thank you
  Katia

  What should I do now?

  If you've run the code manually, go the worker failed via adctrl (option #8 - hidden option) for that worker failed.

  Thank you
  Hussein

• SOAP (timeout &amp; service down) error handling

  Hi all

  I've implemented a WSDL connection with a postExecute event handles the SOAP error messages (described in the XFA specification). The form must handle the following scenarios;

  1. functioning: WSDL returns the soap fault code.

  2. failure operation (soap WSDL returns error code).

  3 connection timeout (?-simulated by setting a breakpoint in WSDL).

  4 cannot connect to WSDL (?-simulated by stopping the service WSDL).

  First of all, two scenarios are correctly handled, but I'm having a harder time with the last two. Initial tests have shown that player performed these scenarios by displaying an error message, but the postExecute event does not what is logical. I have implemented this solution in another form and can not get the drive to generate warnings more. Note that the first two scenarios work very well in the new form. I noticed a Times Reader wrote the warning in the JavaScript debugger. Don't know why since the debugger is always enabled. Why he would write for her this time and not again?

  Questions

  1. is there something that can affect this type of e-mail? Preferences of the reader?

  2 is there a way to better/more safe, consistent waiting/fail another connection times that relying on the reader to treatment?

  Built form in Designer ES2, version 8.1 of the target

  8.4 drive

  Reader Extensions ES2

  Thank you very much!

  Helen

  The examples I have seen use a try block catch and if the capture is fired there is a problem. It returns a number (14) but no description so that you can test it to the e.number == 14 and write your own message. Other that that, I don't know a way (unless you use the Soap Acrobat object method).

  Hope that helps

  Paul