This object is in archive!
Connection of ModBus/eBus devices
Answered
What's the situation with ModBus/eBus devices? Are they supported? Via what interface? If not now, will they be in the near future?
The same question
No connection
Real-time notifications may not work
Please let me know if the Serial Modul is compatible with Modbus devices. How we can write and read in a modbus register ?
Please let me know if the Serial Modul is compatible with Modbus devices. How we can write and read in a modbus register ?
I noticed that there is now a ModBus entry in the new device dialog. I don't know anything more than that!
I noticed that there is now a ModBus entry in the new device dialog. I don't know anything more than that!
Noticed in 1.0.13 that when adding a MODBUS device you get a little bit further into the process than before. Although not being able to add a device yet it seems that the developers have written aanother little bit of code....
Can we, please, get a statement from Zipato about what are the thinking about the MODBUS implementation
BR
Noticed in 1.0.13 that when adding a MODBUS device you get a little bit further into the process than before. Although not being able to add a device yet it seems that the developers have written aanother little bit of code....
Can we, please, get a statement from Zipato about what are the thinking about the MODBUS implementation
BR
Modbus TCP IP will be available very soon. It is one of the priorities now. The implementation has already been done and the only thing still to be done is that user can activate Modbus network creation and discovery start for the devices through UI.
You will soon be able to do what I wrote, but when that will be possible, if you will want your device to be supported, you will have to submit a support ticket with information about your device (the registers it has, the info about supported register values and how to format them if needed). This process shouldn't take long in most of the cases.
Modbus TCP IP will be available very soon. It is one of the priorities now. The implementation has already been done and the only thing still to be done is that user can activate Modbus network creation and discovery start for the devices through UI.
You will soon be able to do what I wrote, but when that will be possible, if you will want your device to be supported, you will have to submit a support ticket with information about your device (the registers it has, the info about supported register values and how to format them if needed). This process shouldn't take long in most of the cases.
Dear Mr Cerovski,
This is excellent news !! I have about 5 different types of Advantech ADAM-6000 modules and the documentation to support them is very good but unfortunatley I don't have the skills to program my self....
I will be happy to test the beta software for these modules (only).
Best regards
Torbjorn Hall
Dear Mr Cerovski,
This is excellent news !! I have about 5 different types of Advantech ADAM-6000 modules and the documentation to support them is very good but unfortunatley I don't have the skills to program my self....
I will be happy to test the beta software for these modules (only).
Best regards
Torbjorn Hall
Dear Mr Cerovski,
are you have some news about Modbus implementation to production?
Thank you.
Dear Mr Cerovski,
are you have some news about Modbus implementation to production?
Thank you.
It seems to be pretty well advanced. Open a ticket to ask about support for your particular device. I asked about a Brink Renovent ventilation unit and it looks as if it will work if I connect it up. Watch this space.
It seems to be pretty well advanced. Open a ticket to ask about support for your particular device. I asked about a Brink Renovent ventilation unit and it looks as if it will work if I connect it up. Watch this space.
The basic implementation has been done and it was tested on one device so far, CoolMasterNet controller. I am interested if there will be problems with Brink.
Basically, Modbus devices should work with Zipabox, but you need to provide info about device's registers as David did. I need those data to write device descriptors (and possibly some FW changes) to support your devices
The basic implementation has been done and it was tested on one device so far, CoolMasterNet controller. I am interested if there will be problems with Brink.
Basically, Modbus devices should work with Zipabox, but you need to provide info about device's registers as David did. I need those data to write device descriptors (and possibly some FW changes) to support your devices
Thank you so match. I use this devices for 220v equipment. It is very good & right cost (about 100euro per unit in Russia). http://contactless.ru/wiki/index.php/WB-MR14_%D0%BC%D0%BE%D0%B4%D1%83%D0%BB%D1%8C_%D1%80%D0%B5%D0%BB%D0%B5_14-%D1%82%D0%B8_%D0%BA%D0%B0%D0%BD%D0%B0%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9
So, it will be great, if you can add this device to support via Modbus. In my construction I have 6 units, and they are working thru this http://novatek-electro.com/eu/produkciya/protocol-converter/protocol-converter-et-485.html in tcp infrastructure.
Unfortunately, 1st one (WB-MR14) have no documentation on English (only Russian). Is it problem for you? Or I can try to translate myself, but I am not sure in my English :)
So, in my house now I am in process of installation of Zipabox +443 mhz+ 2 Security modules + Power Module & Zipatile in each room ( total 7). Concept is all 220v equipment works thru wb-mr14, all sensors, thermostats, conditions & other control via Z-wave.
Help)))))
Thank you!!!
Thank you so match. I use this devices for 220v equipment. It is very good & right cost (about 100euro per unit in Russia). http://contactless.ru/wiki/index.php/WB-MR14_%D0%BC%D0%BE%D0%B4%D1%83%D0%BB%D1%8C_%D1%80%D0%B5%D0%BB%D0%B5_14-%D1%82%D0%B8_%D0%BA%D0%B0%D0%BD%D0%B0%D0%BB%D1%8C%D0%BD%D1%8B%D0%B9
So, it will be great, if you can add this device to support via Modbus. In my construction I have 6 units, and they are working thru this http://novatek-electro.com/eu/produkciya/protocol-converter/protocol-converter-et-485.html in tcp infrastructure.
Unfortunately, 1st one (WB-MR14) have no documentation on English (only Russian). Is it problem for you? Or I can try to translate myself, but I am not sure in my English :)
So, in my house now I am in process of installation of Zipabox +443 mhz+ 2 Security modules + Power Module & Zipatile in each room ( total 7). Concept is all 220v equipment works thru wb-mr14, all sensors, thermostats, conditions & other control via Z-wave.
Help)))))
Thank you!!!
On the first look, if I am not mistaking, you are talking about Modbus RTU devices, right?
If it is so, unfortunately, for now we support only Modbus TCP IP communication.
On the first look, if I am not mistaking, you are talking about Modbus RTU devices, right?
If it is so, unfortunately, for now we support only Modbus TCP IP communication.
Yes, I am talking about Modbus RTU. But 2nd device, that I attached, convert RS-485 Modbus RTU to Modbus TCP IP :) I tested it, it works fine! So, if you can implement support wb-mr14 on level registers & commands, other is my headache)))
Yes, I am talking about Modbus RTU. But 2nd device, that I attached, convert RS-485 Modbus RTU to Modbus TCP IP :) I tested it, it works fine! So, if you can implement support wb-mr14 on level registers & commands, other is my headache)))
Then I might do that. Just tell me which Modbus registers do you need/plan to use?
I doubt you will want to use all of them or...?
Then I might do that. Just tell me which Modbus registers do you need/plan to use?
I doubt you will want to use all of them or...?
I also plan to buy a ModBus RTU to ModBus IP adapter, so I'd be interested to hear if it works with the Zipabox.
I also plan to buy a ModBus RTU to ModBus IP adapter, so I'd be interested to hear if it works with the Zipabox.
So, its excellent news!!!! So please add support on those registers:
0-13 coil RW - 1 or 0status relay 1-14 0-13 discrete R - status input 1-14 5 holding RW 0 : nonlocking key1: stick-type button
3: disable control
buttons mode for all channels (not good idea:) 9-22 holding RW 0 : nonlocking key
1: stick-type button
3: disable control
Input N mode. In register 5 must be null. in this case each input can be programme independiatly.
So, its excellent news!!!! So please add support on those registers:
0-13 coil RW - 1 or 0status relay 1-14 0-13 discrete R - status input 1-14 5 holding RW 0 : nonlocking key1: stick-type button
3: disable control
buttons mode for all channels (not good idea:) 9-22 holding RW 0 : nonlocking key
1: stick-type button
3: disable control
Input N mode. In register 5 must be null. in this case each input can be programme independiatly.
Sorry, table insert is unreadable. I'll repeat in correct format.
Sorry, table insert is unreadable. I'll repeat in correct format.
So, only registers in attached file.
Change of address is broadcast (slave_id 0) team record (WRITE_SINGLE_REGISTER) to holding register address 128 (0x80). At 200 is a signature of 6 bytes. The signature is unique to each model and allows to identify the model. To obtain the signatures necessary to fulfill READ_HOLDING_REGISTERS address 200 length 6. Entry into this area of memory is not supported when attempts to write to an invalid location error is returned 3. The value of each relay is stored in the COIL. From the 1st relay address 0, 2nd - 1.
So, only registers in attached file.
Change of address is broadcast (slave_id 0) team record (WRITE_SINGLE_REGISTER) to holding register address 128 (0x80). At 200 is a signature of 6 bytes. The signature is unique to each model and allows to identify the model. To obtain the signatures necessary to fulfill READ_HOLDING_REGISTERS address 200 length 6. Entry into this area of memory is not supported when attempts to write to an invalid location error is returned 3. The value of each relay is stored in the COIL. From the 1st relay address 0, 2nd - 1.
Dear Mr Cerovski,
So, at last the MODBUS is start moving.....glad to see!
I'm using the Advantech ADAM 6000-series TCP IP modules.
As a start, I would like to see the implementation of the ADAM 6015 module (7 temp senors)
See attached documentation for the total series but for now I would only like to read the actual values from the ADAM 6015's 7 registers :
Address (4X) Channel Description Attribute
40001 0AI ValueRead
40002 1AI ValueRead
40003 2AI ValueRead
40004 3AI ValueRead
40005 4AI ValueRead
40006 5AI ValueRead
40007 6AI ValueRead
I think the registers are read out in 16 bit value but I could do decoding with some operators as long as the value is between 0-65535....
Is this possible?
Best regards
Torbjorn
Dear Mr Cerovski,
So, at last the MODBUS is start moving.....glad to see!
I'm using the Advantech ADAM 6000-series TCP IP modules.
As a start, I would like to see the implementation of the ADAM 6015 module (7 temp senors)
See attached documentation for the total series but for now I would only like to read the actual values from the ADAM 6015's 7 registers :
Address (4X) Channel Description Attribute
40001 0AI ValueRead
40002 1AI ValueRead
40003 2AI ValueRead
40004 3AI ValueRead
40005 4AI ValueRead
40006 5AI ValueRead
40007 6AI ValueRead
I think the registers are read out in 16 bit value but I could do decoding with some operators as long as the value is between 0-65535....
Is this possible?
Best regards
Torbjorn
I think it is possible. I might even do it tomorrow. If not, then by mid next week. As you know, probably the problem might be to properly format the read value, if it is not stated in the documentation (haven't checked yet)-
I think it is possible. I might even do it tomorrow. If not, then by mid next week. As you know, probably the problem might be to properly format the read value, if it is not stated in the documentation (haven't checked yet)-
Vladimir and Torbjorn,
I need to update your Zipabox with adjustments I made for your devices. Therefor, please send me your boxes SN at zcerovski@3plus.hr.
Then I will explain to each one of you how to add your devices to the box and test if they work.
Vladimir and Torbjorn,
I need to update your Zipabox with adjustments I made for your devices. Therefor, please send me your boxes SN at zcerovski@3plus.hr.
Then I will explain to each one of you how to add your devices to the box and test if they work.
My SolarEdge inverter supports modbus IP, via the (universal?) definition of sunspec:
http://www.solaredge.com/sites/default/files/sunspec-implementation-technical-note.pdf
So how would I configure this? I thought to add a modbus device (meter) but the address of 40206 (RealPower) is not accepted: "The maximum value for this field is 9998"
My SolarEdge inverter supports modbus IP, via the (universal?) definition of sunspec:
http://www.solaredge.com/sites/default/files/sunspec-implementation-technical-note.pdf
So how would I configure this? I thought to add a modbus device (meter) but the address of 40206 (RealPower) is not accepted: "The maximum value for this field is 9998"
You probably should enter only 206, but it still won't work since your device is not supported.
open a support ticket with some documentation attached and write which registers you want to use and we will see what can be done remotely
You probably should enter only 206, but it still won't work since your device is not supported.
open a support ticket with some documentation attached and write which registers you want to use and we will see what can be done remotely
How can we add coolmasternet ? it needs IP adress ,port and aircondition adress. Is that port number 10102 ?
How can we add coolmasternet ? it needs IP adress ,port and aircondition adress. Is that port number 10102 ?
I checked CoolMasterNet's ModBus documentation and I don't understand it.
http://coolautomation.com/lib/doc/manual/Modbus-guidelines.pdf
It connects via ModBus IP but apparently you need to get out your hex calculator to figure out what the registers are. Perhaps someone else has already done this and could help out.
I checked CoolMasterNet's ModBus documentation and I don't understand it.
http://coolautomation.com/lib/doc/manual/Modbus-guidelines.pdf
It connects via ModBus IP but apparently you need to get out your hex calculator to figure out what the registers are. Perhaps someone else has already done this and could help out.
First ad all, you need no calculator.
All you need is to telnet to CoolMaster, type modbus IP enable. and type vs auto.
If all is connected properly, after CoolMaster restart you are ready. In discovery with Zipabox, you enter for Name CoolMasterNet, you enter device's IP and port, and for AddressNumber you enter the output of va auto - 1. That is all.
If you need any assistance, contact our support.
Zeljko
First ad all, you need no calculator.
All you need is to telnet to CoolMaster, type modbus IP enable. and type vs auto.
If all is connected properly, after CoolMaster restart you are ready. In discovery with Zipabox, you enter for Name CoolMasterNet, you enter device's IP and port, and for AddressNumber you enter the output of va auto - 1. That is all.
If you need any assistance, contact our support.
Zeljko
Ahh ok. Thanks!
Ahh ok. Thanks!
A ModBus question: where is the slave address configured in a Zipabox ModBus device? As I understand it, it's possible to have more than one slave connected to a single ModBus TCP adapter (with a single IP address). If so, how do the commands go to the correct slave? In a request, the slave address is set at byte 6, according to this:
http://www.rtaautomation.com/technologies/modbus-tcpip/
A ModBus question: where is the slave address configured in a Zipabox ModBus device? As I understand it, it's possible to have more than one slave connected to a single ModBus TCP adapter (with a single IP address). If so, how do the commands go to the correct slave? In a request, the slave address is set at byte 6, according to this:
http://www.rtaautomation.com/technologies/modbus-tcpip/
Hi,
just saw that Modbus is support by Zipato.
I would like to include my Fronius Symo photovoltaik inverter into Zipato. But it´s not in the list.
Can I include the device with "General Modbus IP Device" ?
Hi,
just saw that Modbus is support by Zipato.
I would like to include my Fronius Symo photovoltaik inverter into Zipato. But it´s not in the list.
Can I include the device with "General Modbus IP Device" ?
Replies have been locked on this page!