[…] Guide to…Remote Connections […]
I have been using TNCviewer to attach to my Pi and run the GUI. It is great. Now I need to start programming the GPIO to work with some sensors and some motors. I also plan on interfacing to some microcontrollers and really get the ball rolling.
I can highly recommend having a go with Adafruit’s Servo tutorial (http://learn.adafruit.com/adafruits-raspberry-pi-lesson-8-using-a-servo-motor/the-pwm-and-servo-kernel-module), I had a go at the weekend and for the cost of a servo for £2 from eBay, it was excellent to wire it up and play around with controlling movement (without needing lots of extra electronics).
Knowing the ip address can be very simple: install a little script that mails the ip address to yourself (most of us have mail access on our phones )
Since I first got my Pi I found having to use a seperate keyboard and mouse a bit of a pain so now my Pi is more or less permanantly attached to my laptop via a USB serial cable (for the console) and network cable so I can conenct remotly to the desktop. (see http://mike632t.wordpress.com/2013/02/10/configure-serial-console-pi/ and http://mike632t.wordpress.com/2013/04/18/remote-desktop-vnc/ )
[…] discussed previously (in the Guide to…Remote Connections), there is the option of using a (console) TTL-serial cable, however this only provides rather slow […]
Thank for your mine of info. I have just found this article through the Raspberry website. It took me several hours to find all this by myself. I have put my experience on my blog http://t.co/AV4t5fOw3N where I talk about SSH, and RDC. Especially you left out that once you have SSH, you can easily browse and modify files on your Raspberry Pi very easily using WinSCP for example.
As for the IP address problem, I think a good way would be to have a small screen or just some LEDs to give you visual feedback. A shutdown button would be usefull as well…
Yep, most of the info was out there, but as you say it can take a while to hunt it all down and follow all the dead-ends.
The network solution is great since if you set-up other things like shared folders (SMB) you can drag and drop files, and backup everything.
The IP address problem can still be a pain, but being able to set it to a fixed IP via the SDCard (when you need to) helps a lot. As mentioned before, the PI “should” be able to automatically set an IP for direct connections too, and if the “hostname” lookup worked every-time, the IP address set becomes less of a problem.
We are getting closer to a perfect, easy solution, but we are not there yet (hopefully a few tweaks to the distro and we will be).
Yes, a safe-shutdown on the RPi, would also help a lot for running headless.
Interesting to see how you guys have gone about things … and the X11 forwarding looks intriguing … will try it out later.
However, I notice that you talk about VNC and have a separate X session. That is fine, but I found that annoying.
I had set Rhythymbox to start automatically to act as my music server. Using tightVNC meant that I would not ordinarily
be able to control Rhythymbox via tightVNC.
A bit of searching around and I found x11vnc which was very easy to set up and connects to an existing X session.
If you would like some notes, let me know.
Yes that would be very useful.
I wasn’t keen on VNC starting each time (if it was needed or not), so I added that to a start up menu, so I could enable it via SSH if required.
Would be interested to hear more about the x11vnc solution, could be helpful. So far, x11 works great (particularly now I got it working with Tkinter etc) when coupled with shared folders, means you can code directly on PC.
sudo apt-get install x11vnc
x11vnc -forever -usepw -display :0
whcih seems pretty easy.
I have set x11vnc to start auto-matically on start up.
Let me know what you reckon.
amazing thank you took a bit of time but was worth it :D
[…] Guide to…Remote Connections | Meltwater's Raspberry Pi Hardware. […]
What help do you require?
I strongly recommend installing the “avahi-autoipd” and “avahi-daemon” packages on the Pi so you don’t need to manually configure an address on the Pi or even have a DHCP server on your network (e.g. if you have a direct cable between the Pi and your other computer).
why [xx] does tkinter need trusted X11 forwarding -.-
ssh -Y … Enables trusted X11 forwarding
Fill in your details below or click an icon to log in:
You are commenting using your WordPress.com account. ( Log Out / Change )
You are commenting using your Twitter account. ( Log Out / Change )
You are commenting using your Facebook account. ( Log Out / Change )
You are commenting using your Google+ account. ( Log Out / Change )
Connecting to %s
Notify me of new comments via email.
Get every new post delivered to your Inbox.
Join 131 other followers