using modbustcpcom. struggling to understand the plcaddress properties - click, text, value, visibility. specifically, i am trying implement a selector switch. have only filled in the value and changed to toggle (latched switch i presume). when running in debug the switch acts as momentary and no results, no errors.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There is a known bug in the ModbusTCP driver that is in one of the DLL files that causes problems when writing to higher addresses. What address are you using? Do you have the same address in PLCAddressValue and PLCAddressClick? Also set the OutputType to Toggle.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2012-03-23
wow I wish I had known that when I posted my problems using modbus TCP several weeks ago… that explains why I was having troubles.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It was more along the lines of not being able to address 6000 area registers, and also not able to control to the bit level only word level for some reason
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
the comment about the last three digits being less than 255 fits with what i am experiencing.
it does not appear that you are using the bug tracking feature in sourceforge. is there some other way to get a bug list, especially those related to modbustcpcom? i understand that modbustcpcom is beta and we are getting what we paid for, but sharing where the known bear traps are so that we could avoid them would sure make things less painful. Thanks, and i do appreciate the work that you have done. This is very solid work for basic applications.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We don't use the bug tracking feature because only a very small percentage of our support goes through sourceforge. We use an internal system and report relevant bugs directly to customers on the priority support list.
The update is still not due to be released for another 2 weeks, so if you private message me an email address, I can send you a patch that fixes the modbus driver.
The driver does not have support for 6 series addresses. Do you know what function code would be used for that address range?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
sounds good. will wait for the update. canaanp was the user who was having trouble with the 6000 series addresses and i have no solutions for him. thanks again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2012-03-23
The 6000 registers are for "shared" variables. I did find a way to start using 4000 instead, but I could only control values at the word level, not bit level. I could not figure out a way to manipulate individual bits.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
using modbustcpcom. struggling to understand the plcaddress properties - click, text, value, visibility. specifically, i am trying implement a selector switch. have only filled in the value and changed to toggle (latched switch i presume). when running in debug the switch acts as momentary and no results, no errors.
There is a known bug in the ModbusTCP driver that is in one of the DLL files that causes problems when writing to higher addresses. What address are you using? Do you have the same address in PLCAddressValue and PLCAddressClick? Also set the OutputType to Toggle.
wow I wish I had known that when I posted my problems using modbus TCP several weeks ago… that explains why I was having troubles.
I think the problem occurs when trying to write to an address with the last 3 digits being higher than 255.
Well, here's my other post where I was having troubles…
http://sourceforge.net/projects/advancedhmi/forums/forum/875091/topic/5002292
It was more along the lines of not being able to address 6000 area registers, and also not able to control to the bit level only word level for some reason
the comment about the last three digits being less than 255 fits with what i am experiencing.
it does not appear that you are using the bug tracking feature in sourceforge. is there some other way to get a bug list, especially those related to modbustcpcom? i understand that modbustcpcom is beta and we are getting what we paid for, but sharing where the known bear traps are so that we could avoid them would sure make things less painful. Thanks, and i do appreciate the work that you have done. This is very solid work for basic applications.
We don't use the bug tracking feature because only a very small percentage of our support goes through sourceforge. We use an internal system and report relevant bugs directly to customers on the priority support list.
The update is still not due to be released for another 2 weeks, so if you private message me an email address, I can send you a patch that fixes the modbus driver.
The driver does not have support for 6 series addresses. Do you know what function code would be used for that address range?
sounds good. will wait for the update. canaanp was the user who was having trouble with the 6000 series addresses and i have no solutions for him. thanks again.
The 6000 registers are for "shared" variables. I did find a way to start using 4000 instead, but I could only control values at the word level, not bit level. I could not figure out a way to manipulate individual bits.