Virtual robot control
Forward, backward, left, right and stop.
Team of 6 · B.Tech ECE
Software prototype · Robotics & Automation
RoboLink
Software-Based Long-Distance Human–Robot Communication and Teleoperation
Simulating reliable communication between a human operator and a remotely located virtual robot.
B.Tech Electronics & Computer Engineering
Project Discussion Proposal
Explore the proposal→
Human operatorIndia
Internet
Virtual robotLondon
One idea · no hardware required in Phase 1
A beginner-friendly software-first approach to teleoperation01 / 10
01 / DISCOVERY
Problem Statement
What if the robot and its operator are thousands of kilometres apart?
A remote operation scenario
IndiaOperator side
LondonVirtual robot side
How do we keep communication reliable when the network is not?
01
Latency
Commands may arrive late.
02
Packet loss
Some updates may not arrive.
03
Connection failure
The robot may stop hearing the operator.
?How can long-distance human–robot communication become more reliable and safer when network conditions are poor?
The project lens: understand the communication first02 / 10
02 / CONTEXT
Existing Technology
Remote control and teleoperation already exist. Our project builds understanding, not hype.
Common building blocksAVAILABLE TODAY
Internet / IPWi-Fi · 4G · 5GWebSocketMQTTROS 2 / DDSVideo · Audio
Human→Network→Robot
Our opportunity
+
Make the learning visible.
We will create a beginner-friendly software prototype that monitors communication and demonstrates a fail-safe response.
Honest scope: proposed student project, not an industrial product.
Start with fundamentals · measure · respond safely03 / 10
03 / PROPOSAL
What Are We Building?
RoboLink is a web-based software system that simulates a conversation between a human operator and a virtual robot.
Human operatorSends commands
01
Web dashboardControls + observes
02
Communication serverRoutes messages
03
Virtual robotReturns status
0
Phase 1 scope
SOFTWARE ONLYNo physical robot, motors, ESP32, Raspberry Pi, sensors or other hardware.
From idea → observable software prototype04 / 10
04 / BUILD
Our Project Functions
Small, testable functions turn a big robotics question into a clear first-year project.
Real-time communication
Send commands and receive responses.
Robot status
Position, simulated battery and state.
Network monitoring
Latency, packet loss and connection status.
Fail-safe simulation
Detect failure, stop and enter Safe Mode.
One dashboard · five observable behaviours05 / 10
05 / PROTOTYPE
RoboLink Web Dashboard
A simple control room for the operator. Try the controls to see the proposed interaction.
ROBOLINKLIVE ROBOT STATUS
12:42:08ONLINEstable connection
Latency120 ms
Packet loss0.5 %
Robot statusACTIVE
Battery82 %
PositionX = 25, Y = 40
Signal quality
GOOD
VIRTUAL ROBOT CONTROLWASD
↑←STOP→↓
Emergency STOPOperator message“Hello Robot”
→
Robot response“Message received”
Interactive mockup · the first product conversation06 / 10
06 / TESTING
How Will We Test Communication?
We can study network behaviour without hardware by changing the conditions in software.
Choose a simulated condition
Normal networkLow delay · low loss→High latencyCommands arrive late→Packet lossUpdates go missing→DisconnectNo response received→Normal network
Latency120 ms
Packet loss0.5%
Robot statusACTIVE
Robot is operating normally.
These simulations let us study how a remotely operated robot should respond as communication quality changes.
Test the edge cases before adding hardware07 / 10
07 / FOCUS
What Is Our Main Focus?
Fail-safe communication is the idea that connects every part of RoboLink.
01
Communication reliability
Can commands and information reach the virtual robot correctly?
02
Network monitoring
Can we detect latency, packet loss and connection problems?
03
Safety
What happens if communication suddenly stops?
04
Fail-safe operation
Can the system automatically stop the virtual robot when communication becomes unreliable?
GOOD CONNECTIONNormal operation
↓POOR CONNECTIONWarning
↓CONNECTION LOSTSafe Mode → Stop
FAIL-SAFE COMMUNICATION
When in doubt: stop safely, then recover08 / 10
08 / RESOURCES
Resources & Technologies
A lightweight software stack keeps the first phase practical for our team.
01
Software
- HTML
- CSS
- JavaScript
- Node.js
- WebSocket
02
Development
- VS Code / online coding
- GitHub
- Browser DevTools
03
Online services
- GitHub
- Vercel / Netlify
- Suitable cloud backend
04
Design & documentation
- diagrams.net
- Slides / PowerPoint / Canva
- GitHub collaboration
✓
No hardware is required for Phase 1.
We learn the communication workflow in software before connecting physical components.
Keep the first phase focused, affordable and testable09 / 10
09 / NEXT STEP
Expected Outcome & Future Scope
A clear first milestone: prove the communication idea in a safe, observable software environment.
Expected outcome
A working web-based software prototype
RoboLink will demonstrate long-distance human–robot communication using a virtual robot.
✓ Web control✓ Real-time commands✓ Network monitoring✓ Automatic Safe Mode
Future scope · after the prototype
Physical robotLive cameraTwo-way audioReal sensors4G / 5GAI obstacle detectionCybersecurity
“Our first goal is to understand and solve the communication and reliability problem through software simulation before moving to physical robotics.”
Back to the beginning↺Ready for discussion with our mentor and community.
Thank you · Questions & discussion10 / 10