Canderson_DPI (Customer) asked a question.
Badger M2000 flow meter messaging.
Has anyone messaged data from a Badger m2000 flow meter? I feel like I am close, using my receive message instruction goes from receiving to error with no error code displayed. I have triple checked my ip's subnet and gateway. I am using port 502 on both the message instruction and the meter. I upped the timeout setting on both to be sure it had enough time. Any help would be great as im sure I am just missing something simple. I can ping the meter.
Thanks
Which PLC are you using?
Also, are you using Modbus RTU (serial) or the optional Modbus TCP on that meter?
I am using a Click c0-10DRE-D with C0-08NE3, and two C0-04AD-1 expansion cards. I am using Modbus TCP on the meter.
I have done this on two sites, one with a Click and one with a Micrologix 1400, but with Modbus RTU, not TCP.
In general, I would recommend reading one value first to prove all your settings are right. In the ML1400 code, I have the first value at Holding Register 40212 commented as the MSW of a float, so read two words if you start at holding register 212 (1 based addressing) and the destination is a DS register.
Looking at my old Click program, I am reading the float values one by one directly into DF registers with word swap turned on. I normally don't do things that way, but it would be a good way to start and prove your communication details are right. I'm not 100% certain that one was an M2000 model since that was around ten years ago. I may have not cared about any of the integer words on that project... normally I read everything I can and use what I need, but gather it all.
In the more recent ML1400 program (which I know is connected to two M2000 badger meters) I am reading 32 holding registers from each starting at 40212 (1-based addressing) into integer locations, then doing a word swap on the relevant floats.
Here's a screenshot from the Click program (I used Hex addressing, so it's zero based).
A few months ago, I encountered this exact issue and spent several weeks working with tech support from both AD and Badger. Ultimately, I abandoned the Click and swapped it for a P1000, which functioned immediately and has run without any problems since then. The only caveat was having to configure multiple read messages to accommodate gaps in the Modbus register.