Hello, if you have any need, please feel free to consult us, this is my wechat: wx91due

Assignment 1 - Specification

1 Assignment Aims

It is conducted through an experimental hardware setup we will call “the PLC System”.

By the end of the assignment you will have:

2 Assignment Problem

Twenty four of these units have been setup, along with peripheral equipment (encoders, volt meters, LEDs, motors etc.) in the Mechatronics labs at UNSW. You are required to write the necessary software for controlling the PLC. A header file Galil.h has been provided for you. It declares all the functions which you are required to implement. You must create a C++ file called Galil.cpp (NOTE: The file must have this name EXACTLY) and it must contain all the function definitions you will write. These are defined in Galil.h. You are allowed to add your own private member functions or data, but you must not change the existing public member functions and data. Having completed Galil.hand Galil.cpp you must be prepared to demonstrate the functionality of your object class by calling individual functions where appropriate in a main function.

For testing outside of lab sessions, a simulator has been provided. This emulates the functionality of the physical devices as a means of continuing development. Please note that the in-person assessments will run on the physical hardware within the lab so ensure you test on these during your lab sessions.

You will be coding the assignment in Visual Studio 2022 (a C++ IDE produced by Microsoft). Most of the development can be conducted on your own computer, so you will need the software installed. Running the assignment requires connection to the PLC manufactured by Galil. This can be done in one of two ways, either the physical in-lab hardware or the provided simulator. Further information on running the assignment can be found in the provided ‘Galil Use’ document (found on Moodle).

3 Your task

3.1 Part A: Interacting with the Galil PLC

Your task is to implement a set of functions that define a variety of means of communicating with the Galil PLC. Communication is conducted through different commands that are provided by the manufacturer in the documentation (Galil-RIO47142-CommandReference on moodle). You must implement the class member functions defined withinthe Galil.h (in the Galil class). The functionality of each of these is described within the header file itself. These functions each define a way to interact with the hardware, including the digital and analogue inputs and outputs and querying the PLC.

Whenever you send a command to the Galil PLC (whether physical or in the simulator) it must be sent through the provided class EmbeddedFunctions. This has a number of functions defined within EmbeddedFunctions.h that you should review. This provides a wrapper around Galil-provided implementations and a simulator interface.

3.2 Part B: Direct Ethernet communication with hardware

You must now implement your own modified version of this class using TCP communication principles taught in lectures. Your first task is to write the underlying code that permits this communication to take place so that useful commands can be sent to the PLC. Within a separate EmbeddedFunctions project, you have been provided with the header file EmbeddedFunctions.h (note this is different from the header file of the same name in the previous part of the assignment) that outlines a series of functions that you must implement (these will be implemented in the file EmbededFunctions.cpp).

• void GOpen(String^ address, const int port): This establishes a new connection with the PLC by opening up a TCP socket to the prescribed address.
• void GClose(): Closes the existing connection to the PLC.
• String^ GCommand(String^ command): This sends the query within command to the Galil and returns the response to the caller.

All these should be implemented using networking principles discussed within the lectures.

Your code should be written to account for any errors that may occur during execution.

4 Overview of the Supplied Files

There are two projects within the solution which each correlate to one part of this assignment as described in Section 3.

The Galil project is for part A and contains the following important files:

You can find the following in the Moodle site under Assignment 1.

5 Marking Criteria

This assignment is worth 20 % of the total course mark. The breakdown of marks for this assignment is described in table 1.

5.1 In-person assessment

During this in-person assessment, you will also be tested on your implementation of the separate EmbeddedFunctions class (part B). You must have the class implemented as prescribed and the tutor will type in and attempt to send string commands to the Galil through the main function EFMain.cpp.

Warning: You must attend your designated weekly lab class to progress and get support with this assignment. You will be assessed on the physical hardware in the lab classes, so make sure you test your code here beforehand.

5.2 Auto-marking

5.3 Style marking

6 Submission

The first submission is conducted during your practical assessment in your lab class. This will be assessed in person by your demonstrator for the completion of the provided task. You must also submit the assignment files Galil.h, Galil.cpp, and Main.cpp to Moodle in the ‘Assignment 1 - Practical Assessment’ submission box directly after completion of your assessment time (you will be given five minutes for this).

Completion and submission of this component must be during your assigned week 5 lab time slot. Early submission for one bonus mark must be during your assigned week 4 lab time and early submission for two bonus marks must be during your assigned week 3 lab time.

The second submission will be for code style and auto-marking. Without zipping the files, submit your EmbeddedFunctions.h, EmbeddedFunctions.cpp, Galil.h, and Galil.cpp files to Moodle in the ‘Assignment 1 - Code Submission’ submission box. The submitted code will be first checked for similarity scores prior to the assessment outcomes.

Submission must be by 11.59 pm of Friday of week 5 (11 October, 2024). However, early submission can be conducted to gain bonus marks. Submitting one week early (by 11.59 pm of Friday of week 4) will grant one bonus mark and submitting two weeks early (by 11.59 pm of Friday of week 3) will grant two bonus marks.

Note: if you choose to submit early, both components must be submitted early. Submitting both parts one week early will grant a total of one bonus mark. Similarly submitting both parts two weeks early will grant a total of two bonus marks.

Note: bonus marks are added to the assignment, which is capped at 20 marks (you are not able to get more than 20 marks for the assignment).

7 Plagiarism

You will be notified and allowed to justify your case before such a penalty is applied.