Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

I am doing a very similar project, however i decided to start off at a more basic level of control using arrow keys. I assume that you already have a small wifi dongle for your robot? and intend on using your home wifi network?

The next stage is to decide on the type of interaction you wish to achieve. if you are not after providing GUI or dont mind a slow response you can use an SSH program (command line) or a VNC server(Pi GUI) being run on your stationary computer alos connected to the same wifi network. Or do you wish to run the program to recieve your controls on your local computer and then simply send the comands to a smaller recieving program that implements them?

I personally chose the second option and proceeded to create 2 seperate programs.

  • PiBotController (deals with user input and is a client to the server running from my pi)
  • PiBotReciever (This is the server which waits for the commands to be sent to it)

I chose to use a Socket server for simplicity. The server runs constantly whent the robot is active and waits for commands to be sent to predetermined 'sockets'.

The code for the server and client side of this and some of my controller is here;

http://stackoverflow.com/questions/18150100/socketserver-used-to-control-pibot-remotely-python/18150274#18150274https://stackoverflow.com/questions/18150100/socketserver-used-to-control-pibot-remotely-python/18150274#18150274

I have yet to implement the control side within the server as i have been trying to optimise the client such that is doesnt send excessive data when no variables are changing.

I am doing a very similar project, however i decided to start off at a more basic level of control using arrow keys. I assume that you already have a small wifi dongle for your robot? and intend on using your home wifi network?

The next stage is to decide on the type of interaction you wish to achieve. if you are not after providing GUI or dont mind a slow response you can use an SSH program (command line) or a VNC server(Pi GUI) being run on your stationary computer alos connected to the same wifi network. Or do you wish to run the program to recieve your controls on your local computer and then simply send the comands to a smaller recieving program that implements them?

I personally chose the second option and proceeded to create 2 seperate programs.

  • PiBotController (deals with user input and is a client to the server running from my pi)
  • PiBotReciever (This is the server which waits for the commands to be sent to it)

I chose to use a Socket server for simplicity. The server runs constantly whent the robot is active and waits for commands to be sent to predetermined 'sockets'.

The code for the server and client side of this and some of my controller is here;

http://stackoverflow.com/questions/18150100/socketserver-used-to-control-pibot-remotely-python/18150274#18150274

I have yet to implement the control side within the server as i have been trying to optimise the client such that is doesnt send excessive data when no variables are changing.

I am doing a very similar project, however i decided to start off at a more basic level of control using arrow keys. I assume that you already have a small wifi dongle for your robot? and intend on using your home wifi network?

The next stage is to decide on the type of interaction you wish to achieve. if you are not after providing GUI or dont mind a slow response you can use an SSH program (command line) or a VNC server(Pi GUI) being run on your stationary computer alos connected to the same wifi network. Or do you wish to run the program to recieve your controls on your local computer and then simply send the comands to a smaller recieving program that implements them?

I personally chose the second option and proceeded to create 2 seperate programs.

  • PiBotController (deals with user input and is a client to the server running from my pi)
  • PiBotReciever (This is the server which waits for the commands to be sent to it)

I chose to use a Socket server for simplicity. The server runs constantly whent the robot is active and waits for commands to be sent to predetermined 'sockets'.

The code for the server and client side of this and some of my controller is here;

https://stackoverflow.com/questions/18150100/socketserver-used-to-control-pibot-remotely-python/18150274#18150274

I have yet to implement the control side within the server as i have been trying to optimise the client such that is doesnt send excessive data when no variables are changing.

Source Link
D Mason
  • 135
  • 1
  • 11

I am doing a very similar project, however i decided to start off at a more basic level of control using arrow keys. I assume that you already have a small wifi dongle for your robot? and intend on using your home wifi network?

The next stage is to decide on the type of interaction you wish to achieve. if you are not after providing GUI or dont mind a slow response you can use an SSH program (command line) or a VNC server(Pi GUI) being run on your stationary computer alos connected to the same wifi network. Or do you wish to run the program to recieve your controls on your local computer and then simply send the comands to a smaller recieving program that implements them?

I personally chose the second option and proceeded to create 2 seperate programs.

  • PiBotController (deals with user input and is a client to the server running from my pi)
  • PiBotReciever (This is the server which waits for the commands to be sent to it)

I chose to use a Socket server for simplicity. The server runs constantly whent the robot is active and waits for commands to be sent to predetermined 'sockets'.

The code for the server and client side of this and some of my controller is here;

http://stackoverflow.com/questions/18150100/socketserver-used-to-control-pibot-remotely-python/18150274#18150274

I have yet to implement the control side within the server as i have been trying to optimise the client such that is doesnt send excessive data when no variables are changing.