Changes between Version 2 and Version 3 of Old/Dailyupdates


Ignore:
Timestamp:
Jun 8, 2007, 7:36:57 PM (17 years ago)
Author:
aniket
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Old/Dailyupdates

    v2 v3  
    22All day we wrestled with the ERSP installation. The error we got over and over was a license error which appeared immediately after the installer asks for the product id (312).
    33
    4 Apparently, the installer uses the less command to display the EULA. For future reference, ERSP will not install unless the less package is available. Many hours were spent on this problem. Once this was done, the packages ersp-license and ersp-config installed successfully.
     4Apparently, the installer uses the ''less'' command to display the EULA. For future reference, ERSP will not install unless the ''less'' package is available. Many hours were spent on this problem. Once this was done, the packages ersp-license and ersp-config installed successfully.
    55
    6 The main package, ersp, faced a chain of unmet dependencies. Tracing them to their route led to the packages libraw1394-5 and libdc1395-11, libraries involved in firewire data transfer. Once these packages were downloaded from the debian site and installed via dpkg, the ersp package installed without further error.
     6The main package, ''ersp'', faced a chain of unmet dependencies. Tracing them to their root led to the packages ''libraw1394-5'' and ''libdc1394-11'', libraries involved in firewire data transfer. Once these packages were downloaded from the debian site and installed via dpkg, the ersp package installed without further error.
    77
    8 We’ve been working on Mobile 33, which after the day’s work has working copy of Debian Sarge with Gnome. The /opt/evolution_robotics directory is populated by the software package.
     8We’ve been working on Mobile 33, which after the day’s work has working copy of Debian Sarge with Gnome. The ''/opt/evolution_robotics'' directory is populated by the software package.
    99
    10 The package ersp-sample-code¬ installed easily. I created a folder in our home directory in which I untarred the sample code.
     10The package ''ersp-sample-code'' installed easily. I created a folder in our home directory in which I untarred the sample code.
    1111
    12 I attempted to run the classic triangles.py example script, and received an ImportError. The same error appears regardless of whether or not the thinkpad is connected to the chassis, leading me to believe the problem is a dead battery. I tried both batteries with identical results. I would like the charge the batteries and see if we can make this thing move tomorrow, but I’m unsure which of the many adapters lying around are correct. Ivan is characteristically unfindable.
     12I attempted to run the classic ''triangles.py'' example script, and received an ImportError. The same error appears regardless of whether or not the thinkpad is connected to the chassis, leading me to believe the problem is a dead battery. I tried both batteries with identical results. I would like the charge the batteries and see if we can make this thing move tomorrow, but I’m unsure which of the many adapters lying around are correct. Ivan is characteristically unfindable.
    1313
    1414 
     
    1616We downgraded from python 2.4 to 2.3 on Mobile 33. The labtop can now power the chassis via python! Great success.
    1717
    18 We have begun setting up Debian on Mobile 37. After the minimal install, we upgraded the kernel to 2.6.8-2-386. We then attempted to install the package xserver-xorg.
     18We have begun setting up Debian on Mobile 37. After the minimal install, we upgraded the kernel to ''2.6.8-2-386''. We then attempted to install the package ''xserver-xorg''.
    1919
    20 We copied the file xorg.conf from the working version on Mobile 33 using ssh. We still have issues with fonts. The needed font package was xfonts-base. Once this was done, the X server launched. We then installed the Gnome window manager.
     20We copied the file xorg.conf from the working version on Mobile 33 using ssh. We still have issues with fonts. The needed font package was ''xfonts-base''. Once this was done, the X server launched. We then installed the Gnome window manager.
    2121
    22 Python is a bit of an issue, as the scripts seem to expect python 2.3 whereas the software itself installs python 2.4. After much reconfiguring, some of which included switching window managers on Mobile 33 (now running KDE), the solution was found in the form of a symlink called libpython2.3.s.0.1 pointing to the corresponding python 2.4 file in /usr/lib.
     22Python is a bit of an issue, as the scripts seem to expect python 2.3 whereas the software itself installs python 2.4. After much reconfiguring, some of which included switching window managers on Mobile 33 (now running KDE), the solution was found in the form of a symlink called ''libpython2.3.s.0.1'' pointing to the corresponding python 2.4 file in ''/usr/lib''.
    2323
    24 Some more packages were required in order to successfully compile the sample c++ code. Namely build-essential and libstdc++5. Once compiled, the example 01-simple executed and turned the robot’s wheels. This is the first time I’ve successfully controlled the robot using c++ code. One observation that I’ve made is that the code will not compile passed to gcc on its own; the make command must be used. This makes it necessary for us to generate makefiles for our own programs – something I currently know nothing about.
     24Some more packages were required in order to successfully compile the sample c++ code. Namely ''build-essential'' and ''libstdc++5''. Once compiled, the example 01-simple executed and turned the robot’s wheels. This is the first time I’ve successfully controlled the robot using c++ code. One observation that I’ve made is that the code will not compile passed to gcc on its own; the ''make'' command must be used. This makes it necessary for us to generate makefiles for our own programs – something I currently know nothing about.
    2525
    26 I spent a large part of the afternoon trying, unsuccessfully, to test the camera. ERSP comes with a binary package called test¬¬_camera, which gives several hints at the problem. I don’t know the specific model name of the camera we are using, and google is not being very helpful either.
     26I spent a large part of the afternoon trying, unsuccessfully, to test the camera. ERSP comes with a binary package called ''test¬¬_camera'', which gives several hints at the problem. I don’t know the specific model name of the camera we are using, and google is not being very helpful either.
    2727
    2828One goal for tomorrow is to obtain printouts of the User’s Guide and Programming Tutorials.