For automation purpose i am trying to set a voltage on power supply(peaktech 1565 model).
When i used the below script, i am getting the error as
Sending Message to first instance Failed:
ErrorCode=6
Error: The handle is invalid
Error 5 is an UIPI access problem. Try starting the first Instance with realterm.exe first=2 [other params]
code is like this:
echo off
echo on
set rt=realterm
start %rt% caption=BatchDemo s1=SOUT0 s1=VOLT021
pause Press any key to close Realterm
start /wait %rt% first quit
"VOLT021" is send to editbox but it is not reflecting in window or sending to hardware device.
I have set CR for end of command in init file already.
I can't use Win10 at present, but possibly permissions need to be changed, or perhaps the ongoing security changes have broken interwindow comms. You don't seem to be needing to do it anyway, in the example batch file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hello all,
For automation purpose i am trying to set a voltage on power supply(peaktech 1565 model).
When i used the below script, i am getting the error as
Sending Message to first instance Failed:
ErrorCode=6
Error: The handle is invalid
Error 5 is an UIPI access problem. Try starting the first Instance with realterm.exe first=2 [other params]
code is like this:
echo off
echo on
set rt=realterm
start %rt% caption=BatchDemo s1=SOUT0 s1=VOLT021
pause Press any key to close Realterm
start /wait %rt% first quit
"VOLT021" is send to editbox but it is not reflecting in window or sending to hardware device.
I have set CR for end of command in init file already.
version used : Realterm_3.0.1.44
OS : windows 10
@crun please provide your feedback on this.
It will be a great help , if you can provide feedback as soon as possible .
Probably your are misunderstanding S2, S2. They don't send strings, they just load the editboxes
https://realterm.sourceforge.io/#Command_Line_Parameters
I can't use Win10 at present, but possibly permissions need to be changed, or perhaps the ongoing security changes have broken interwindow comms. You don't seem to be needing to do it anyway, in the example batch file.