sengupta/scilab-serial

Serial Communication Toolbox for Scilab

scilab-serial's Issues

var MSDOS no longer exists in Scilab 5.4

From a comment on the ATOMS page by Samuel Gougeon

Hello,
The constant MSDOS -- for instance used in openserial() -- no
longer exists in Scilab 5.4. Please upgrade using getos() instead.
Regards
Samuel

Error when starting Scilab with toolbox

Guys,
Please advise.
New to Scilab. Very expeienced with LabView and VISA.
Installed Scilab version 6.0.2 on Lenovo laptop running current Windows 10 OS 64 bit.
Obviously no NI interface hardware.
Most modern instruments include USB or Ethernet communication ports.
Additionally, does this toolbox require a separate VISA installation?
If so, which version of VISA? Latest version is 19.
Thanks in advance,
Ted

Get the following message in the console after installing toolbox and restarting Scilab:

Starting the Serial Toolbox
Load macros
Load help

Start VISA Integration Toolbox
Load macros
Load gateways
atomsLoad: An error occurred while loading 'visa-0.9.1':
link: The shared archive was not loaded: The system cannot find the file specified.
Warning : redefining function: startModule . Use funcprot(0) to avoid this message

readSerial problem in RTU mode

I am receiving "01 03 02 00 23 f9 9d" via serial COM port in RTU mode, but readSerial gets me "01 03 02 20 20 20 20". [I converted the recieved string character by character like this: buf = readserial(h); ch(i) = ascii(part(buf,i:i)). Might be ugly...]. I copied the readserial function and removed ascii conversion in last line. This solved the problem for me now. Maybe there should be a function like readserial in RTU mode.

Add usage notes

• Add notes on how to specify which port to use, on Windows and on Unix systems.
• Add notes on Mac compatibility.

Issues!

Under Ubuntu 11.10, when trying to open a serial port, the machine hangs up on the
openserial command. Even with the the rights to use the serial ports.

Under Windows XP, the serial port communication works except the data returned, which is set to be translated to binary, seems to be an ascii string. Since there are no ascii codes corresponding to the data transmitted, conversion to integers yields incorrect results.