Project

General

Profile

Actions
Copy link

Task #3021

open

Task #2911: PLC MODBUS mapping from Chola on Siemens PLC

E-REMOS device configuration & Dashboard setup

Task #3021: E-REMOS device configuration & Dashboard setup

Added by Venu Krishnamurthy 4 months ago. Updated about 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Prakash M
Target version:
-
Start date:
07/01/2026
Due date:
16/01/2026 (about 4 months late)
% Done:

100%

Estimated time:
Spent time:
28:00 h

Description

E-remos device creation and signals on modbus with address and data type creation

  1. create a new device
  2. Configure the device to list all signals based on the modbus
  3. test and verify the config packet
  4. Dashboard creation with the signal list

Files

Download all files
Screenshot 2026-01-16 115036.png (159 KB) Screenshot 2026-01-16 115036.png This image shows that all Modbus parameters have been configured and connected to the dashboard. Prakash M, 16/01/2026 06:54 AM
image.png (135 KB) image.png The image has shown the config packet list with parameters. Prakash M, 16/01/2026 02:05 PM
Screenshot 2026-01-16 115036.png
image.png

Updated by VenuMadhav S 4 months ago Actions
Copy link
 #1

Venu Sir, has to check to with Prakash.

Updated by Thomas Joseph 4 months ago Actions
Copy link
 #2

Device ID: EG6270-2435-001

Updated by Prakash M 4 months ago Actions
Copy link
 #3

  • Status changed from New to In Progress
  • % Done changed from 0 to 40

A real (floating-point) data type Modbus parameter has been added to E-REMOS.
A bit-based data type parameter is pending and needs to be added.

Updated by VenuMadhav S 4 months ago Actions
Copy link
 #4

Dash board configuration has to enable based on bit type signals and alarms.

Updated by Thomas Joseph 4 months ago Actions
Copy link
 #5

  • Due date set to 16/01/2026

Due date extended to 16/01/2026

Updated by Thomas Joseph 4 months ago Actions
Copy link
 #6

  • Subject changed from E-remos device creation and signals on modbus with address and data type creation to E-REMOS device configuration & Dashboard setup
  • Description updated (diff)

Updated by Prakash M 4 months ago Actions
Copy link
 #7

  • % Done changed from 40 to 90

All Modbus parameters (real data type and alarm-based bit fields) have been added to the dashboard.

Summary:
Totally, 103 modbus parameters.

39 parameters => Non-alarm based,
64 parameters => Alarm based.

Updated by Prakash M 4 months ago Actions
Copy link
 #8

Screenshot 2026-01-16 115036.png

image for all modbus parameters.

Updated by Prakash M 4 months ago · Edited Actions
Copy link
 #9

image.png

Parameters:
19-extra parameters have been added for group and also to show the graph.

Totally,

  1. 39 Modbus parameters -> Non-Alarm based,
  2. 4 (2 * Modbus holding -combo/ Real data type) * 16(Real data)=> 64(bit) -> Alarm based.
  3. 19 parameters -> Group and Graph.

Next action plan:*

1.Modbus parameters -> Needs to be verified the data types and it's ranges.

Updated by Prakash M 3 months ago · Edited Actions
Copy link
 #10

========== CONFIG REQUEST ==========
[TX CONFIG] #2c0021000000getsignallist;EG6270_2435_001;3;4$
[DEBUG] CONFIG SENT
[DEBUG] CONFIG RESPONSE LENGTH: 2229
[RX CONFIG] [1,["EG62702435001s1;40001;T;0;fl;99","EG62702435001s2;40003;T;1;fl;99","EG62702435001s3;40005;T;2;fl;99","EG62702435001s4;40007;T;3;fl;99","EG62702435001s5;40009;T;4;fl;99","EG62702435001s6;40011;T;5;fl;99","EG62702435001s7;40013;T;6;fl;99","EG62702435001s8;40015;T;7;fl;99","EG62702435001s9;40017;T;8;fl;99","EG62702435001s10;40019;T;9;fl;99","EG62702435001s11;40021;T;10;fl;99","EG62702435001s12;40023;T;11;fl;99","EG62702435001s13;40025;T;12;fl;99","EG62702435001s14;40027;T;13;fl;99","EG62702435001s15;40029;T;14;fl;99","EG62702435001s16;40031;T;15;fl;99","EG62702435001s17;40033;T;16;fl;99","EG62702435001s18;40035;T;17;fl;99","EG62702435001s19;40037;T;18;fl;99","EG62702435001s20;40039;T;19;fl;99","EG62702435001s21;40041;T;20;fl;99","EG62702435001s22;40045;T;21;fl;99","EG62702435001s23;40049;T;22;fl;99","EG62702435001s24;40051;T;23;fl;99","EG62702435001s25;40055;T;24;fl;99","EG62702435001s26;40059;T;25;fl;99","EG62702435001s27;40057;T;26;fl;99","EG62702435001s28;40053;T;27;fl;99","EG62702435001s29;40061;T;28;fl;99","EG62702435001s30;40063;T;29;fl;99","EG62702435001s31;40065;T;30;fl;99","EG62702435001s32;40067;T;31;fl;99","EG62702435001s33;40069;T;32;fl;99","EG62702435001s34;40075;T;33;fl;99","EG62702435001s35;40077;T;34;fl;99","EG62702435001s36;40043;T;35;fl;99","EG62702435001s37;40047;T;36;fl;99","EG62702435001s38;40071;T;37;fl;99","EG62702435001s39;40073;T;38;fl;99","EG62702435001s40;40079;T;39;b;99","EG62702435001s56;40081;T;40;b;99","EG62702435001s72;40083;T;41;b;99","EG62702435001s88;40085;T;42;b;99","EG62702435001s105;40002;T;43;fl;99","EG62702435001s106;40010;T;44;fl;99","EG62702435001s107;40018;T;45;fl;99","EG62702435001s108;40020;T;46;fl;99","EG62702435001s109;40022;T;47;fl;99","EG62702435001s110;40024;T;48;fl;99","EG62702435001s111;40026;T;49;fl;99","EG62702435001s112;40028;T;50;fl;99","EG62702435001s113;40030;T;51;fl;99","EG62702435001s114;40050;T;52;fl;99","EG62702435001s115;40052;T;53;fl;99","EG62702435001s116;40060;T;54;fl;99","EG62702435001s117;40062;T;55;fl;99","EG62702435001s118;40064;T;56;fl;99","EG62702435001s119;40068;T;57;fl;99","EG62702435001s120;40072;T;58;fl;99","EG62702435001s121;40058;T;59;fl;99","EG62702435001s122;400;T;60;fl;99","EG62702435001s123;402;T;61;fl;99"]]

[INFO] TOTAL SIGNALS RECEIVED: 62

Summary:
1.Non-alarm based=> 39 -> EG62702435001s1 to EG62702435001s39

2.Alarm based => 4 (No . of Modbus holding reg) * 16(each Modbus address has 16-bit ) -> Totally, 64 bit -> EG62702435001s40,EG62702435001s56,EG62702435001s72,EG62702435001s88

3.Dummy for group to show the graph
EG62702435001s105 to EG62702435001s123

Next action Plan

1.Needs to be verify the Modbus parameter value ranges-> min/max with board and simulator.

Updated by Prakash M 3 months ago · Edited Actions
Copy link
 #11

The Modbus parameter names were corrected after updating the placeholders(limits) on the UI.

Next action plan:

1.Modbus parameter value-ranges needs to be verify with E54 board and ModRsim simulator.

Updated by Thomas Joseph 3 months ago · Edited Actions
Copy link
 #12

Prakash M wrote in #note-11:

The Modbus parameter names were corrected after updating the placeholders(limits) on the UI.

Next action plan:

1.Modbus parameter value-ranges needs to be verify with E54 board and ModRsim simulator.

Depends on http://5.161.106.25:3000/issues/2953

Updated by Prakash M 3 months ago Actions
Copy link
 #13

To verify the config packet size i ran the Linux based chola application on edge gateway device .i observed some signal are missed in config packet list.

Log-
+TCPRECV: 0,1655,[1,["EG62702435001s1;40001;True;0;float","EG62702435001s2;40003;True;1;float","EG62702435001s3;40005;True;2;float","EG62702435001s4;40007;True;3;float","EG62702435001s5;40009;True;4;float","EG62702435001s6;40011;True;5;float","EG62702435001s7;40013;True;6;float","EG62702435001s8;40015;True;7;float","EG62702435001s9;40017;True;8;float","EG62702435001s10;40019;True;9;float","EG62702435001s11;40021;True;10;float","EG62702435001s12;40023;True;11;float","EG62702435001s13;40025;True;12;float","EG62702435001s14;40027;True;13;float","EG62702435001s15;40029;True;14;float","EG62702435001s16;40031;True;15;float","EG62702435001s17;40033;True;16;float","EG62702435001s18;40035;True;17;float","EG62702435001s19;40037;True;18;float","EG62702435001s20;40039;True;19;float","EG62702435001s21;40041;True;20;float","EG62702435001s22;40045;True;21;float","EG62702435001s23;40049;True;22;float","EG62702435001s24;40051;True;23;float","EG62702435001s25;40055;True;24;float","EG62702435001s26;40

[+TCPRECV] TCP data parsing started

[+TCPRECV] TCP data parsing started
[DEBUG] CID=0, TotalSize=1655
[RX] Collected 980 / 1655 bytes.

Venu sir told "some suggestion to implement in Linux based code to get the config packet fully".currently i'm doing that one.

Updated by Prakash M 3 months ago Actions
Copy link
 #14

Config pakcet has been gotten, data posting is in process-> linux platform.

Updated by Prakash M 3 months ago Actions
Copy link
 #15

JSON Paylaod is not coming on server side during the data posting from device side.

Updated by Prakash M 3 months ago · Edited Actions
Copy link
 #16

Data posting packet list has been gotten in correct JSON payload format, But in Payload, additional character is adding by automatically on server side during device is sending correct Json payload without adding new JSON payload

For reference: https://elpisit-my.sharepoint.com/:t:/g/personal/satish_sl_elpisitsolutions_com/IQBtUpPxF_V9Q6b7zsaBrR1oAXxthf4U5CEyB0qpOvJ3cmI?e=ruu3aY

Updated by Prakash M about 2 months ago Actions
Copy link
 #17

  • Status changed from In Progress to Resolved

Updated by Prakash M about 2 months ago Actions
Copy link
 #18

  • % Done changed from 90 to 100
Actions
Copy link

Also available in: PDF Atom