Here is a SOCKET toolbox for Scilab. This toolbox enables communications between an instrument or server located via TCPIP protocol and Scilab.
Upload date : 2010-01-19 16:09:34 MD5 : 5cd4df53ec983251a2ed9c028d466887 SHA1 : 623b6939f9963aebe911306ee7032f68d2d71b5a Downloads : 634 File list
Linux binary version Automatically generated by the atoms compilation chain
Upload date : 2010-03-04 09:48:42 MD5 : fbc9debcf44b236830b16822697255f1 SHA1 : 179bdfc81476238ad3f86b2126835aa972972c09 Downloads : 4055 File list
Windows binary version Automatically generated by the atoms compilation chain
Upload date : 2010-01-19 17:55:17 MD5 : 5dfcadabb335d22403126aae8f89819b SHA1 : a73779b189865fb6866c76c335584e829c6b8e91 Downloads : 3465 File list
Hi, any info appreciated about working environments using TCP/IP connected data acquisition like labjacks UE9. thanks
I had a problem with SOCKET_write, it gave one enter command more than necessary. In my case the result was that I could not see the answer to the command, but instead the answer to an empty command (simple enter). I fixed it by removing the +ascii(10) part in macros/SOCKET_write.sci, then rebuilt from the source (had to outcomment some lines that gave problems in builder.sce) best regards, Oscar
Hi, I tried to access simply a HTTP page through socket using following sequence : SOCKET_open(1,<address>,80); SOCKET_write(1,"GET HTTP/1.0"); r = SOCKET_read(1); In that case, it seems that SOCKET_read output cannot be "silently" redirected to the variable, and all content is fed to the interpreter command line. Am I missing something, or is there a way to avoid this ? Best Regards, Dominique.
> r = SOCKET_read(1); > > In that case, it seems that SOCKET_read output cannot be "silently" redirected > to the variable, and all content is fed to the interpreter command line. For me, it works with SOCKET_read() as well as with SOCKET_query(). Yet, the module has not been updated since your post... The only issue is about ' in the answer (see my other post today, and the fix). Regards Samuel
Hello, SOCKET_read() bugs when the answer contains some ' chars (as it bugged for " chars). The fix is the same: Replace // bug en cas de "" "ScilabEval ""mat=\[\""[string map {\"" \""\"" } $tclsocketligne]\"";mat\];"""; with // bug en cas de " ou ' "ScilabEval ""mat=\[\""[string map {\"" \""\"" \'' \''\''} $tclsocketligne]\"";mat\];"""; Then it works Cheers Samuel
> Hello, > > SOCKET_read() bugs when the answer contains some ' chars > (as it bugged for " chars). The fix is the same: > > Replace > // bug en cas de "" > "ScilabEval ""mat=\[\""[string map {\"" > \""\"" } $tclsocketligne]\"";mat\];"""; > > with > // bug en cas de " ou ' > "ScilabEval ""mat=\[\""[string map {\"" > \""\"" \'' \''\''} > $tclsocketligne]\"";mat\];"""; > > Then it works > > Cheers > Samuel I had tried getting in touch with the author about this bug almost a year ago but never got a response. I've pushed out a fixed version of this here: https://github.com/sengupta/scilab-socket (feel free to use this version) I have had to do this since I am writing a toolbox that will require socket functions (this toolbox: https://github.com/sengupta/scilab-http) to work; and this bug would not allow me to use the existing socket toolbox.
> Replace > // bug en cas de "" > "ScilabEval ""mat=\[\""[string map {\"" > \""\"" } $tclsocketligne]\"";mat\];"""; > > with > // bug en cas de " ou ' > "ScilabEval ""mat=\[\""[string map {\"" > \""\"" \'' \''\''} > $tclsocketligne]\"";mat\];"""; Fixed in the 2.0.3 version
Hi, I am new to both linux and Scilab. I have Ubuntu 12.10 and Scilab5.3.3. I have downloaded socket_toolbox_2.0- 1.bin.linux.tar.gz file. But I don't know how to include it in Scilab.