Why it does not work as Hyperterminal?

[plit string]

Sorry, I did not send a corrected file (with detail setting), here it is!

Note: To be sure that I send the right ascii code, I display the sending string in Hexadecimal. Also since when hitting the ENTER key is equal to 0x0D that is why I changed ... but anyway, even I try some thing else with or without after "*debug", it does not work!

 

[Dennis_Knutson]

I really don't know what you are actually doing now. The first VI had the string control set to '\' Codes Display. Then you send two other VIs with the string control set to Normal display and in your text, you say you are using Hex display. Just set it to '\' Codes and if you want to, create an indicator in hex display and connect it to the control. Save that VI and try it.

[plit string]

I did try & it also does not work. I also tried to see I am able to send the "*debug\r" out through COM1 (with other Hyperterminal in another PC) & it sends/receives the strings OK (means the VI working file).

However, I just remember 1 thing that is the device has USB connector & after installing its driver, the Virtual COM3 is created.

Might be the Hyperterminal can work with the USB Virtual COM port & NI can not! Because I did try to use the Measurement & Automation Explorer to try Write Vi & read Vi directly and it happen exactly as in LW program

This time might it help to explain my problem?

[TCPlomp]

There is no reason why LabVIEW (what is LW?) couldn't communicate with a USB-based RS232 interface (after you have installed all the drivers off course).

Did you set a termination character in the LabVIEW application?

Ton

[plit string]

1. The device I am trying to communiacte is EK302DL Evaluation kits & I am not sure NI can support its driver? After installing its driver the Measurement & Automation Explorer seeing the Virtual COM3 & after Seral conflict baudrate between Visa (9600) & Windows (115200), I did correct it successfully!

    *) I am not sure NI can support this Virtual COM3!

2. I did try as all of you suggested & it still does not work (sorry about typo-error LV not LW) 

3. I also did try with Serial sample CVI that able to set all Serial parameters in Run mode (C:\Program Files\National Instruments\CVI80\samples\rs232\Serial.cws), I also did try to send *debug command with CR or LF or none ... but it also does not work at all (no Serial error happened)

 I hope you can know more detail now! I am still trying & trying!

[plit string]

I found the problem, as in NI mentioned that Hyperteminal received data with slow typing speed, meanwhile any SW that sends the whole string in one shot! I did send bity-by-bite & it work!

Thanks for trying to help