Skip to content
ShiHau edited this page Mar 5, 2022 · 7 revisions

Welcome to the Collaborative-Robotics-Interface-CRI- wiki!

This Wiki Page acts as a hub where all documentation within this GitHub repo can be found. At the bottom of this wiki is a list of improvements/ optimizations and issues to be fixed, it will be updated as the issues get resolved.

Video Documentation for Dobot Node-RED CR5

Part 1: https://youtu.be/nr1G-7w5hfA

Part 2: https://youtu.be/9sca3ibS7go

PDF Documentation for Dobot Node-RED CR5

Node-Red CR5 Documentation.pdf

Dobot Blockly Python Web App for CR5

Documentation for Blockly Web App.docx

Improvements optimizations and issues to be fixed

For CR5 Node Red

  1. Rework method of retrieving data to use a for loop and modifying the method of exporting data to not include an end at the back. This way users could save multiple times in a session without causing errors to the code.

  2. Move chunks of code into functions so the main() function will not have to be so long and messy

  3. Think of a more optimal way to clear MQTT after certain data has been sent to avoid repeat sending of data. Current method involves sending a dummy message to MQTT to change the data to something irrelevant.

  4. Add more methods of movement into the export csv portion, allowing users to perform MoveL, MoveC etc.

  5. Issues laid out under the issues tab

For CR5 Blockly

  1. Add more features to fully flesh out the CR5 blockly generation of python script such as I/O, end effector setting etc.

For MG400 Node Red

  1. Rework method of retrieving data to use a for loop and modifying the method of exporting data to not include an end at the back. This way users could save multiple times in a session without causing errors to the code.

  2. Move chunks of code into functions so the main() function will not have to be so long and messy

  3. Think of a more optimal way to clear MQTT after certain data has been sent to avoid repeat sending of data. Current method involves sending a dummy message to MQTT to change the data to something irrelevant.

  4. Add more methods of movement into the export csv portion, allowing users to perform MoveL, MoveC etc.

  5. Issues laid out under the issues tab