labview driver for vitrek 4700

[idans]

those 2 vis dealing with buffers have no effect over this spooling phenomena , i removed them but i get same phenomena , read success only at second iteration  

[rolfk]

If you read the Operating Manual it says in Section 7 following.

Commands are terminated by either <CR> OR <LF> so you can append \r or \n in LabVIEW to your string (but only if you set that string constant to backslash display mode, right click on the string constant and select "'\' -Codes Display").

The response is always terminated by a <CR> followed by a <LF> so you should probably set your termination character to a "line feed" constant, otherwise you will after the first query command always receive the terminating <LF> character from the previous response as first character in your read back string.

Do not use a loop around commands!

[idans]

thanks Rolf

i do add manually lf character and I enabled termination character , now I checked my code using LAN interface and it work fine but i still have problem with RS232 

[rolfk]

Sorry my crystal ball has been defective for quite some time, so I can't see your latest code that you haven't attached. 😀

[idans]

here is a picture of my latest initialize vi code

somehow it works fine using LAN but does not work using RS232

[rolfk]

What would you say if I send you a pic of my car and ask you to tell me why it doesn't start? Most likely you would think, What an *hole! How am I supposed to know from a picture!

Save your entire VI driver back to at least LabVIEW 2018 or earlier if you use LabVIEW 2019 and ZIP up those VIs and attach the ZIP archive to your post. I can't see from the pic what your subVI does that you use to send the *IDN? comment. All I can see that you probably should remove the Termchar property writes outside of the first case structure!

[idans]

here you go

[idans]

here is full project , it works fine via LAN 

[idans]

i hope now it works' uploads

[rolfk]

I’ll take a look at it.

The upload worked both times. I recently noticed myself that when you attach things they don’t immediately are visible in the post. I suppose that they run a virus scanner or something and only make it visible after the scan was successful. Refreshing the web page after a short time always made the attachment show up eventually.

I think it would be helpful if the forum software gave some form of feedback that there is actually an attachment but as disabled link that can’t be clicked yet, maybe with the text “scanning files”.