There is already a lot of information about testing an Ethernet connection on issue #59 from our previous repo.
After basic communication is tested using Ethernet, Python classes should be made according to the UML Class diagram.
Refer to the Network Communication and GUI design plans.
Albertaloop 2\3 - Electrical\2 - Software Group\1 - Design\T_SWE_PLAN - GUI.gdoc
Albertaloop 2\3 - Electrical\2 - Software Group\1 - Design\T_SWE_PLAN - Network Communications.gdoc
Add your changes to a new branch fromhttps://github.com/albertaloop/T_SWE_2022_2023/tree/NetworkComms/main, title your branch NetworkComms/(yourname)-(changes) without parenthesis and create a pull request to merge your branch back to NetworkComms/main when your work is completed.
Summary
There is already a lot of information about testing an Ethernet connection on issue #59 from our previous repo. After basic communication is tested using Ethernet, Python classes should be made according to the UML Class diagram.
Refer to the Network Communication and GUI design plans. Albertaloop 2\3 - Electrical\2 - Software Group\1 - Design\T_SWE_PLAN - GUI.gdoc Albertaloop 2\3 - Electrical\2 - Software Group\1 - Design\T_SWE_PLAN - Network Communications.gdoc
Add your changes to a new branch fromhttps://github.com/albertaloop/T_SWE_2022_2023/tree/NetworkComms/main, title your branch NetworkComms/(yourname)-(changes) without parenthesis and create a pull request to merge your branch back to NetworkComms/main when your work is completed.
Acceptance Criteria