--> atomsInstall("modbus")
Module to read and write data on Modbus protocol
Upload date : 2012-12-03 14:00:53 MD5 : a134c9721d5a3b18db617e005922f85d SHA1 : b7132c35e104668c801e9a38d422ff00dda9ecee Downloads : 676 File list
Linux 32-bit Automatically generated by the ATOMS compilation chain
Upload date : 2012-12-03 14:03:33 MD5 : 1801da891d27a0f45e930fc896a87042 SHA1 : b7de81a7777e071d13b40d0660d703a0b94bc17e Downloads : 835 File list
Windows 32-bit Automatically generated by the ATOMS compilation chain
Upload date : 2012-12-03 14:03:50 MD5 : 942a6facc1fdf398cbab9705f9034524 SHA1 : 37ade6174920320e2fa6906c01c8604339416567 Downloads : 1550 File list
Windows 64-bit Automatically generated by the ATOMS compilation chain
Upload date : 2012-12-03 14:03:42 MD5 : d1ddb4b4c52d2c7334d3c5edc561a62b SHA1 : 3a945d9bee082e025f8e1745d48e085e8ae69a71 Downloads : 2656 File list
Linux 64-bit Automatically generated by the ATOMS compilation chain
Upload date : 2012-12-03 14:03:28 MD5 : 1d94924d83038cd16e2295de6a0e28fa SHA1 : c3bdff9f41f03413019e6809bf37c7fe90f32cb5 Downloads : 1441 File list
Windows version (x64) Automatically generated by the ATOMS compilation chain
Upload date : 2016-06-22 17:35:15 MD5 : 1e63caea757588c6df869a4b438f54d8 SHA1 : 98f4d5cd53ecc4abe70d3341bed4f099d1461484 Downloads : 2659
Linux version (i686) Automatically generated by the ATOMS compilation chain
Upload date : 2016-06-22 17:35:13 MD5 : c21e0591e5210f31217adf7b510a6029 SHA1 : b0d5fcf54577a75282668d4e6e50d9541f8ff845 Downloads : 437
Windows version (i686) Automatically generated by the ATOMS compilation chain
Upload date : 2016-06-22 17:35:16 MD5 : 8c2d9cee95966a94946eafde4ae36f8c SHA1 : e9985c4aef1329e0d1cd091d6a4739a1c49d184b Downloads : 392
Linux version (x86_64) Automatically generated by the ATOMS compilation chain
Upload date : 2016-06-22 17:35:12 MD5 : f6604c55825c7fb47a9273508f30a73a SHA1 : 4e9062c0fa4ef76344203d7efaeb8d48804c4df8 Downloads : 2837
some samples of code related to reading transactions available on request.
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.
Thanks to add me as author !!!