|
PvdM
|
Friday 24 September 2004 3:28:20 am |
|
|
MVI56-MCM preset multiple registers
The MVI56-MCM is used as slave (standard / no pass through).
function code 16 is not working, functioncode 6 is
incoming modbus messages with functioncode 6 ( preset single register) result in changing value in internal database (and tag MCM.ReadData[200]
but
incomming messages with functioncode 16 (preset multiple registers) trying to preset 2 registers DON'T CHANGE
MCM.ReadData[200] and MCM.ReadData[201]
Has anyone seen this before ?
|
|
CH
|
Friday 24 September 2004 8:11:32 am |
|
|
RE:MVI56-MCM preset multiple registers
PvdM,
The best way to troubleshoot the problem is to connect to the Debug/CFG port at 57600,8,N,1 and select option "A" to use the Data Analyzer. This will show the Modbus traffic. Anytime you connect to the debug port, you can press "?" to show your available menu options.
When viewing the Modbus traffic, and you're unsure as to what to look for, please feel free to post the Modbus traffic in this thread.
- CH
|
|
mtracy
|
Friday 24 September 2004 8:43:58 am |
|
|
RE:MVI56-MCM preset multiple registers
This may be a timing issue. There are parameters in Port1Aux controller tag labeled UseGuardBand and GuardBandTime.
Try setting UseGuardBand to 1, and GuardBandTime to 10. Warm boot the module after making these changes.
|
|
PvdM
|
Friday 08 October 2004 6:25:42 am |
|
|
RE:MVI56-MCM preset multiple registers
We tried different card with different software revision (1.12)
NO PROBLEMS.
Problem arised with software revision 1.21
It seems that problem disappears when dataanalyser is active.
Problem appears again with dataanalyser switched off.
????????????????????????????????????
|
|
CH
|
Friday 08 October 2004 6:43:06 pm |
|
|
RE:MVI56-MCM preset multiple registers
PvdM,
Using Mtracy's recommendation above (regarding guardband) will fix you right up.
- CH
|
|
PvdM
|
Monday 11 October 2004 1:28:40 am |
|
|
RE:MVI56-MCM preset multiple registers
At first I didn't find the mentioned parameters, since i was using the basic example program. After i did steal the relevant parts from the advanced example and set the parameters it worked.
Thanks a lot for your help
This still leaves me curious. I was using the card the most simple way as slave, single point to point connection, basic example program, do i have just bad luck with hardware, or is this an known problem ??
|
|
PvdM
|
Friday 15 October 2004 10:02:09 am |
|
|
RE:MVI56-MCM preset multiple registers
Does it mean i have to change the programs for locations that have no problems to be prepared for future swap of MVI56-MCM cards ????
Is it safe to do this when the communication doesn't give any problems at the other locations??
The end-user of the systems is getting really worried.
please advise....
|
|
CH
|
Friday 15 October 2004 10:42:21 am |
|
|
RE:MVI56-MCM preset multiple registers
PvdM,
The GuardBand is used when the module is setup as a slave, and the master is issuing multiple register writes. This is why you were only seeing timeouts when you were issuing MB FC 16, 15.
This will not effect the normal operation of the module, and is nothing to worry about.
- CH
|
|
PvdM
|
Monday 18 October 2004 7:06:43 am |
|
|
RE:MVI56-MCM preset multiple registers
I am sorry, I think i haven't been clear enough.
I hope your are not getting sick of me by now.
I'm gratefull for your help.
We have MCM cards now that are processing the MB FC16 without any problems with NO guardband set.
Can i set the guardband for this cards as well without problems.
Customer wants to make sure that when he has to swap his OK card with a BAD card ( as he calls it) the system still processes his MB FC 16. So he asks me to use guardband for all cards.
I just want to make sure that his OK cards will still be OK after using the guardband.
Peter
|
|
jsanders
|
Tuesday 10 May 2005 11:58:18 pm |
|
|
RE:MVI56-MCM preset multiple registers
Peter,
If all the MVI56-MCM modules have firmware revisions new enough to support the Guardband function, then you could enable the Guardband on them all, even the ones that really don't need it right now, without any ill effects. Before adding Guardband logic and trying to use Guardband, be sure your module firmware is Version 1.06 or higher. You can check this through the Debug Port with Hyperterminal.
|
