Version 0.29 Alpha

[riclolsen]

Notes for version 0.29:

• Default login credentials: username=admin password=jsonscada.
• New IEC61850 Client protocol driver.
• C# MongoDB drivers updated.
• Npm packages updated.
• Refactored Nodejs code for updated mongodb driver.
• MongoDB Compass updated to 1.39.0.
• MongoDB Community Server updated to 6.0.8.
• Grafana updated to 9.5.6.
• Chromium updated to 115.0.5790.102.
• Telegraf runtime updated to 1.27.2.
• Dotnet runtime updated to 6.0.19.
• Nodejs runtime updated to 20.5.0.

Requirements and recommendations:

• Windows 10/11 64 bits or Server >=2016, Windows PowerShell. At least 10GB of free space in the "C:" drive.
• Administrative rights. Corporative Windows policies may cause problems with the creation of services and the opening of TCP ports.
• Free TCP ports 27017, 5432, 80, 8080, 3000, 9000. Other ports may be required for optional services and protocols.
• If the server already has MongoDB, PostgreSQL, Grafana, Nginx or another webserver, please uninstall, disable or watch out for possible conflicts.
• Do not update previously installed JSON-SCADA. Please uninstall previous JSON-SCADA versions before installing a new version.

---

This discussion was created from the release Version 0.29 Alpha.

[arifmjcet]

Hi Ricardo, I am testing json-scada 0.29 on IEC 61850 ieds, Iam facing following issues.

1)I am unable to use excel based configuration tool. Iam getting error( "runtime error:438: Object doesn't support this property or method"). I ensured that "config_server_excel" windows service was running.

2)How to add parameters related to protocol destination for a tag? In web based configuration of tags, parameters related to protocol source are only available to configure. My objective is to get data from IEC 61850 servers using IEC 61850 MMS client protocol driver and then send the same to a IEC-104 client using IEC-104 server protocol driver.

By the way Great work.

[riclolsen]

Hi,

1. I will check this problem.
2. The web UI is not complete in this regard. You can try using MongoDB Compass and update the tags on protocolDestinations array as described here https://github.com/riclolsen/json-scada/blob/master/src/lib60870.netcore/iec104server/README.md#configure-tags-for-distribution.

[riclolsen]

I have tested the Excel config and it works with Excel 2016 and the current 365 version.
The problem can be an older version of Excel or perhaps some locale incompatibility. Please try to use EN-US locale if possible.
Also if you can debug the error, please inform the line of code that is causing the error.

[arifmjcet]

Hi, I have tested excel based configuration using Excel 2021, it is working perfectly fine. It is not working with older versions of excel. Thanks for the support.

[riclolsen]

Thanks, this is important to know.

[arifmjcet]

Hi Ricardo, while trying to use json scada as iec 61850 client, tags are not getting updated by MMS reports from server. Every time json scada client gets a report, i am getting an error ("Value cannot be null. (Parameter 'source')") in the log. Although data is correctly updating using polling. I checked the server side, it is sending reports correctly. I have attached the log file, any help is much appreciated.
61850log.txt

[riclolsen]

I think I understand the problem now.
Reports does not contain data references. This is not implemented yet in this driver.
Processing reports without references will require more time to implement, now I see it is necessary.
Let's see if it works by setting optional bit for requesting data references be included in reports.

Please try this new version, post the logs.

iec61850_client.zip

[arifmjcet]

I have tried the new version and I have posted the new log( Notepad++ line 279 onwards). Now, the json-scada client is receiving the reports sent by the server. One thing I have observed is, every time a report is received, new tags are getting created and the tags which are linked to the received data are also getting updated with the new data. I think only the tags which are associated with the data(using protocol source object address) should be updated. Also, "auto create tags" setting is disabled. Thanks for the great work!
61850log15082023.txt

[riclolsen]

Thanks. You can try this new update to see if it can avoid creating new tags.

iec61850_client.zip

[arifmjcet]

I have tried the new version, it is working perfectly fine for analog data. Thank you very much. I would like to report one more issue I am facing with the json scada client. For digital tags(double point status) , data is not read properly from the server. Example: for status= 0,1 it is showing v=0, but for status= 2, and 3 the value is read as v=1 (61850log1 notepad++ line 272, 277). Also, json scada client is not adding digital status as a "desired entry" when protocol source object address is set as: R2L6M1Control/XCBR1.Pos.stVal (full path) (61850log1 notepad++ line 102) and reports are not getting logged for digital status. When I set protocol source object address as: R2L6M1Control/XCBR1.Pos, reports are getting logged but correct value is not updated in digital tag, for all possible states, v=0 is logged. MMS bitstring is reflecting correct value(61850log2 notepad++ line 314). I have posted both the logs when the actual value of digital tag is =2(ON status).
61850log1.txt
61850log2.txt

[arifmjcet]

One more thing I have observed is, if full path is configured in the protocol source object address field in the digital status tag configuration (eg: R2L6M1Control/XCBR1.Pos.stVal), Although I am getting a value 0( for 00 and 01) or 1 ( for 10 and 11), in HMI graphics, it is correctly showing the digital double point status. On more thing I would like to report is, if I distribute this digital status tag to an iec- 104 client using the json scada IEC- 104 server driver , the value of the digital state is correctly sent for two states 01 and 10. Only reports are not working.

[arifmjcet]

Hi Ricardo, While using excel based configuration tool to configure Iec 61850 tags, the protocol common address is of type "text" and expected entry in the cell is of type int.64. I was able to get around this problem by changing following in realtimeData query in excel file from {"protocolSourceCommonAddress", Int64.Type} to {"protocolSourceCommonAddress", type text} and also replacing following line,
elem.protocolSourceCommonAddress = toMongoDouble(elem.protocolSourceCommonAddress ) with elem.protocolSourceCommonAddress = toMongoDoubleOrString(
elem.protocolSourceCommonAddress
), in index.js file in C:\json-scada\src\config_server_for_excel.

[riclolsen]

There is indeed a problem here. I will fix that. Thanks for reporting.

[riclolsen]

Fixed in the source code.

[arifmjcet]

Thanks!