VISA Write sends continuously

[JÞB]

OK this has gotten interesting.  Time to RTM can you link to the users manual or provide the model number for the Flame Ionization Detector.  We must have miss-understood the command structure.

here is the LV10 version Mo

[MoReese]

Thanks Jeff.  RTM (Read The Manual)?  Where is this detector mentioned (or is this an inside joke I am unaware of)?  Perhaps I missed something.

So let me get this straight.  Is the OP claiming that 0x11 is being sent repeatedly with this code? Just trying to get a handle on his problem as well as understand the apparent impossibility of that happening.  But then I've seen many apparent things that can't be explained.  The code runs as expected for me; although, I have not sniffed out the serial port to see what's happening there.

[JÞB]

---

@MoReese wrote:

Thanks Jeff.  RTM (Read The Manual)?  Spot on

Where is this detector mentioned (or is this an inside joke I am unaware of)?  Perhaps I missed something.  OP in post 1 mentions FID

So let me get this straight.  Is the OP claiming that 0x11 is being sent repeatedly with this code?

---

I bet it will make perfect sense when we figure it out

[SteveChandler]

---

@MoReese wrote:

Is the OP claiming that 0x11 is being sent repeatedly with this code? Just trying to get a handle on his problem as well as understand the apparent impossibility of that happening.

---

The only thing that would explain it is if he is pressing run continuous. I asked above but still have not seen an answer. (Or a weird driver problem with the virtual serial port. I have never used or heard of a virtual serial port)

[JÞB]

Steve,

I bet thats a Virtual COM Port as in a usb to rs-232 VCP

[gatekeeper]

I have not been pressing "Run Continuously." 

The virtual serial port isn't a USB-RS232 adaptor; it is a program that creates a "fake" serial port on your computer to provide a destination for testing programs that use serial communications without actually connecting to the device.

I've attached the manual for the FID, the communications info is in chapter six.

[JÞB]

Thanks for the manual and the explaination on the VSP target (I've never used one either-and won't speak for its reliability)

with the vi in its current state you write 0x11 ^Q "start data stream" and the term character 0x0A which is not recognized be the device.  Change the term char enable to F and "Bob's your uncle" - or at least you wrote the code to spec!  the true test is targeting it to real hardware.  then you'll see how close the tech writers got to what the engineers produced.  (You'ld be surprised how often that breaks down)

Good luck!

[SteveChandler]

Gatekeeper, did you ever find out what was going on?

[gatekeeper]

Not yet, I've been pulled away from the project by more important work.  I should know sometime next week.

[gatekeeper]

Finally got back to the project.  It turns out I hadn't installed the NI-VISA package. 

Seems obvious now, but it wasn't included as an option on the installation discs - I had to download the package from NI.  Also, the VISA functions are included in the development environment even without the package installed, and that's what threw me for a loop.