Messages

1

Feature Request / Re: MELSEC Drivers ? FX series PLC's

« on: January 16, 2015, 10:02:08 AM »

Mitsubishi FX PLC's don't have a modbus port !

They have an RS 422 connector that is for programming , using MELSEC protocol.

If modbus is required it is an expensive add on board.

I have been down tis road many times.

2

Feature Request / MELSEC Drivers ? FX series PLC's

« on: November 17, 2014, 11:28:57 PM »

Hi Archie

It would be awesome if you created Mitsubishi FX drivers, as there PLC's are cheap but Displays are crazy and poor resolution.

Thanks Heaps great product.

Greg.

3

Open Discussion / Re: Connect to MODBUS device through USB port

« on: July 13, 2014, 08:31:19 PM »

I am using the Procon X modbus gateway (cheapest and most awesome) simple to setup and works first time wit Advanced HMI.

4

Open Discussion / Re: 4 x unsigned int values joined Modbus TCP Digital Panel Meter Help Please

« on: July 13, 2014, 08:28:41 PM »

Thank You Archie

That helped heaps is there a list of modifiers or is the L the only one?

I purchased the extra packs and noticed that there was a larger LED Display that will be able to display the 4 integer long return value when it grows.

Thanks again

Great.

5

Open Discussion / 4 x unsigned int values joined Modbus TCP Digital Panel Meter Help Please

« on: June 30, 2014, 04:30:02 AM »

Can someone please help me.

I have to read in 4 registers for the value that is going into the digitalpanelmeter.
the value is hexadecimal and right justified with 2 decimal places.

It is for reading an ABB energy meter.

I can do it with BB Comtest pro but cant figure it out in Advanced HMI as I always get a 0 value.

The read address is 0x5000 (20480) so I put 420480 in the PLC Address field and 4 in resolution but no joy.

The meter registers (420480 = 0x0000, 420481 = 0x0000, 420482 = 0x0003, 42083 = 0xFF57) = 2619.75 KwHrs (Decimal)



Please see attachment for data description.

6

Support Questions / Re: Modbus TCP

« on: June 05, 2014, 03:17:29 AM »

I just got home and tried the above and it returned INVALID VALUE RETURNED "Illegal modbus function".
So I I guess that is not the answer.

7

Support Questions / Re: Modbus TCP

« on: June 04, 2014, 11:55:03 PM »

Would I be correct if I assumed that the PLC address field should contain 320480 to read holding register 0x5000 (20480 dec) ?

I am also assuming that the unit id on the ModbusTcpCom is the remote device ID (like rtu/485).
so does this mean that for every device on  the 485 bus via the transparent converter a separate instance of ModbusTcpCom would need to be created.

Cheers.

8

Support Questions / Modbus TCP

« on: June 04, 2014, 06:25:20 AM »

Hi Archie
I am a total newbie and just getting my head around this stuff.
I have been using a modbus client (comtest pro from baseblock, awesome) and I can read the meter by setting it to unit address 1, function 3 and read address 0x5000 and it returns a bundle of numbers representing the current energy consumed in kWh.

In advanced HMI I have set the modbus connector to the IP address  192.x.x.x, unit id 1 but I dont know what to put in the PLCaddressxxx fields on the meter objects and the like.

I am enjoying the learning process, though I feel pretty dumb at present.
A modbus video would be awesome..

Thanks.