Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't activate more than 1 Bacnet IP datasource simultaneously #2152

Open
nduvernois opened this issue Mar 29, 2022 · 6 comments
Open

Can't activate more than 1 Bacnet IP datasource simultaneously #2152

nduvernois opened this issue Mar 29, 2022 · 6 comments

Comments

@nduvernois
Copy link

nduvernois commented Mar 29, 2022

I have about 130-140 BacNet IP datasources, but as soon as 1 is active, I can't activate the other, and neither can I discover new datapoints in the active datasource, or in any other. This is the same behaviour as in ScadaBR.

For example, after a Tomcat restart, I find this in the event list :
8:57:11 : 'B519 sous-station': Initialization error: Address already in use: Cannot bind
Well, actually, there is no other datasource with the same IP address.

Steps to reproduce the behavior:
Datasources have been initially created in ScadaBR, and the MySQL databased has been dumped to disk and imported to MySQL 5.7

  1. only one BacNet IP address is active
  2. in datasources management, click on any other database to activate it

Configuration

OS: Windows Server 2016
Browser : Chrome
Releases: ScadaLTS 2.6.13, Apache Tomcat 9.0.59, MySQL 5.7.19
I also noticed the same behaviour with ScadaLTS 2.5.1.

Log from tomcat9-stdout:
INFO 2022-03-29T08:57:12,082 (com.serotonin.mango.rt.RuntimeManager.initializeDataSource:378) - Data source 'B519 sous-station' initialized
I have not found anything relevant at the same timestamp in catalina, tomcat9-stderr or localhost logs.

EDIT:

For this issue validation for ports in BACnet data sources will be implemented. Additionally, information about port usage will be added to the help documentation on data source edit view.

@Limraj Limraj added the community Community Reported Issues label Mar 29, 2022
@Limraj Limraj added the bug label Nov 1, 2022
@Golffies Golffies pinned this issue Nov 7, 2023
@Limraj Limraj added high priority and removed community Community Reported Issues labels Nov 10, 2023
@Limraj Limraj added the to check label May 6, 2024
@Limraj Limraj added this to the 2.7.9 milestone May 6, 2024
@Limraj Limraj modified the milestones: 2.7.9, 2.8.0 Jul 10, 2024
@Limraj Limraj assigned Limraj and Patrykb0802 and unassigned Limraj Jul 10, 2024
@Limraj Limraj modified the milestones: 2.8.0, 2.7.9 Jul 14, 2024
@Limraj Limraj self-assigned this Jul 27, 2024
@Limraj Limraj modified the milestones: 2.8.0, 2.9.0 Jul 30, 2024
@nduvernois
Copy link
Author

so, it was just my fault by lack of knowledge in network configuration. The issue was caused by indicating port 47808 on the datapoint configuration for multiple Bacnet sources. May I suggest to add in the comment of bacnet datasources that this "port" field should remain at 0 unless the user knows well enough what he is doing ?

@Limraj
Copy link
Collaborator

Limraj commented Oct 22, 2024

Hi @nduvernois,

  1. Was the problem that more than one Data Source Bacnet had the same port set?
  2. Is it that multiple points were used in one Data Source with the port set to a value other than 0?

Regards,
Kamil Jarmusik

@nduvernois
Copy link
Author

Proposal 1 : more than one Bacnet Data Source had the same port set (= the port number in BacNet properties block).

@Limraj
Copy link
Collaborator

Limraj commented Oct 22, 2024

Thanks, I think we can add such validation so that the Data Source cannot be saved with a busy port.

@nduvernois
Copy link
Author

Maybe it would also be worth precising in the BACnet I/P properties block what is relevant for the distant device (Device ID + broadcast address) and what is relevant for the ScadaLTS server (port, if I correctly understood)

@nduvernois
Copy link
Author

Last comment : when a new Bacnet datasource is created, by default, the field "port" is filled with 47808, whereas I had to input 0 in order to solve my issue. This is ... misleading.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants