November 20, 2023 at 9:25 am #13667
I am encountering some issues while initiating a SCADA project and would appreciate any assistance. Here are the specific problems I’ve run into:
Initial Project Launch: When starting the project for the first time, I noticed missing files such as ‘lang’ and ‘Mod’. To address this, I copied these files from the path where scada v6 was installed into the source code path. I’m not sure if this was the correct approach, but it allowed the project to start.
Launching Components: I was able to launch scadaAdmin, scadaServer, scadaAgentApp, and scadaComm. However, when starting scadaComm, the console displayed the following messages:
“Communicator is started successfully”
“Press ‘x’ or create ‘commstop’ file to stop Communicator”
After a few seconds, an error occurred at the line commLine.Channel.MakeReady(); with a System.NullReferenceException: “Object reference not set to an instance of an object.” Interestingly, this error did not appear in the console.
Configuration Upload Issue: When I attempted to upload the configuration in admin, I encountered an error stating, “Error uploading configuration: InternalServerError: Error while processing the operation.”
I am seeking advice on how to resolve these issues. Any insights or suggestions would be greatly appreciated.November 20, 2023 at 9:33 am #13668
Additionally, I have another question. If I follow the standard procedure for launching the application, what should I do to complete the missing ‘mod’, ‘lang’, and other XML configuration files after downloading the source code?November 20, 2023 at 11:44 am #13674
Please provide more info how do you launch a project? Screenshots can help.November 21, 2023 at 2:43 am #13677
1.I Build the solutions using Visual Studio in the sequence below.
then I start the ScadaComm with Debug .November 21, 2023 at 2:43 am #13678November 21, 2023 at 2:55 am #13679
I made an error with the admin configuration file, but I don’t know why. Can you provide some ideas?
https://sm.ms/image/aWEMyYhdItSDj3BNovember 21, 2023 at 11:31 am #13689
After building the applications you need to copy the output files in the Rapid SCADA installation folder. See the file structure in the distributive package.
To debug applications from VS, use Debug – Attach to Process menu.November 21, 2023 at 11:33 am #13690
To run Rapid SCADA *dll, *.xml and other files should be in proper locations.November 22, 2023 at 10:20 am #13697
I’m very sorry for bothering you.
I want to try writing a driver module. After successfully generating it, I placed the .dll files in their respective locations. However, I am unable to use them in the admin. Below are screenshots of my code and my attempt to use it in the admin.
November 23, 2023 at 12:00 pm #13703
Full class name of DrvUdpView must be as written in the error message. You should change the namespace to meet the requirements.
- You must be logged in to reply to this topic.