raarenst's profile - activity

overview network karma followed questions activity

2021-05-14 06:56:18 -0500	received badge	● Famous Question (source)
2019-02-17 01:43:41 -0500	received badge	● Notable Question (source)
2019-02-17 01:43:41 -0500	received badge	● Popular Question (source)
2017-10-09 20:48:46 -0500	received badge	● Student (source)
2017-02-18 13:33:52 -0500	asked a question	robot_startup errors I'm trying to install a launch-file to run at boot on my odroid (lubuntu). It use face detection (opencv) and audio for pocket-shinx for speech recognizer. Looking at the log file my launch file is executed but I get warning/errors. The launch file works when I run it manually. The errors are: (MyVideo:3247): Gtk-WARNING **: cannot open display: [face_detector-4] process has died ... ... [ERROR] [WallTime: ...] Error processing request: no element "PulseAudio" Seems like the display is not set up here and PauleAudio is not found. Do I need to wait until they have started? Synchnize in some way or do I need to setup some additional environment variables? Permissions?
2015-10-19 05:36:22 -0500	commented answer	Sourcing from multiple workspaces I also need to remove the build folder. Under step 2: rm -r build
2015-09-12 09:29:09 -0500	commented answer	Kinect isn't visible from Odroid when battery powered (turtlebot v2) Changing regulators didn't help. I have also tried with a odroid U2 and same issue. However, I have found that it happens only when the battery is running low. It could be that the power to the kinect isn't enough for it and that the odroid works perfectly. Everything else works for quite some time.
2015-03-01 15:34:01 -0500	commented answer	Kinect isn't visible from Odroid when battery powered (turtlebot v2) Yes, that makes sense. However, the hardkernel power supply is the only soruce that works and it is 5V/2A. Maybe it is some transient thing. I will use better DC/DC and make sure 3A is possible. Let's see what happens.
2015-03-01 04:23:06 -0500	answered a question	Kinect isn't visible from Odroid when battery powered (turtlebot v2) After some more measurements I see that when running on battery there are loads of USB error messages during startup. Then the voltage on the USB port becomes 4.2 V, while power from a DC/DC step down regulator fed into odroid is 5.25V. Still all other USB devices works well (WiFi, camera), but not the kinect. Current to kinect is 0 A. [Later] It didn't work with better (at least more expensive) regulators. First I thought it worked then I realized that the charging cable to the kobuki was attached. So it still doesn't work when running kobuki on battieries but it works when charging is attached. I use 2 5V/3A regulators to the 12V/5A kubuki port. Could it be a ground problem??
2015-03-01 04:19:49 -0500	received badge	● Notable Question (source)
2015-03-01 04:19:49 -0500	received badge	● Famous Question (source)
2015-02-10 20:28:03 -0500	received badge	● Famous Question (source)
2015-02-10 17:54:04 -0500	received badge	● Supporter (source)
2015-02-10 17:53:44 -0500	commented answer	Robot_upstart Thanks, it worked fine from source! Is there a recommended way to remove an upstart job?
2015-02-10 01:35:56 -0500	received badge	● Notable Question (source)
2015-02-09 21:58:04 -0500	commented question	Robot_upstart I have changed to pkg/path: odroid@odroidU2a:~$ rosrun robot_upstart install counter/launch/counterstart.launch --interface wlan2 but still the same thing.
2015-02-09 20:47:40 -0500	received badge	● Popular Question (source)
2015-02-08 14:14:27 -0500	asked a question	Robot_upstart After quite some search I think robot_upstart would be the best way to call a launch file during boot. Howeve, it seems to be hard to get up and running. The documentation is about usage but installation seems to be an issue (for me at least). I'm running ROS indigo on an odroid U2. I have a launch file created basically from the tutorials and a cpp project with a counter as service and publisher. I can run the launchfile and it starts up fine. I can call the service from another odroid as well, so that part seems to work fine. I installed the ros-indigo-robot-upstart package with apt-get. rosrun didn't find it so I made a rosbuild robot_update. Now rosrun finds it. Then I try to run: odroid@odroidU2a:~$ rosrun robot_upstart install RosProjects/catkin_ws/src/counter/launch/counterstart.launch --interface wlan2 sudo: a password is required Re-invoking installation script as root. [sudo] password for odroid: grep: Invalid range end grep: Invalid range end grep: Invalid range end grep: Invalid range end /opt/ros/indigo/lib/robot_upstart/install: line 136: source: /bin/true: cannot execute binary file Installing odroidindigo job using network interface true. /opt/ros/indigo/lib/robot_upstart/install: line 153: rosrun: command not found /opt/ros/indigo/lib/robot_upstart/install: line 154: rosrun: command not found /opt/ros/indigo/lib/robot_upstart/install: line 155: rosrun: command not found /opt/ros/indigo/lib/robot_upstart/install: line 162: rospd: command not found Adding files to odroidindigo job: odroidindigo/home/odroid/RosProjects/catkin_ws/devel/setup.bashRosProjects/catkin_ws/src/counter/launch/counterstart.launchwlan2/* /opt/ros/indigo/lib/robot_upstart/install: line 168: pushd: home/odroid/RosProjects/catkin_ws/devel/setup.bashRosProjects/catkin_ws/src/counter/launch/counterstart.launchwlan2: No such file or directory cp: omitting directory 'etc' cp: omitting directory 'include' cp: omitting directory 'lib' cp: omitting directory 'share' /opt/ros/indigo/lib/robot_upstart/install: line 170: popd: directory stack empty /opt/ros/indigo/lib/robot_upstart/install: line 172: popd: directory stack empty I'm completely lost here. Anyone having an idea what could be wrong? As it seems it can't identify rosrun from sudo I have also tried to invoke the command as root and source the ros setup.bash. Then I get: root@odroidU2a:/home/odroid# rosrun robot_upstart install /home/odroid/RosProjects/catkin_ws/src/counter/launch/counterstart.launch --interface wlan2 bash: rosrun: command not found root@odroidU2a:/home/odroid# source /opt/ros/indigo/setup.bash root@odroidU2a:/home/odroid# rosrun robot_upstart install /home/odroid/RosProjects/catkin_ws/src/counter/launch/counterstart.launch --interface wlan2 grep: Invalid range end /opt/ros/indigo/lib/robot_upstart/install: line 136: source: filename argument required source: usage: source filename [arguments] Installing job using network interface true. usage: start_gen [-h] --setup SETUP --rosdistro ROSDISTRO --job JOB --master MASTER --user USER --interface INTERFACE [outfile] start_gen: error: argument --job: expected one argument usage: stop_gen [-h] --job JOB [outfile] stop_gen: error: argument --job: expected one argument usage: job_conf_gen [-h] --interface INTERFACE --job JOB [outfile] job_conf_gen: error: argument --job: expected one ... (more)
2015-02-05 09:43:10 -0500	received badge	● Popular Question (source)
2015-02-05 09:43:07 -0500	received badge	● Enthusiast
2015-01-31 15:44:02 -0500	asked a question	Kinect isn't visible from Odroid when battery powered (turtlebot v2) I have a problem with my turtlebot 2 that is driven by an odroid U3. The problem is that the Kinect isn’t visible from the odroid. The odroid is powered from the 12V/5A connector on the kobuki base. There is a LM2596, 5V voltage regulator between. If I disconnect the voltage regulator and istead drive the odroid with a wall power supply is works perfectly. The current from the 12V source at the base is is measured to 1.5A, so current should be enough. To test I have also driven the odroid with an external 5V powerpack (charging unit for mobile devices 12000mAh, max current 3.4A), that didn’t work either. With not working I mean that the Kinect isn’t visible from the odroid, everything else works perfectly. There are a lot of other stuff on as well; screen, 11 IR sensors, mic and camera. Everything works well regardless of power source, except the Kinect that doesn’t work when the odroid is battery driven. Everything except the things in the figure below are now disconnected not to interfere. I have no clue and I have tested and measured everything I can think of, any ideas?