12-14-2018 02:30 AM - edited 12-14-2018 02:34 AM
@Joshua38 wrote:
OK, I have tried removing the "\n" and wiring a "false" constant to the "enable terminating character" terminal, but that didn't solve the problem.
Is that a logical AND or is it an OR? If it is an AND then you may have changed one variable in the equation to much. I would expect the device to need to receive ONE termination character (sequence) in order to know when the command is finished. And it may not be "line feed" (\n) but could be also "carriage return" (\r) or the DOS end of line indication which is both characters after each other (\r\n). Other characters are absolutely possible too such as "End of Text" (\03) or whatever the developer of that device fancied at that day!
Without a proper protocol documentation you can keep trying the next 100 years and maybe never get a working solution. Even with protocol documentation it takes usually a few hours or days, as developers are surprisingly bad at documenting a communication protocol in an unambigous and easy way.
12-14-2018 06:16 AM
Success! Adding the \r in front of the \n did the trick. Thanks for all the helpful advice.
01-22-2020 11:52 AM
Anyway you could send me the vi for this? I don't have a serial settings object in my library and would also like to examine the other bits too.
01-22-2020 01:46 PM
@crash_override wrote:
Anyway you could send me the vi for this? I don't have a serial settings object in my library and would also like to examine the other bits too.
You are probably looking for the VISA Configure Serial Port.