Logical Hardware Controlling Software (Jupiter Software)

• The client was looking forward to develop a Windows-based editable software for the users to create logic to control the hardware connected to the PC.
• The client wants to develop this software from scratch with a feature to accept inbound signals and send outbound commands via:
  • Jupiter Control Module
  • Motor Drives
  • Weight Modules
  • Network Cameras

Additional features required:

• He wants to add a “RUN” button to activate the project and a “STOP” button to stop the project.
• The user can save the project on the computer or open previously-made projects for execution.
• Users will get the status of the inputs and outputs (such as weight value, motor speed, etc.) on a web application.

The client is looking for editable software where every block has its own command.

1. 

   Beginning Cap Blocks are used to start a logic.

2. 

   Execution Blocks are used to send commands.

3. 

   Report Blocks are used to display the value of the results.

4. 

   Report Blocks are used to display the value of the results.

5. 

   Ending Cap Blocks are used to end a logic.

As the client wants this to be Windows-based editable software, so we have followed a systematic approach to developing this software. This will ensure that the software is able to effectively control the hardware it is designed for. Here is a step-by-step approach to designing logical hardware-controlling software:

1. 01

   Determine hardware requirements:

   In the first step, we determined the hardware requirements for the software. This involves identifying the hardware that needs to be controlled, its technical specifications, and any interfaces or protocols that it uses.

2. 02

   Identify the control objectives:

   In the next step, we identified the control objectives of the software, like determining the specific actions that the software needs to perform to control the hardware.

3. 03

   Define the software architecture:

   Once the hardware requirements and control objectives have been identified, we define the software architecture. This involves determining the components that will be required for the software, their functionality, and how they will interact with each other.

4. 04

   Design the software components:

   Based on the software architecture, our next step was to design the software components. This involves creating detailed designs for each component, specifying their functionality, and determining how they will interact with other components.

5. 05

   Develop the software:

   Once the software components have been designed, the next step was to develop the software. This involves writing code, integrating the components, and testing the software to ensure that it works as expected.

6. 06

   Test and validate the software:

   After the software has been developed, we test and validate it rigorously. This involves running the software in a controlled environment, simulating hardware behavior, and ensuring that the software is able to effectively control the hardware.

7. 07

   Deploy and maintain the software:

   Once the software has been validated, the final step is to deploy it to the hardware system and maintain it over time. This involves monitoring the software's performance, addressing any issues that arise, and updating the software as needed to ensure that it continues to meet the hardware control objectives.

• Front End Desktop:-
  MAUI .Net 6
• Back End:-
  .Net Core 6
• Front End Web :-
  Asp.Net Core
• Database :-
  MS SQL
• Server-side language:-
  C# , Type Script
• Communication Protocol :-
  UART , MODBUS , MAX 232 , Ovnif , ZigBee , Wifi , BLE

We developed a complete Windows-based editable software named “Prime Systems Integrated Software” for the users to create logic to control the hardware connected with the PC.

Connect Hardware: Software can accept inbound signals and send outbound commands through the following hardware:

• The Jupiter control module connects with the PCs through RS-485
• Motor drives are connected to the PCs through Modbus to send and accept variable signals.
• Weight modules are connected to the PCs through TTL input.
• Network cameras connected to PCs with USB and WiFi.

For Installation: Users will use the Windows installer package to install the software.

After installation, there will be an Integrids shortcut on the desktop.

For opening the software: Double click on it to open the software:

Run the Save Project Option: If the user wants to run a saved project, then click on the

Run The Saved Project Button and it will ask for the project you want to save. Select the required project and click on OK.

Code Screen: We have created a code screen for this software that will be shown when the user click on the Run button:

Start Creating Option:

Devices Screen: If the user clicks on the start creating option, they will be on the testing page for the devices. Here, users will be able to test the connection of their devices by selecting the applicable parameters.

Fresh Code Screen: The fresh code screen looks like this, and users can go to the code screen and make their logic by dragging the right block.

After completion of the logic, the user can click on the Run button, and if he wants to save the project, he can click on the Save button available in the top right corner of the screen.

After clicking on the Run button, the HMI screen will come up. Click on the "Start Program" button, and it will run your block successfully. If you want to stop the execution, then click on the “Stop Program” button.