1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries tagged robot
</title>
5 <description>Entries tagged robot
</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>The space rover coquine, or how I ended up on the dark side of the moon
</title>
11 <link>http://people.skolelinux.org/pere/blog/The_space_rover_coquine__or_how_I_ended_up_on_the_dark_side_of_the_moon.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_space_rover_coquine__or_how_I_ended_up_on_the_dark_side_of_the_moon.html
</guid>
13 <pubDate>Sun,
2 Jun
2019 23:
55:
00 +
0200</pubDate>
14 <description><p
>A while back a college and friend from Debian and the Skolelinux /
15 Debian Edu project approached me, asking if I knew someone that might
16 be interested in helping out with a technology project he was running
17 as a teacher at
<a href=
"https://www.ecolefrancodanoise.dk/
">L
'école
18 franco-danoise
</a
> - the Danish-French school and kindergarden. The
19 kids were building robots, rovers. The story behind it is to build a
21 <a href=
"http://blog.ecolefrancodanoise.dk/first-week-on-the-dark-side
">on
22 the dark side of the moon
</a
>, and remote control it. As travel cost
23 was a bit high for the final destination, and they wanted to test the
24 concept first, he was looking for volunteers to host a rover for the
25 kids to control in a foreign country. I ended up volunteering as a
26 host, and last week the rover arrived. It took a while to arrive
27 after
<a href=
"http://blog.ecolefrancodanoise.dk/model-moms
">it was
28 built and shipped
</a
>, because of customs confusion. Luckily we were
29 able fix it quickly with help from my colleges at work.
</p
>
31 <p
>This is what it looked like when the rover arrived. Note the cute
32 eyes looking up on me from the wrapping
</p
>
34 <img src=
"http://people.skolelinux.org/pere/blog/images/
2019-
06-
02-robot-dark-side-of-moon-esken-med-det-rare-i.jpeg
" width=
"32%
" style=
"clear:left
"/
>
35 <img src=
"http://people.skolelinux.org/pere/blog/images/
2019-
06-
02-robot-dark-side-of-moon-den-ser-meg.jpeg
" width=
"32%
" style=
"clear:left
"/
>
36 <img src=
"http://people.skolelinux.org/pere/blog/images/
2019-
06-
02-robot-dark-side-of-moon-en-skrue-loes.jpeg
" width=
"32%
" style=
"clear:left
"/
>
38 <p style=
"text-align:left
">Once the robot arrived, we needed to track
39 down batteries and figure out how to build custom firmware for it with
40 the appropriate wifi settings. I asked a friend if I could get two
41 18650 batteries from his pile of Tesla batteries (he had then from the
42 wrack of a crashed Tesla), so now the rover is running on Tesla
46 <a href=
"https://gitlab.com/ecolefrancodanoise/arduino-efd/
">the rover
47 firmware
</a
> proved a bit harder, as the code did not work out of the
48 box with the Arduino IDE package in Debian Buster. I suspect this is
50 <a href=
"https://github.com/arduino/Arduino/pull/
2703"> license problem
51 with arduino
</a
> blocking Debian from upgrading to the latest version.
52 In the end we gave up debugging why the IDE failed to find the
53 required libraries, and ended up using the Arduino Makefile from the
54 <a href=
"https://tracker.debian.org/pkg/arduino-mk
">arduino-mk Debian
55 package
</a
> instead. Unfortunately the camera library is missing from
56 the Arduino environment in Debian, so we disabled the camera support
57 for the first firmware build, to get something up and running. With
58 this reduced firmware, the robot could be controlled via the
59 controller server, driving around and measuring distance using its
60 internal acoustic sensor.
</p
>
62 <p
>Next, With some help from my friend in Denmark, which commited the
63 camera library into the gitlab repository for me to use, we were able
64 to build a new and more complete version of the firmware, and the
65 robot is now up and running. This is what the
"commander
" web page
66 look like after taking a measurement and a snapshot:
</p
>
68 <img src=
"http://people.skolelinux.org/pere/blog/images/
2019-
06-
02-robot-dark-side-of-moon-commander.png
" width=
"40%
" border=
"1" align=
"center
"/
>
70 <p
>If you want to learn more about this project, you can check out the
71 <a href=
"https://hackaday.io/project/
164082-the-dark-side-challenge
">The
72 Dark Side Challenge
</a
> Hackaday web pages.
</p
>
74 <p
>As usual, if you use Bitcoin and want to show your support of my
75 activities, please send Bitcoin donations to my address
76 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
81 <title>Debian now got everything you need to program Micro:bit
</title>
82 <link>http://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</link>
83 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</guid>
84 <pubDate>Tue,
22 Jan
2019 17:
20:
00 +
0100</pubDate>
85 <description><p
>I am amazed and very pleased to discover that since a few days ago,
86 everything you need to program the
<a href=
"https://microbit.org/
">BBC
87 micro:bit
</a
> is available from the Debian archive. All this is
88 thanks to the hard work of Nick Morrott and the Debian python
89 packaging team. The micro:bit project recommend the mu-editor to
90 program the microcomputer, as this editor will take care of all the
91 machinery required to injekt/flash micropython alongside the program
92 into the micro:bit, as long as the pieces are available.
</p
>
94 <p
>There are three main pieces involved. The first to enter Debian
96 <a href=
"https://tracker.debian.org/pkg/python-uflash
">python-uflash
</a
>,
97 which was accepted into the archive
2019-
01-
12. The next one was
98 <a href=
"https://tracker.debian.org/pkg/mu-editor
">mu-editor
</a
>, which
99 showed up
2019-
01-
13. The final and hardest part to to into the
101 <a href=
"https://tracker.debian.org/pkg/firmware-microbit-micropython
">firmware-microbit-micropython
</a
>,
102 which needed to get its build system and dependencies into Debian
103 before it was accepted
2019-
01-
20. The last one is already in Debian
104 Unstable and should enter Debian Testing / Buster in three days. This
105 all allow any user of the micro:bit to get going by simply running
106 'apt install mu-editor
' when using Testing or Unstable, and once
107 Buster is released as stable, all the users of Debian stable will be
108 catered for.
</p
>
110 <p
>As a minor final touch, I added rules to
111 <a href=
"https://tracker.debian.org/pkg/isenkram
">the isenkram
112 package
</a
> for recognizing micro:bit and recommend the mu-editor
113 package. This make sure any user of the isenkram desktop daemon will
114 get a popup suggesting to install mu-editor then the USB cable from
115 the micro:bit is inserted for the first time.
</p
>
117 <p
>This should make it easier to have fun.
</p
>
119 <p
>As usual, if you use Bitcoin and want to show your support of my
120 activities, please send Bitcoin donations to my address
121 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
126 <title>My own self balancing Lego Segway
</title>
127 <link>http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
128 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
129 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
130 <description><p
>A while back I received a Gyro sensor for the NXT
131 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
132 present. It had been on my wishlist for a while, because I wanted to
133 build a Segway like balancing lego robot. I had already built
134 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
135 robot
</a
> with the kids, using the light/color sensor included in the
136 NXT kit as the balance sensor, but it was not working very well. It
137 could balance for a while, but was very sensitive to the light
138 condition in the room and the reflective properties of the surface and
139 would fall over after a short while. I wanted something more robust,
141 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
142 gyro sensor from HiTechnic
</a
> I believed would solve it on my
143 wishlist for some years before it suddenly showed up as a gift from my
144 loved ones. :)
</p
>
146 <p
>Unfortunately I have not had time to sit down and play with it
147 since then. But that changed some days ago, when I was searching for
148 lego segway information and came across a recipe from HiTechnic for
150 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
151 HTWay
</a
>, a segway like balancing robot. Build instructions and
152 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
153 code
</a
> was included, so it was just a question of putting it all
154 together. And thanks to the great work of many Debian developers, the
155 compiler needed to build the source for the NXT is already included in
156 Debian, so I was read to go in less than an hour. The resulting robot
157 do not look very impressive in its simplicity:
</p
>
159 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
161 <p
>Because I lack the infrared sensor used to control the robot in the
162 design from HiTechnic, I had to comment out the last task
163 (taskControl). I simply placed /* and */ around it get the program
164 working without that sensor present. Now it balances just fine until
165 the battery status run low:
</p
>
167 <p align=
"center
"><video width=
"70%
" controls=
"true
">
168 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
169 </video
></p
>
171 <p
>Now we would like to teach it how to follow a line and take remote
172 control instructions using the included Bluetooth receiver in the NXT.
</p
>
174 <p
>If you, like me, love LEGO and want to make sure we find the tools
175 they need to work with LEGO in Debian and all our derivative
176 distributions like Ubuntu, check out
177 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
178 project page
</a
> and join the Debian LEGO team. Personally I own a
179 RCX and NXT controller (no EV3), and would like to make sure the
180 Debian tools needed to program the systems I own work as they
186 <title>All drones should be radio marked with what they do and who they belong to
</title>
187 <link>http://people.skolelinux.org/pere/blog/All_drones_should_be_radio_marked_with_what_they_do_and_who_they_belong_to.html
</link>
188 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/All_drones_should_be_radio_marked_with_what_they_do_and_who_they_belong_to.html
</guid>
189 <pubDate>Thu,
21 Nov
2013 15:
40:
00 +
0100</pubDate>
190 <description><p
>Drones, flying robots, are getting more and more popular. The most
191 know ones are the killer drones used by some government to murder
192 people they do not like without giving them the chance of a fair
193 trial, but the technology have many good uses too, from mapping and
194 forest maintenance to photography and search and rescue. I am sure it
195 is just a question of time before
"bad drones
" are in the hands of
196 private enterprises and not only state criminals but petty criminals
197 too. The drone technology is very useful and very dangerous. To have
198 some control over the use of drones, I agree with Daniel Suarez in his
200 "<a href=
"https://archive.org/details/DanielSuarez_2013G
">The kill
201 decision shouldn
't belong to a robot
</a
>", where he suggested this
202 little gem to keep the good while limiting the bad use of drones:
</p
>
206 <p
>Each robot and drone should have a cryptographically signed
207 I.D. burned in at the factory that can be used to track its movement
208 through public spaces. We have license plates on cars, tail numbers on
209 aircraft. This is no different. And every citizen should be able to
210 download an app that shows the population of drones and autonomous
211 vehicles moving through public spaces around them, both right now and
212 historically. And civic leaders should deploy sensors and civic drones
213 to detect rogue drones, and instead of sending killer drones of their
214 own up to shoot them down, they should notify humans to their
215 presence. And in certain very high-security areas, perhaps civic
216 drones would snare them and drag them off to a bomb disposal facility.
</p
>
218 <p
>But notice, this is more an immune system than a weapons system. It
219 would allow us to avail ourselves of the use of autonomous vehicles
220 and drones while still preserving our open, civil society.
</p
>
224 <p
>The key is that
<em
>every citizen
</em
> should be able to read the
225 radio beacons sent from the drones in the area, to be able to check
226 both the government and others use of drones. For such control to be
227 effective, everyone must be able to do it. What should such beacon
228 contain? At least formal owner, purpose, contact information and GPS
229 location. Probably also the origin and target position of the current
230 flight. And perhaps some registration number to be able to look up
231 the drone in a central database tracking their movement. Robots
232 should not have privacy. It is people who need privacy.
</p
>
237 <title>Perl library to control the Spykee robot moved to github
</title>
238 <link>http://people.skolelinux.org/pere/blog/Perl_library_to_control_the_Spykee_robot_moved_to_github.html
</link>
239 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_library_to_control_the_Spykee_robot_moved_to_github.html
</guid>
240 <pubDate>Sat,
19 Oct
2013 10:
20:
00 +
0200</pubDate>
241 <description><p
>Back in
2010, I created a Perl library to talk to
242 <a href=
"http://en.wikipedia.org/wiki/Spykee
">the Spykee robot
</a
>
243 (with two belts, wifi, USB and Linux) and made it available from my
244 web page. Today I concluded that it should move to a site that is
245 easier to use to cooperate with others, and moved it to github. If
246 you got a Spykee robot, you might want to check out
247 <a href=
"https://github.com/petterreinholdtsen/libspykee-perl
">the
248 libspykee-perl github repository
</a
>.
</p
>
253 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
254 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
255 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
256 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
257 <description><P
>In January,
258 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
259 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
260 channel #debian-lego
</a
>, for those of us in the Debian and Linux
261 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
262 marvellous construction system from Denmark. We also created
263 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
264 a place to take notes and write down our plans and hopes. And several
265 people showed up to help. I was very happy to see the effect of my
266 call. Since the small start, we have a debtags tag
267 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
268 tag for LEGO related packages, and now count
10 packages related to
269 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
271 <p
><table
>
272 <tr
><td
><a href=
"http://packages.qa.debian.org/brickos
">brickos
</a
></td
><td
>alternative OS for LEGO Mindstorms RCX. Supports development in C/C++
</td
></tr
>
273 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
274 <tr
><td
><a href=
"http://packages.qa.debian.org/libnxt
">libnxt
</a
></td
><td
>utility library for talking to the LEGO Mindstorms NX
</td
></tr
>
275 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
276 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
277 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
278 <tr
><td
><a href=
"http://packages.qa.debian.org/python-nxt
">python-nxt
</a
></td
><td
>python driver/interface/wrapper for the Lego Mindstorms NXT robot
</td
></tr
>
279 <tr
><td
><a href=
"http://packages.qa.debian.org/python-nxt-filer
">python-nxt-filer
</a
></td
><td
>simple GUI to manage files on a LEGO Mindstorms NXT
</td
></tr
>
280 <tr
><td
><a href=
"http://packages.qa.debian.org/scratch
">scratch
</a
></td
><td
>easy to use programming environment for ages
8 and up
</td
></tr
>
281 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
282 </table
></p
>
284 <p
>Some of these are available in Wheezy, and all but one are
285 currently available in Jessie/testing. leocad is so far only
286 available in experimental.
</p
>
288 <p
>If you care about LEGO in Debian, please join us on IRC and help
289 adding the rest of the great free software tools available on Linux
290 for LEGO designers.
</p
>
295 <title>Moved the pymissile Debian packaging to collab-maint
</title>
296 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
297 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
298 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
299 <description><p
>As part of my investigation on how to improve the support in Debian
300 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
301 Launcher and updated the Debian package
302 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
303 sure udev will fix the device permissions when it is plugged in. I
304 also added a
"Modaliases
" header to test it in the Debian archive and
305 hopefully make the package be proposed by jockey in Ubuntu when a user
306 plug in his rocket launcher. In the process I moved the source to a
307 git repository under collab-maint, to make it easier for any DD to
308 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
309 is not very active, but the software still work for me even after five
310 years of relative silence. The new git repository is not listed in
311 the uploaded package yet, because I want to test the other changes a
312 bit more before I upload the new version. If you want to check out
313 the new version with a .desktop file included, visit the
314 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
315 view
</a
> or use
"<tt
>git clone
316 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
321 <title>New IRC channel for LEGO designers using Debian
</title>
322 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
323 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
324 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
325 <description><p
>During Christmas, I have worked a bit on the Debian support for
326 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
327 NXT
</a
>. My son and I have played a bit with my NXT set, and I
328 discovered I had to build all the tools myself because none were
329 already in Debian Squeeze. If Debian support for LEGO is something
330 you care about, please join me on the IRC channel
331 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
332 irc.debian.org). There is a lot that could be done to improve the
333 Debian support for LEGO designers. For example both CAD software
334 and Mindstorm compilers are missing. :)
</p
>
336 <p
>Update
2012-
01-
03: A
337 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
338 including links to Lego related packages is now available.
</p
>
343 <title>First version of a Perl library to control the Spykee robot
</title>
344 <link>http://people.skolelinux.org/pere/blog/First_version_of_a_Perl_library_to_control_the_Spykee_robot.html
</link>
345 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_version_of_a_Perl_library_to_control_the_Spykee_robot.html
</guid>
346 <pubDate>Sat,
9 Oct
2010 14:
00:
00 +
0200</pubDate>
347 <description><p
>This summer I got the chance to buy cheap Spykee robots, and since
348 then I have worked on getting Linux software in place to control them.
349 The firmware for the robot is available from the producer, and using
350 that source it was trivial to figure out the protocol specification.
351 I
've started on a perl library to control it, and made some demo
352 programs using this perl library to allow one to control the
355 <p
>The library is quite functional already, and capable of controlling
356 the driving, fetching video, uploading MP3s and play them. There are
357 a few less important features too.
</p
>
359 <p
>Since a few weeks ago, I ran out of time to spend on this project,
360 but I never got around to releasing the current source. I decided
361 today that it was time to do something about it, and uploaded the
362 source to my Debian package store at people.skolelinux.org.
</p
>
364 <p
>Because it was simpler for me, I made a Debian package and
365 published the source and deb. If you got a spykee robot, grab the
366 source or binary package:
</p
>
369 <li
><a href=
"http://people.skolelinux.org/~pere/debian/packages/lenny/libspykee-perl_0.0
.20101009-
1.tar.gz
">libspykee-perl_0.0
.20101009-
1.tar.gz
</a
></li
>
370 <li
><a href=
"http://people.skolelinux.org/~pere/debian/packages/lenny/libspykee-perl_0.0
.20101009-
1.dsc
">libspykee-perl_0.0
.20101009-
1.dsc
</a
></li
>
371 <li
><a href=
"http://people.skolelinux.org/~pere/debian/packages/lenny/libspykee-perl_0.0
.20101009-
1_all.deb
">libspykee-perl_0.0
.20101009-
1_all.deb
</a
></li
>
372 </ul
></p
>
374 <p
>If you are interested in helping out with developing this library,
375 please let me know.
</p
>
380 <title>My first perl GUI application - controlling a Spykee robot
</title>
381 <link>http://people.skolelinux.org/pere/blog/My_first_perl_GUI_application___controlling_a_Spykee_robot.html
</link>
382 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/My_first_perl_GUI_application___controlling_a_Spykee_robot.html
</guid>
383 <pubDate>Wed,
1 Sep
2010 21:
00:
00 +
0200</pubDate>
384 <description><p
>This evening I made my first Perl GUI application. The last few
385 days I have worked on a Perl module for controlling my recently
386 aquired Spykee robots, and the module is now getting complete enought
387 that it is possible to use it to control the robot driving at least.
388 It was now time to figure out how to use it to create some GUI to
389 allow me to drive the robot around. I picked PerlQt as I have had
390 positive experiences with the Qt API before, and spent a few minutes
391 browsing the web for examples. Using Qt Designer seemed like a short
392 cut, so I ended up writing the perl GUI using Qt Designer and
393 compiling it into a perl program using the puic program from
394 libqt-perl. Nothing fancy yet, but it got buttons to connect and
395 drive around.
</p
>
397 <p
>The perl module I have written provide a object oriented API for
398 controlling the robot. Here is an small example on how to use it:
</p
>
402 Spykee::discover(sub {$robot{$_[
0]} = $_[
1]});
403 my $host = (keys %robot)[
0];
404 my $spykee = Spykee-
>new();
405 $spykee-
>contact($host,
"admin
",
"admin
");
410 $spykee-
>forward();
415 </pre
></p
>
417 <p
>Thanks to the release of the source of the robot firmware, I could
418 peek into the implementation at the other end to figure out how to
419 implement the protocol used by the robot. I
've implemented several of
420 the commands the robot understand, but is still missing the camera
421 support to make it possible to control the robot from remote. First I
422 want to implement support for uploading new firmware and configuring
423 the wireless network, to make it possible to bootstrap a Spykee robot
424 without the producers Windows and MacOSX software (I only have Linux,
425 so I had to ask a friend to come over to get the robot testing
428 <p
>Will release the source to the public soon, but need to figure out
429 where to make it available first. I will add a link to
430 <a href=
"http://wiki.nuug.no/grupper/robot/
">the NUUG wiki
</a
> for
431 those that want to check back later to find it.
</p
>
436 <title>Robot, reis deg...
</title>
437 <link>http://people.skolelinux.org/pere/blog/Robot__reis_deg___.html
</link>
438 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Robot__reis_deg___.html
</guid>
439 <pubDate>Sat,
21 Aug
2010 22:
10:
00 +
0200</pubDate>
440 <description><p
>I dag fikk jeg endelig tittet litt på mine nyinnkjøpte roboter, og
441 har brukt noen timer til å google etter interessante referanser og
442 aktuell kildekode for bruk på Linux. Det mest lovende så langt er
443 <a href=
"http://ispykee.toyz.org/
">ispykee
</a
>, som har en
444 BSD-lisensiert linux-daemon som står som mellomledd mellom roboter på
445 lokalnettet og en sentral tjeneste der en iPhone kan koble seg opp for
446 å fjernstyre roboten. Linux-daemonen implementerer deler av
447 protokollen som roboten forstår. Etter å ha knotet litt med å oppnå
448 kontakt med roboten (den oppretter et eget ad-hoc wifi-nett, så jeg
449 måtte gå av mitt vanlige nett for å få kontakt), og kommet frem til at
450 den lytter på IP-port
9000 og
9001, gikk jeg i gang med å finne ut
451 hvordan jeg kunne snakke med roboten vha. disse portene. Robotbiten
452 av protokollen er publisert av produsenten med GPL-lisens, slik at det
453 er mulig å se hvordan protokollen fungerer. Det finnes en java-klient
454 for Android som så ganske snasen ut, men fant ingen kildekode for
455 denne. Derimot hadde iphone-løsningen kildekode, så jeg tok
456 utgangspunkt i den.
</p
>
458 <p
>Daemonen ville i utgangspunktet forsøke å kontakte den sentrale
459 tjenesten som iphone-programmet kobler seg til. Jeg skrev dette om
460 til i stedet å sette opp en nettverkstjeneste på min lokale maskin,
461 som jeg kan koble meg opp til med telnet og gi kommandoer til roboten
462 (act, forward, right, left, etc). Det involverte i praksis å bytte ut
463 socket()/connect() med socket()/bind()/listen()/accept() for å gjøre
464 klienten om til en tjener.
</p
>
466 <p
>Mens jeg har forsøkt å få roboten til å bevege seg har min samboer
467 skrudd sammen resten av roboten for å få montert kamera og plastpynten
468 (armer, plastfiber for lys). Nå er det hele montert, og roboten er
469 klar til bruk. Må få flyttet den over til mitt vanlige trådløsnett
470 før det blir praktisk, men de bitene av protokollen er ikke
471 implementert i ispykee-daemonen, så der må jeg enten få tak i en mac
472 eller en windows-maskin, eller implementere det selv.
</p
>
474 <p
>Vi var tre som kjøpte slike roboter, og vi har blitt enige om å
475 samle notater og referanser på
<a
476 href=
"http://wiki.nuug.no/grupper/robot/
">NUUGs wiki
</a
>. Ta en titt
477 der hvis du er nysgjerrig.
</p
>
482 <title>2 Spykee-roboter i hus, nå skal det lekes
</title>
483 <link>http://people.skolelinux.org/pere/blog/
2_Spykee_roboter_i_hus__n__skal_det_lekes.html
</link>
484 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/
2_Spykee_roboter_i_hus__n__skal_det_lekes.html
</guid>
485 <pubDate>Wed,
18 Aug
2010 13:
30:
00 +
0200</pubDate>
486 <description><p
>Jeg kjøpte nettopp to
487 <a href=
"http://www.spykee-robot.com/
">Spykee
</a
>-roboter, for test og
488 leking. Kjøpte to da det var så billige, og gir meg mulighet til å
489 eksperimentere uten å være veldig redd for å ødelegge alt ved å bytte
490 ut firmware og slikt. Oppdaget at lekebutikken på Bryn senter hadde
491 en liten stabel på lager som de ikke hadde klart å selge ut etter
492 fjorårets juleinnkjøp, og var villig til å selge for en femtedel av
493 vanlig pris. Jeg, Ronny og Jarle har skaffet oss restbeholdningen, og
494 det blir morsomt å se hva vi får ut av dette.
</p
>
496 <p
>Roboten har belter styrt av to motorer, kamera, høytaler, mikrofon
497 og wifi-tilkobling. Det hele styrt av en GPL-lisensiert databoks som
498 jeg mistenker kjører linux. Firmware-kildekoden ble visst publisert i
499 mai. Eneste utfordringen er at kontroller-programvaren kun finnes til
500 Windows, men det må en kunne jobbe seg rundt når vi har kildekoden til
501 firmwaren. :)
</p
>
504 <li
><a href=
"http://en.wikipedia.org/wiki/Spykee
">Wikipedia-oppføring
</a
></li
>
505 <li
><a href=
"http://www.spykeeworld.com/spykee/US/freeSoftware.html
">Nedlasting av firmware-kilden
</a
></li
>
506 <li
><a href=
"http://wiki.nuug.no/grupper/robot
">prosjektwiki hos NUUG
</a
></li
>