Messages

31

Support Questions / Re: VLINX MESR911 ModBus TCP to Modbus Serial Converter to Badger M-5000

« on: August 19, 2013, 06:36:53 PM »

Thank you so much for your answer.  As far as I can tell, the ONLY thing that works is "40001", but I work with wireshark all the time and will definitely do as you advise to see what happens. 

Would you help clarify with would be contained in Address.Substring(1)?  Say for example values "30541" and "40001" placed in to PLCADDRESSVALUE?

32

Support Questions / VLINX MESR911 ModBus TCP to Modbus Serial Converter to Badger M-5000

« on: August 18, 2013, 11:48:30 PM »

I'm using Advanced HMI's ModbusTCP driver (v341) to connect to a VLINK MESR911 Module which in turn is connected RS-232 to a Badger M-5000 flow meter.  (The purpose of the MESR911 is to convert Modbus TCP to Modbus Serial.)

Software supplied by Badger running on my laptop is able to read the M-5000 when connected directly to the M-5000 with the serial cable.

However, depending on what address I attempt to read, I get "Illegal Modbus Function" or "Invalid Modbus Address" errors when using the AdvancedHMI ModbusTCP driver connected to the MESR911.

I want to read the following Modbus address: 30541.  When I do, I get Invalid Modbus Address displayed in the advancedhmi control.  As I mentioned, attempted reads of other addresses will return Illegal Modbus Function or Invalid Modbus Address. 

I have found through experimentation that I can read modbus address "40001" successfully.  Well, at least AdvancedHMI controls display a "2" when I read that address instead of an error. 

I've done lots and lots of trouble shooting.  The config for the MESR911 is very simple and I've been through it all making changes just to see what would happen.  Any deviation from what I think should be the proper config yields COMM ERRORS or similar AdvancedHMI type responses.  I've changed the Modbus UnitID in the M-5000 and have witnessed AdvancedHMI complain about that.  Changing the unitid value in the ModbusTCP driver to match the meter setting corrects the problem.  So I feel that I'm getting through to the Meter using AdvancedHMI.

The address 40001 that I believe that I'm able to read is a UINT 16.  The value that I want to read is a FLOAT32 at address 30541.  However, other UINT 16 address fail to read as well.  I don't know if being able to read 40001 is significant and if I'm having an offset issue, though I can't read any 30001 or 10001 or 00001 addresses.

I noticed that the AdvancedHMI modbusTCP driver is described as Alpha software at this time.  I'm wondering if the driver is causing the problem or if it's something that I'm missing or doing wrong.

Any help and advice would be appreciated. 

33

Feature Request / Re: Request the ability to specify port in TCP Comm Control

« on: August 18, 2013, 10:27:02 PM »

Archie,

Thank you so much for following up and providing us with the ability to specify the TCP Port in the EthernetIPforCLXCom driver.

Unfortunately, and it's completely my fault, I was not specific as to which Ethernet comm driver I was using.  And even when you were very specific in your response as to which driver you would update, I missed it anyway. 

So, if it is agreeable to you, would you mind please adding the ability to specify the TCP port in the EthernetIPforPLCSLCMicroCom driver?

Thank you again for all that you do with this great project.

34

Support Questions / Re: C++ builder

« on: August 16, 2013, 10:23:44 PM »

I have been a Borland fan from way way way back.  I cut my teeth on Turbo C, Turbo Pascal, and then Turbo C++.  I resisted going to Microsoft's IDE for a long time, but I must tell you that they got this part right.  Go ahead and make the switch over to .net and Visual Studio (even express) and you will won't be sorry. There is so much more available to you once you make the switch.

come to the dark side....   

35

Feature Request / Re: Request the ability to specify port in TCP Comm Control

« on: August 08, 2013, 10:40:16 PM »

thank you so much!   

36

Feature Request / Request the ability to specify port in TCP Comm Control

« on: August 04, 2013, 11:16:18 PM »

I have a need to access via the Ethernet TCP drive a PLC on a port other than the fixed port 0xAF12 that is hard coded in the Data Link Layer.  I respectfully request the ability to specify the port value in the comm control properties or via a set property method.  Thank you!

37

Support Questions / Re: Can I specify port in Ethernet Comm Control?

« on: August 01, 2013, 04:49:57 PM »

That's unfortunate.  I'm involved in a very common scenario (I feel).  I'm surprised this hasn't come up before.

We have PLCS running behind cellular modems in vending machines located in remote rural areas.   Port forwarding is used to translate incoming requests to the cellular modem's public IP to a private non routable IP on the LAN side network. 

We recently added a second vending machine at one of the remote sites.  We want both machines serviced from the same cellular modem.  Therefore, due to the way port forwarding works, we need to connect to another port other than the standard 44818 to signify to the modem's router that the traffic needs to be routed internally to another IP/PLC.

38

Support Questions / Re: Can I specify port in Ethernet Comm Control?

« on: August 01, 2013, 04:36:34 PM »

Hi Archie, 

Thanks for the quick response!  So by fixed, are you saying that it can't be changed somehow in AdvancedHMI? 

39

Support Questions / Can I specify port in Ethernet Comm Control?

« on: August 01, 2013, 02:44:03 PM »

Hi, is it possible to specify the port number that an ethernet comm control uses when connecting to a PLC?

I looked at the control, but couldn't see how to do this.  I tried adding ":" and the alternate port to the end of the IP address and that did not work.

Thanks!