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

Modbus

(3920/3920 downloads)
Modbus Interface
Details
Version
1.0-7
Author(s)
antoine.elias@scilab-enterprises.com
bruno.jofret@scilab-enterprises.com
Allan CORNET
Entity
Scilab Enterprises
Package maintainers
Antoine Elias
Bruno Jofret
Categories
License
Supported Scilab Versions
>= 5.4
Creation Date
24th of October 2012
ATOMS packaging system
Available on
How To Install
atomsInstall('modbus')
Description
Module to read and write data on Modbus protocole
Files (5)
[463.83 Ko] modbus_1.0-7.bin.x86_64.linux.tar.gz
Linux version (x86_64)
Automatically generated by the ATOMS compilation chain

[459.41 Ko] modbus_1.0-7.bin.i686.linux.tar.gz
Linux version (i686)
Automatically generated by the ATOMS compilation chain

[503.77 Ko] modbus_1.0-7.bin.x64.windows.zip
Windows version (x64)
Automatically generated by the ATOMS compilation chain

[502.06 Ko] modbus_1.0-7.bin.windows.zip
Windows version (i686)
Automatically generated by the ATOMS compilation chain

News (0)
Comments (2)
    Leave a comment 
Comment from Allan Cornet -- 9th of July 2013, 11:20:23 AM    
Thanks to add me as author !!!
Comment from Mark Dresser -- 17th of January 2015, 10:56:57 PM    
I'm trying to understand how this library is handling the write single register function 
(Modbus FC06).

As far as I can tell, modbus_writeReg is actually calling modbus_writeRegs without a 
register count, which I don't understand.  The details of parameter passing between 
Scilab and c libraries are a little beyond me so this may be OK.  If it was calling 
modbus_writeRegs with a register count of 1 it would be logically equivalent to 
modbus_writeReg but using Modbus FC16.

The reason for my interest is that I am dealing with an instrument (Honeywell UDC2500) 
that refuses FC16 with a count of 1 for writing a single register.  It works with FC06-- 
not very logical but when your name is Honeywell, you can pretty much do what you like 
and who can argue!

The other thing I noted is that the modbus_writeReg example code in the help 
documentation calls modbus_readReg function which doesn't seem to exist.

I have high hopes for this library to be a big help in the kind of work I am doing but 
figuring out the details to get going has got me puzzled.

Any advice would be welcome.
Leave a comment
You need to log in before you can leave a comment.