Support Forums
Multifunction energy meter connection using RS485

Dear all,

I need to connect several Multi function Energy meter to DT85 using RS485.
I have never worked before with modbus /serial communication.

I checked manual and says need to set profile etc. But silly question, where do i put this code ? as i have always used deX for making program so it was pretty straight forward.

Should i use Detransfer to put command or can it be done via deX ??

Your help is much appreciated.

Regards,
Nik

Dear all, I need to connect several Multi function Energy meter to DT85 using RS485. I have never worked before with modbus /serial communication. I checked manual and says need to set profile etc. But silly question, where do i put this code ? as i have always used deX for making program so it was pretty straight forward. Should i use Detransfer to put command or can it be done via deX ?? Your help is much appreciated. Regards, Nik

Hi Nik,

Profile setting is located at the top of configuration tree where you find dataTaker model.
This configuration tree is the list of schedules/ channels on the left side of your screen when you access "Configure the Logger".

After clicking dataTaker model, please select "Serial port" from the list to access its profile setting.
You can set baudrate, data bit, parity, stop bit, function, mode and flow control through this profile setting (match the setting with sensor's).

After setting selection, you can start writing MODBUS syntax using manual channel.

Best regards,
Rudy Gunawan

Hi Nik, Profile setting is located at the top of configuration tree where you find dataTaker model. This configuration tree is the list of schedules/ channels on the left side of your screen when you access "Configure the Logger". After clicking dataTaker model, please select "Serial port" from the list to access its profile setting. You can set baudrate, data bit, parity, stop bit, function, mode and flow control through this profile setting (match the setting with sensor's). After setting selection, you can start writing MODBUS syntax using manual channel. Best regards, Rudy Gunawan

Hi Rudy,

thanks a lot for your reply. I am planning to connect 5 multi function energy meter.
Each meter gives five variables such as: Voltage, current, power , energy etc.

Should i define manual channel based on each variable or should i define based on each meter ?

sorry for my ignorance. i am have pretty zero knowledge in Modbus/ serial communication area.

If you have any sample code, can you please share with me ?

Regards,
Nik

Hi Rudy, thanks a lot for your reply. I am planning to connect 5 multi function energy meter. Each meter gives five variables such as: Voltage, current, power , energy etc. Should i define manual channel based on each variable or should i define based on each meter ? sorry for my ignorance. i am have pretty zero knowledge in Modbus/ serial communication area. If you have any sample code, can you please share with me ? Regards, Nik

Hi Nik,

You may use either way, however for future troubleshooting it might be easier to have one manual channel for one parameter (specially when those parameters are not in direct sequence).
If the MODBUS parameters are in direct sequence (i.e.: parameter 1 address 30051, parameter 2 address 30052), you may consider to perform block read/ transfer.f

Best regards,
Rudy Gunawan

Hi Nik, You may use either way, however for future troubleshooting it might be easier to have one manual channel for one parameter (specially when those parameters are not in direct sequence). If the MODBUS parameters are in direct sequence (i.e.: parameter 1 address 30051, parameter 2 address 30052), you may consider to perform block read/ transfer.f Best regards, Rudy Gunawan

Thanks Rudy,

I am getting it slowly. I have tried following command in Manual channel

1MODBUS(AD1,R4:16383,MBF,MES,"F")=1CV

However, i am getting msg on Datatakker : Not Yet not and no activity/reading on dex

I have Multifunction power meter : link for it:
https://www.accuenergy.com/files/acuvim-ii/Acuvim-II-Power-Meter-User-Manual-1040E1303.pdf

if you check on Page 244 it gives example to read data from meter via modbus.

What am i still missing? ( i have set sensor port to Modbus master: RS485, 38400 8N1 ,same on meter too) Feeling bit nervous with it.

Regards,
Nik

Thanks Rudy, I am getting it slowly. I have tried following command in Manual channel 1MODBUS(AD1,R4:16383,MBF,MES,"F")=1CV However, i am getting msg on Datatakker : Not Yet not and no activity/reading on dex I have Multifunction power meter : link for it: https://www.accuenergy.com/files/acuvim-ii/Acuvim-II-Power-Meter-User-Manual-1040E1303.pdf if you check on Page 244 it gives example to read data from meter via modbus. What am i still missing? ( i have set sensor port to Modbus master: RS485, 38400 8N1 ,same on meter too) Feeling bit nervous with it. Regards, Nik

Hi Nik,

Please check the wiring, RS485 must be connected on Tx, RTS and D Gnd pin.
If you have long wire (above 20 metres), 100 ohms termination resistor is required.

Preferably you do this troubleshooting via command interface DeTransfer since it is easier to check one line of code than the entire program at once.
Turn ON MODBUS diagnostic by sending P56=4 to the logger, check for sensor response.

Diagnostic example:
Modbus TX >SS: 11 033fff0002fabf (8)
Modbus timeout
dataTaker 80 E124 - Modbus transaction failed
1MODBUS NotYetSet
The above example indicates no connection to the sensor.

Modbus TX >SS: 01 0400a30001c1e8 (8)
Modbus RX <SS: 01 840182c0 (5)
Modbus master - slave reported exception: EX_ILLEGAL_FUNCTION = 0x01
The above example indicates target register is not avaiilable

Then if you still failed to get the reading, labelling standard might be the issue (A, B, +, -, inverting, non inverting) so please swap the wire.

Best regards,
Rudy Gunawan

Hi Nik, Please check the wiring, RS485 must be connected on Tx, RTS and D Gnd pin. If you have long wire (above 20 metres), 100 ohms termination resistor is required. Preferably you do this troubleshooting via command interface DeTransfer since it is easier to check one line of code than the entire program at once. Turn ON MODBUS diagnostic by sending P56=4 to the logger, check for sensor response. Diagnostic example: Modbus TX &gt;SS: 11 033fff0002fabf (8) Modbus timeout dataTaker 80 E124 - Modbus transaction failed 1MODBUS NotYetSet The above example indicates no connection to the sensor. Modbus TX &gt;SS: 01 0400a30001c1e8 (8) Modbus RX &lt;SS: 01 840182c0 (5) Modbus master - slave reported exception: EX_ILLEGAL_FUNCTION = 0x01 The above example indicates target register is not avaiilable Then if you still failed to get the reading, labelling standard might be the issue (A, B, +, -, inverting, non inverting) so please swap the wire. Best regards, Rudy Gunawan
29
5
2
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft