Scilab Home Page | Wiki | Bug Tracker | Forge | Mailing List Archives | Scilab Online Help | File Exchange
ATOMS : BackDoor details
Please login or create an account

BackDoor

This module opens a BackDoor into Scilab workspace.
(5764 downloads for this version - 6084 downloads for all versions)
Details
Version
0.2
A more recent valid version exists: 0.21
Author
Federico Bergero
Owner Organization
CIFASIS - UNR
Maintainers
Federico Martín Bergero
Administrator Atoms
William Thissell
Category
License
Creation Date
April 15, 2015
Source created on
Scilab 5.3.x
Binaries available on
Scilab 5.3.x:
Linux 32-bit Windows 32-bit Windows 64-bit Linux 64-bit
Scilab 5.5.x:
Linux 32-bit Windows 32-bit Windows 64-bit Linux 64-bit
Install command
--> atomsInstall("BackDoor")
Description
            This module opens a BackDoor into Scilab workspace. 

It works by creating a new thread that listens on requests on a TCP port.
Each string send to that thread is executed in the Scilab workspace and a result
is sent back to the caller when requested.

For testing load the module (when the module is loaded you should see something
like:
	
	BackDoor: listening to commands on TCP port 28020

and then try opening a telnet connection 
	
	telnet 120.0.0.1 28020

and start writing Scilab commands as you would on the command window (with a new
line in the end). NOTE: the port used is 27020 in windows and 27020 + UID in
Linux. This is to allow multiple users using the module.

The result of the calculation is saved in the bd_result variable in Scilab.

If you need to run a command that shouldn't be saved in bd_result you can prefix
your command with "\", for example "\load('file.dat')". 

Also if you type a '@' you will get the value of bd_result(in binary form of a C
double). If you type "?" you will get the value of bd_result in text.

The intention of this module is to use it with PowerDEVS (https://sourceforge.net/projects/powerdevs)
 in order to process simulation results in the Scilab enviroment.
            
Files (9)
[22.17 kB]
Source code archive

[23.17 kB]
Linux 32-bit binary for Scilab 5.3.x
Linux 32-bit
Automatically generated by the ATOMS compilation chain

[35.24 kB]
Windows 32-bit binary for Scilab 5.3.x
Windows 32-bit
Automatically generated by the ATOMS compilation chain

[35.39 kB]
Windows 64-bit binary for Scilab 5.3.x
Windows 64-bit
Automatically generated by the ATOMS compilation chain

[24.49 kB]
Linux 64-bit binary for Scilab 5.3.x
Linux 64-bit
Automatically generated by the ATOMS compilation chain

[28.46 kB]
Linux 32-bit binary for Scilab 5.5.x
Linux version (i686)
Automatically generated by the ATOMS compilation chain

[48.70 kB]
Windows 32-bit binary for Scilab 5.5.x
Windows version (i686)
Automatically generated by the ATOMS compilation chain

[48.87 kB]
Windows 64-bit binary for Scilab 5.5.x
Windows version (x64)
Automatically generated by the ATOMS compilation chain

[27.65 kB]
Linux 64-bit binary for Scilab 5.5.x
Linux version (x86_64)
Automatically generated by the ATOMS compilation chain

News (0)
Comments (8)     Leave a comment 
Comment from Gaston Melo -- September 11, 2018, 04:00:49 PM    
hi,
    I install scilab 6.0.1 and needed BackDoor to work with octave. After install backdoor
scilab prompt lib: Old binary lib detected. Please recompile it for Scilab 6.
Is there a way to recompile backdoor to use with scilab? Or do I need to install old
vesion of scilab? any help will be appreciate. Thanks. Gaston
Comment from Federico Martín Bergero -- September 11, 2018, 11:56:20 PM    
Hi Gaston I'm out of time right now to re-compile it right now but you are more than
welcome 
to give it a try [1]. If you download the source and exec builder.sce it should recompile
it 
(you need a gcc toolchain)

[1] https://wiki.scilab.org/howto/Create%20a%20toolbox#Build_and_load_a_module
Comment from Ezequiel Pecker Marcosig -- September 22, 2018, 11:18:48 PM    
Hi all,

I had the same problem as Gaston. I followed the steps in the link and executed the
script: builder.sce, which is placed in the root folder of BackDoor toolbox. Then, I got
the following error message: "error: 'pvApiCtx' undeclared" in function
SendScilabJobBD
when compiling backdoor.c.

Do you know how to solve this problem?

Thanks in advance.

Regards

Comment from William Thissell -- January 25, 2019, 04:19:43 AM    
Dear Colleagues,
    I built an rpm for SciLab V 5.5.2 for Centos 7.5 and installed it for use with this 
backdoor module.  Unfortunately, this version of SciLab is too old to properly support the

4K display on my development computer because the icons, fonts, and spacing between lines 
are all screwed up and I am unable to make this version of SciLab usable through the 
available options.
    I therefore have a requirement to get this backdoor module to work with the SciLab V 
6.0.1 to work.
    Is it possible for the developer of this module to or someone else fix the issue with 
compiling this module for SciLab V. 6.0.1 and create binaries for us to use?  
    Thank you in advance for your reply.
    
Comment from William Thissell -- January 26, 2019, 01:05:40 AM    
Dear Colleagues,
    I built an rpm for SciLab V 5.5.2 for Centos 7.5 and installed it for use with this 
backdoor module.  Unfortunately, this version of SciLab is too old to properly support the

4K display on my development computer because the icons, fonts, and spacing between lines 
are all screwed up and I am unable to make this version of SciLab usable through the 
available options.
    I therefore have a requirement to get this backdoor module to work with the SciLab V 
6.0.1 to work.
    Is it possible for the developer of this module to or someone else fix the issue with 
compiling this module for SciLab V. 6.0.1 and create binaries for us to use?  
    Thank you in advance for your reply.
    
Comment from William Thissell -- January 28, 2019, 02:10:43 AM    
Dear Colleagues,
    I built a rpm for SciLab V 6.0.1 for Centos 7.5 and installed it hoping that it would 
be more usable with my 4K display than V 5.5.2 and it is somewhat more usable than V 
5.5.2, but many of the fonts and icons are still way too small and many of the windows 
truncate the rows, making the text challenging to read.  
    I then ported the backdoor module for SciLab V 6.0.1 and I tried to build it, but I am

unable to do so because I think I require atomsCC to do so, but I am unable to download 
the source code for it because I do not have the required permissions. 
    How do I upload the port that I performed in order to use the Atoms automated build 
toolchain, or how do I build the port that I performed and then upload the built atom? 
    How may I obtain access to a beta build for the next version of SciLab to test if it 
is more usable with a 4K display than V 6.0.1?
    Thank you in advance for your reply.
Comment from William Thissell -- January 30, 2019, 01:09:05 AM    
Dear Colleagues,
    I built an rpm for SciLab V 5.5.2 for Centos 7.5 and installed it for use with this 
backdoor module.  Unfortunately, this version of SciLab is too old to properly support the

4K display on my development computer because the icons, fonts, and spacing between lines 
are all screwed up and I am unable to make this version of SciLab usable through the 
available options.
    I therefore have a requirement to get this backdoor module to work with the SciLab V 
6.0.1 to work.
    Is it possible for the developer of this module to or someone else fix the issue with 
compiling this module for SciLab V. 6.0.1 and create binaries for us to use?  
    Thank you in advance for your reply.
    
Comment from William Thissell -- January 31, 2019, 02:30:55 AM    
Dear Colleagues,
    I built a rpm for SciLab V 6.0.1 for Centos 7.5 and installed it hoping that it would 
be more usable with my 4K display than V 5.5.2 and it is somewhat more usable than V 
5.5.2, but many of the fonts and icons are still way too small and many of the windows 
truncate the rows, making the text challenging to read.  
    I then ported the backdoor module for SciLab V 6.0.1 and I tried to build it, but I am

unable to do so because I think I require atomsCC to do so, but I am unable to download 
the source code for it because I do not have the required permissions. 
    How do I upload the port that I performed in order to use the Atoms automated build 
toolchain, or how do I build the port that I performed and then upload the built atom? 
    How may I obtain access to a beta build for the next version of SciLab to test if it 
is more usable with a 4K display than V 6.0.1?
    Thank you in advance for your reply.
Leave a comment
You must register and log in before leaving a comment.
Email notifications
Send me email when this toolbox has changes, new files or a new release.
You must register and log in before setting up notifications.