Jump to content

fliesskomma

Members
  • Posts

    2
  • Joined

  • Last visited

fliesskomma's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Hi folks, since I'm glad NI solved the naming conflict problem, I'm not very happy about the funny difference of the "current VI's Path" behaveure in llb's, or exe files. I need the name of the mail llb, or exe file, containing all vis. Chain and applications directory just give back paths, or names of the top level vi, but not the name of the llb, or exe container. Anybody know, how to handle this, working for llb and exe containers as well? fliesskomma
  2. ZITAT(Val Brown @ Jun 2 2007, 12:29 PM) Hi Val, I began using legacy serial drivers with LabView 6.0 which worked quite well with most devices to communicate with. Later on, I developed Software for some serial communication with several serial ports, beeing busy at the same time. Every time when there was a continous (115kbd) bytestream to read, with a size above of a couple kByte, serious dataloss occured. So I changed to VISA (Lv6.1 ... Lv7.1), where I could adjust read- and write buffer size and all communication errors vanished. The adjustable buffer feature of VISA was the deciding reason for me to change. I didn't find this feature in the legacy drivers. Please tell me, if I'm wrong. Maybe this information could prevent you running into problems.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.