From: Regis V. <vincent@AI.SRI.COM> - 2009-02-14 01:15:55
|
hi, After fighting for couple weeks on getting our new segway working with Karto, I have created a webpage that hopefully capture all you have to do to get this robot to work under player 2.1.x The URL is http://www.ai.sri.com/~vincent/segway.php R. |
From: Joshua S <Jos...@ou...> - 2009-03-14 20:05:19
|
I have been working through the guide and every step has worked except : "Edit Makefile to add -lftd2xx next to -lcanbus (look for -lcanbus and then add -lftd2xx next to it. There is 3 occurences in my case ) build player by typing make." I have been unable to find any references to -lcanbus in any of the Makefiles. Does anyone know why this may be? Thanks, Josh Regis Vincent wrote: > > hi, > > After fighting for couple weeks on getting our new segway working with > Karto, I have created a webpage that hopefully capture all you have to > do to get this robot to work under player 2.1.x > > The URL is http://www.ai.sri.com/~vincent/segway.php > > R. > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, > CA > -OSBC tackles the biggest issue in open source: Open Sourcing the > Enterprise > -Strategies to boost innovation and cut costs with open source > participation > -Receive a $600 discount off the registration fee with the source code: > SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > > -- View this message in context: http://www.nabble.com/Player-2.1.x-on-a-USB-segway-RMP-50-tp22007997p22516534.html Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Joshua S <Jos...@ou...> - 2009-03-18 19:59:20
|
I have gotten things working, which required a slightly different setup. Because I didn't have any Makefile references to -lcanbus I had to initially modify <player-dir>/server/Makefile line to: LIBS = -lpthread -lrt -lnsl -lcrypto -lraw1394 -lz -lltdl -ldl -ljpeg -lGL -lGLU -lftd2xx I had problems at runtime because check_device exists in both player(setpwc_api) and in ftd2xx. I modified the function check_device() as it is defined in setpwc_api.[c/h] to setpwc_check_device() to keep ftd2xx from calling the wrong check_device. Next time I compile I will try to target the ftd2xx linking with more precision to avoid this problem. Thanks to everyone who worked on getting this together. Josh Joshua S wrote: > > I have been working through the guide and every step has worked except : > > "Edit Makefile to add -lftd2xx next to -lcanbus (look for -lcanbus and > then add -lftd2xx next to it. There is 3 occurences in my case ) build > player by typing make." > > I have been unable to find any references to -lcanbus in any of the > Makefiles. Does anyone know why this may be? > > Thanks, > > Josh > > > > Regis Vincent wrote: >> >> hi, >> >> After fighting for couple weeks on getting our new segway working with >> Karto, I have created a webpage that hopefully capture all you have to >> do to get this robot to work under player 2.1.x >> >> The URL is http://www.ai.sri.com/~vincent/segway.php >> >> R. >> >> ------------------------------------------------------------------------------ >> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, >> CA >> -OSBC tackles the biggest issue in open source: Open Sourcing the >> Enterprise >> -Strategies to boost innovation and cut costs with open source >> participation >> -Receive a $600 discount off the registration fee with the source code: >> SFAD >> http://p.sf.net/sfu/XcvMzF8H >> _______________________________________________ >> Playerstage-users mailing list >> Pla...@li... >> https://lists.sourceforge.net/lists/listinfo/playerstage-users >> >> > > -- View this message in context: http://www.nabble.com/Player-2.1.x-on-a-USB-segway-RMP-50-tp22007997p22587295.html Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Todd F. <tf...@gc...> - 2009-04-09 04:15:15
|
Hi, I have an RMP 100 that I've been following the instructions for (using ubuntu) and encountered the same issue you mentioned. I made the changes that you suggested but I'm still not getting the connection completely set up. When attempting to run the joystick.cfg, I'm getting "error (-1) reading packet on channel 0" and "error on write" messages after attempting to send the 0 speed information. I am not certain if this is a canbus error or from player itself, but it is clearly not working. All other aspects of the instructions seemed to work. I have the devices connected via USB successfully. I'm wondering if there's something obvious I've done wrong or if this is something you've encountered or if this might be something specific to using the RMP 100. I am trying to use it in balance mode, which might be making a difference. Any insight would help. Thanks in advance. -Todd Joshua S wrote: > > I have gotten things working, which required a slightly different setup. > Because I didn't have any Makefile references to -lcanbus I had to > initially modify <player-dir>/server/Makefile line to: > LIBS = -lpthread -lrt -lnsl -lcrypto -lraw1394 -lz -lltdl -ldl -ljpeg > -lGL -lGLU -lftd2xx > > I had problems at runtime because check_device exists in both > player(setpwc_api) and in ftd2xx. I modified the function check_device() > as it is defined in setpwc_api.[c/h] to setpwc_check_device() to keep > ftd2xx from calling the wrong check_device. Next time I compile I will > try to target the ftd2xx linking with more precision to avoid this > problem. > > Thanks to everyone who worked on getting this together. > > Josh > > -- View this message in context: http://www.nabble.com/Player-2.1.x-on-a-USB-segway-RMP-50-tp22007997p22964163.html Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Sumita S. <sum...@gm...> - 2009-05-01 23:41:11
|
Hi, I´ve been working on an RMP 50 and am still at the compile/install stage of operations. Here are the problems I´ve been encountering: Player wouldn´t compile because it didn´t recognize canio_rmpusb.o. I had to go in and make some minor adjustments to Makefiles in server/drivers/mixed/rmp and the Player root directory to make sure canio_rmpusb produced the object file and then carry on installing. Now, however, I am trying to make install Player as a whole, and this is the error I get: ../server/libplayerdrivers/.libs/libplayerdrivers.so: undefined reference to `CANIOrmpusb::CANIOrmpusb()' This is because I haven´t been able to get linuxcan installed - and this is the error I get for attempting that: building PCIcan Kernel src: /lib/modules/2.6.24-23-generic/build -------------------------------------------------------------------- cd ./pcican cp ./pcican/Makefile_26 ./pcican/Makefile -f make -C /lib/modules/`uname -r`/build SUBDIRS=/pcican modules KV_DEBUG_ON=0 make[1]: Entering directory `/usr/src/linux-headers-2.6.24-23-generic' scripts/Makefile.build:41: /pcican/Makefile: No such file or directory make[2]: *** No rule to make target `/pcican/Makefile'. Stop. I have no idea what this error is, and have tried everything from checking the Makefiles to installing Linux source code. As I´m a completely newbie and not familiar with Makefile/configure though I am probably missing something obvious. Any help would be greatly appreciated. Sumita On Wed, Apr 8, 2009 at 11:15 PM, Todd Flyr <tf...@gc...> wrote: > > > Hi, > I have an RMP 100 that I've been following the instructions for (using > ubuntu) and encountered the same issue you mentioned. I made the changes > that you suggested but I'm still not getting the connection completely set > up. When attempting to run the joystick.cfg, I'm getting "error (-1) > reading packet on channel 0" and "error on write" messages after attempting > to send the 0 speed information. I am not certain if this is a canbus > error > or from player itself, but it is clearly not working. All other aspects of > the instructions seemed to work. I have the devices connected via USB > successfully. I'm wondering if there's something obvious I've done wrong > or > if this is something you've encountered or if this might be something > specific to using the RMP 100. I am trying to use it in balance mode, > which > might be making a difference. > > Any insight would help. Thanks in advance. > > -Todd > > > > Joshua S wrote: > > > > I have gotten things working, which required a slightly different setup. > > Because I didn't have any Makefile references to -lcanbus I had to > > initially modify <player-dir>/server/Makefile line to: > > LIBS = -lpthread -lrt -lnsl -lcrypto -lraw1394 -lz -lltdl -ldl -ljpeg > > -lGL -lGLU -lftd2xx > > > > I had problems at runtime because check_device exists in both > > player(setpwc_api) and in ftd2xx. I modified the function check_device() > > as it is defined in setpwc_api.[c/h] to setpwc_check_device() to keep > > ftd2xx from calling the wrong check_device. Next time I compile I will > > try to target the ftd2xx linking with more precision to avoid this > > problem. > > > > Thanks to everyone who worked on getting this together. > > > > Josh > > > > > -- > View this message in context: > http://www.nabble.com/Player-2.1.x-on-a-USB-segway-RMP-50-tp22007997p22964163.html > Sent from the playerstage-users mailing list archive at Nabble.com. > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > -- Sumita Sami Editor-in-Chief, Nazar - A South Asian Perspective Electrical and Computer Engineering/Plan II University of Texas at Austin |
From: Todd F. <tf...@gc...> - 2009-05-14 20:55:41
|
Sumita, Don't know if you solved this yet, but the problem is the pathing in the makefile of the drivers. In the settings.mak file configure DRIVER_TOP_DIR to be the absolute path to the linuxcan directory. Then substitute DRIVER_TOP_DIR for PWD for in the Makefile. This should allow all the install scripts to build. There's possibly a better way to do this, but this is what worked for me. -Todd S Sami wrote: > > Hi, > > I´ve been working on an RMP 50 and am still at the compile/install stage > of > operations. Here are the problems I´ve been encountering: > > Player wouldn´t compile because it didn´t recognize canio_rmpusb.o. I had > to > go in and make some minor adjustments to Makefiles in > server/drivers/mixed/rmp and the Player root directory to make sure > canio_rmpusb produced the object file and then carry on installing. > > Now, however, I am trying to make install Player as a whole, and this is > the > error I get: > > ../server/libplayerdrivers/.libs/libplayerdrivers.so: undefined reference > to > `CANIOrmpusb::CANIOrmpusb()' > > This is because I haven´t been able to get linuxcan installed - and this > is > the error I get for attempting that: > > building PCIcan > Kernel src: /lib/modules/2.6.24-23-generic/build > -------------------------------------------------------------------- > cd ./pcican > cp ./pcican/Makefile_26 ./pcican/Makefile -f > make -C /lib/modules/`uname -r`/build SUBDIRS=/pcican modules > KV_DEBUG_ON=0 > make[1]: Entering directory `/usr/src/linux-headers-2.6.24-23-generic' > scripts/Makefile.build:41: /pcican/Makefile: No such file or directory > make[2]: *** No rule to make target `/pcican/Makefile'. Stop. > > > I have no idea what this error is, and have tried everything from checking > the Makefiles to installing Linux source code. As I´m a completely newbie > and not familiar with Makefile/configure though I am probably missing > something obvious. > > Any help would be greatly appreciated. > > > Sumita > > -- View this message in context: http://www.nabble.com/Player-2.1.x-on-a-USB-segway-RMP-50-tp22007997p23548832.html Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Sumita S. <sum...@gm...> - 2009-06-02 22:03:17
|
Todd, That worked perfectly, thank you. One thing I realized after some failed attempts was that DRIVER_TOP_DIR is actually commented out. Thanks again! Sumita On Thu, May 14, 2009 at 3:55 PM, Todd Flyr <tf...@gc...> wrote: > > > Sumita, > Don't know if you solved this yet, but the problem is the pathing in the > makefile of the drivers. > > In the settings.mak file configure DRIVER_TOP_DIR to be the absolute path > to > the linuxcan directory. > > Then substitute DRIVER_TOP_DIR for PWD for in the Makefile. This should > allow all the install scripts to build. > > There's possibly a better way to do this, but this is what worked for me. > > -Todd > > > S Sami wrote: > > > > Hi, > > > > I´ve been working on an RMP 50 and am still at the compile/install stage > > of > > operations. Here are the problems I´ve been encountering: > > > > Player wouldn´t compile because it didn´t recognize canio_rmpusb.o. I had > > to > > go in and make some minor adjustments to Makefiles in > > server/drivers/mixed/rmp and the Player root directory to make sure > > canio_rmpusb produced the object file and then carry on installing. > > > > Now, however, I am trying to make install Player as a whole, and this is > > the > > error I get: > > > > ../server/libplayerdrivers/.libs/libplayerdrivers.so: undefined reference > > to > > `CANIOrmpusb::CANIOrmpusb()' > > > > This is because I haven´t been able to get linuxcan installed - and this > > is > > the error I get for attempting that: > > > > building PCIcan > > Kernel src: /lib/modules/2.6.24-23-generic/build > > -------------------------------------------------------------------- > > cd ./pcican > > cp ./pcican/Makefile_26 ./pcican/Makefile -f > > make -C /lib/modules/`uname -r`/build SUBDIRS=/pcican modules > > KV_DEBUG_ON=0 > > make[1]: Entering directory `/usr/src/linux-headers-2.6.24-23-generic' > > scripts/Makefile.build:41: /pcican/Makefile: No such file or directory > > make[2]: *** No rule to make target `/pcican/Makefile'. Stop. > > > > > > I have no idea what this error is, and have tried everything from > checking > > the Makefiles to installing Linux source code. As I´m a completely newbie > > and not familiar with Makefile/configure though I am probably missing > > something obvious. > > > > Any help would be greatly appreciated. > > > > > > Sumita > > > > > > -- > View this message in context: > http://www.nabble.com/Player-2.1.x-on-a-USB-segway-RMP-50-tp22007997p23548832.html > Sent from the playerstage-users mailing list archive at Nabble.com. > > > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK > i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > -- Sumita Sami Editor-in-Chief, Nazar - A South Asian Perspective Electrical and Computer Engineering/Plan II University of Texas at Austin |
From: Drew_S <dst...@ma...> - 2009-12-17 22:15:16
|
Any luck resolving this error? (I'm getting the same error) Based on the Knowledgebase at ftdichip.com, I updated my version of canio_rmpusb.cc to list all the connected devices. Turns out that I have no devices. I suspect that this is the root of the "error (-1)" problem that I'm having, but I'm not sure how to fix it. My Segway is turned on and connected. The results of "dmesg | grep FTDI" look promising. After that, I'm not sure what else to do to debug the problem... -Drew My code is exactly the same as the documentation found on this site: http://www.ftdichip.com/Support/Knowledgebase/index.html?ft_listdevices.htm ListDevices Function Documentation The results of the dmesg test: $ dmesg | grep FTDI [ 123.146256] USB Serial support registered for FTDI USB Serial Device [ 123.146325] ftdi_sio 1-6.3:1.0: FTDI USB Serial Device converter detected [ 123.146540] usb 1-6.3: FTDI USB Serial Device converter now attached to ttyUSB0 [ 123.146559] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver Todd Flyr wrote: > > > Hi, > I have an RMP 100 that I've been following the instructions for (using > ubuntu) and encountered the same issue you mentioned. I made the changes > that you suggested but I'm still not getting the connection completely set > up. When attempting to run the joystick.cfg, I'm getting "error (-1) > reading packet on channel 0" and "error on write" messages after > attempting to send the 0 speed information. I am not certain if this is a > canbus error or from player itself, but it is clearly not working. All > other aspects of the instructions seemed to work. I have the devices > connected via USB successfully. I'm wondering if there's something > obvious I've done wrong or if this is something you've encountered or if > this might be something specific to using the RMP 100. I am trying to use > it in balance mode, which might be making a difference. > > Any insight would help. Thanks in advance. > > -Todd > > > > Joshua S wrote: >> >> I have gotten things working, which required a slightly different setup. >> Because I didn't have any Makefile references to -lcanbus I had to >> initially modify <player-dir>/server/Makefile line to: >> LIBS = -lpthread -lrt -lnsl -lcrypto -lraw1394 -lz -lltdl -ldl -ljpeg >> -lGL -lGLU -lftd2xx >> >> I had problems at runtime because check_device exists in both >> player(setpwc_api) and in ftd2xx. I modified the function check_device() >> as it is defined in setpwc_api.[c/h] to setpwc_check_device() to keep >> ftd2xx from calling the wrong check_device. Next time I compile I will >> try to target the ftd2xx linking with more precision to avoid this >> problem. >> >> Thanks to everyone who worked on getting this together. >> >> Josh >> >> > -- View this message in context: http://old.nabble.com/Player-2.1.x-on-a-USB-segway-RMP-50-tp22007997p26835956.html Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Rich M. <jp...@gm...> - 2009-12-17 23:30:07
|
The original segwayrmp driver isn't compatible with the Segway USB controller board. The RMP's USB interface board is providing a USB to serial (not USB to CAN) converter, which is why you see ttyUSB0 (a USB serial port). The driver is looking for a CAN device, and failing because you don't have one connected. The original RMP's didn't have a USB port, just a CAN connection. You had to get some sort of USB to CAN converter like one from Kvaser in order to communicate with the RMPs. That's what the original segwayrmp driver was designed to do. To use the USB interface board, you have to open a serial connection at /dev/ttyUSBx, and send CAN packets over the serial connection. It is a little counter-intuitive. Luckily, Player 3.0 contains an updated RMP driver with a USB interface option. We built it to work with the RMP200 and 400, but my understanding is that all of the RMPs have the same USB interface board. The RMP Interface guide says that the RMP50 & 100 use some different velocity, torque, and position scaling factors than the RMP200 & 400, but that'll only affect the readings you get out of the driver. You can modify the scaling factors at the top of rmp_frame.h. It wouldn't be too hard to backport the 3.0 "segwayrmp" driver to Player 2.1 and use it as a plugin. I used it extensively with the RMP400 in player 2.1, with the stock FTDI driver in Fedora 11 (I created a udev rule to modprobe ftdi_sio with the correct product and vendor IDs). Then ported it to 3.0 and tested it briefly before contributing the patch. It looks like the documentation page is way out of date, so I'm adding a sample configuration file if you succeed in backporting the driver or upgrading to Player 3.0. And looking over segwayrmp.cc, it seems like it's possible to remove all association with canio_kvaser so you don't need their canlib headers and libraries. Rich driver ( name "segwayrmp" plugin "/path/to/libsegwayrmp.so" provides ["position2d:0" "position3d:0" "power:0"] bus "usb" usb_device "/dev/ttyUSB0" max_xspeed 1.5 max_yawspeed 80 ) On 12/17/2009 05:15 PM, Drew_S wrote: > > Any luck resolving this error? (I'm getting the same error) > > Based on the Knowledgebase at ftdichip.com, I updated my version of > canio_rmpusb.cc to list all the connected devices. Turns out that I have no > devices. > > I suspect that this is the root of the "error (-1)" problem that I'm having, > but I'm not sure how to fix it. My Segway is turned on and connected. The > results of "dmesg | grep FTDI" look promising. After that, I'm not sure > what else to do to debug the problem... > > -Drew > > My code is exactly the same as the documentation found on this site: > http://www.ftdichip.com/Support/Knowledgebase/index.html?ft_listdevices.htm > ListDevices Function Documentation > > The results of the dmesg test: > $ dmesg | grep FTDI > [ 123.146256] USB Serial support registered for FTDI USB Serial Device > [ 123.146325] ftdi_sio 1-6.3:1.0: FTDI USB Serial Device converter detected > [ 123.146540] usb 1-6.3: FTDI USB Serial Device converter now attached to > ttyUSB0 > [ 123.146559] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver > > > > Todd Flyr wrote: >> >> >> Hi, >> I have an RMP 100 that I've been following the instructions for (using >> ubuntu) and encountered the same issue you mentioned. I made the changes >> that you suggested but I'm still not getting the connection completely set >> up. When attempting to run the joystick.cfg, I'm getting "error (-1) >> reading packet on channel 0" and "error on write" messages after >> attempting to send the 0 speed information. I am not certain if this is a >> canbus error or from player itself, but it is clearly not working. All >> other aspects of the instructions seemed to work. I have the devices >> connected via USB successfully. I'm wondering if there's something >> obvious I've done wrong or if this is something you've encountered or if >> this might be something specific to using the RMP 100. I am trying to use >> it in balance mode, which might be making a difference. >> >> Any insight would help. Thanks in advance. >> >> -Todd >> >> >> >> Joshua S wrote: >>> >>> I have gotten things working, which required a slightly different setup. >>> Because I didn't have any Makefile references to -lcanbus I had to >>> initially modify<player-dir>/server/Makefile line to: >>> LIBS = -lpthread -lrt -lnsl -lcrypto -lraw1394 -lz -lltdl -ldl -ljpeg >>> -lGL -lGLU -lftd2xx >>> >>> I had problems at runtime because check_device exists in both >>> player(setpwc_api) and in ftd2xx. I modified the function check_device() >>> as it is defined in setpwc_api.[c/h] to setpwc_check_device() to keep >>> ftd2xx from calling the wrong check_device. Next time I compile I will >>> try to target the ftd2xx linking with more precision to avoid this >>> problem. >>> >>> Thanks to everyone who worked on getting this together. >>> >>> Josh >>> >>> >> > |
From: Drew S. <dst...@ma...> - 2009-12-23 17:31:17
|
Found the answer to my own question. The error message "error (-1) reading packet on channel 0" is indeed related to the FTDI driver not being able to find the RMP. The source of this particular problem was simply access control. By executing as root (sudo player foo.cfg), the player server was able to find and connect to the RMP. -Drew On Thu, Dec 17, 2009 at 4:15 PM, Drew_S <dst...@ma...> wrote: > > Any luck resolving this error? (I'm getting the same error) > > Based on the Knowledgebase at ftdichip.com, I updated my version of > canio_rmpusb.cc to list all the connected devices. Turns out that I have > no > devices. > > I suspect that this is the root of the "error (-1)" problem that I'm > having, > but I'm not sure how to fix it. My Segway is turned on and connected. The > results of "dmesg | grep FTDI" look promising. After that, I'm not sure > what else to do to debug the problem... > > -Drew > > My code is exactly the same as the documentation found on this site: > http://www.ftdichip.com/Support/Knowledgebase/index.html?ft_listdevices.htm > ListDevices Function Documentation > > The results of the dmesg test: > $ dmesg | grep FTDI > [ 123.146256] USB Serial support registered for FTDI USB Serial Device > [ 123.146325] ftdi_sio 1-6.3:1.0: FTDI USB Serial Device converter > detected > [ 123.146540] usb 1-6.3: FTDI USB Serial Device converter now attached to > ttyUSB0 > [ 123.146559] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver > > > > Todd Flyr wrote: > > > > > > Hi, > > I have an RMP 100 that I've been following the instructions for (using > > ubuntu) and encountered the same issue you mentioned. I made the changes > > that you suggested but I'm still not getting the connection completely > set > > up. When attempting to run the joystick.cfg, I'm getting "error (-1) > > reading packet on channel 0" and "error on write" messages after > > attempting to send the 0 speed information. I am not certain if this is > a > > canbus error or from player itself, but it is clearly not working. All > > other aspects of the instructions seemed to work. I have the devices > > connected via USB successfully. I'm wondering if there's something > > obvious I've done wrong or if this is something you've encountered or if > > this might be something specific to using the RMP 100. I am trying to > use > > it in balance mode, which might be making a difference. > > > > Any insight would help. Thanks in advance. > > > > -Todd > > > > > > > > Joshua S wrote: > >> > >> I have gotten things working, which required a slightly different setup. > >> Because I didn't have any Makefile references to -lcanbus I had to > >> initially modify <player-dir>/server/Makefile line to: > >> LIBS = -lpthread -lrt -lnsl -lcrypto -lraw1394 -lz -lltdl -ldl -ljpeg > >> -lGL -lGLU -lftd2xx > >> > >> I had problems at runtime because check_device exists in both > >> player(setpwc_api) and in ftd2xx. I modified the function check_device() > >> as it is defined in setpwc_api.[c/h] to setpwc_check_device() to keep > >> ftd2xx from calling the wrong check_device. Next time I compile I will > >> try to target the ftd2xx linking with more precision to avoid this > >> problem. > >> > >> Thanks to everyone who worked on getting this together. > >> > >> Josh > >> > >> > > > > -- > View this message in context: > http://old.nabble.com/Player-2.1.x-on-a-USB-segway-RMP-50-tp22007997p26835956.html > Sent from the playerstage-users mailing list archive at Nabble.com. > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > |
From: Wu H. <wu....@gm...> - 2011-01-13 02:39:47
|
Greetings all The url http://www.ai.sri.com/~vincent/segway.php <http://www.ai.sri.com/%7Evincent/segway.php>returns a forbidden access. Is there a new url for it? Best Regards Hengxin Wu Institute for Infocomm Research A*star On Thu, Dec 24, 2009 at 1:30 AM, Drew Stovall <dst...@ma...>wrote: > Found the answer to my own question. The error message "error > (-1) reading packet on channel 0" is indeed related to the FTDI driver not > being able to find the RMP. The source of this particular problem was > simply access control. By executing as root (sudo player foo.cfg), the > player server was able to find and connect to the RMP. > > -Drew > > On Thu, Dec 17, 2009 at 4:15 PM, Drew_S <dst...@ma...> wrote: > >> >> Any luck resolving this error? (I'm getting the same error) >> >> Based on the Knowledgebase at ftdichip.com, I updated my version of >> canio_rmpusb.cc to list all the connected devices. Turns out that I have >> no >> devices. >> >> I suspect that this is the root of the "error (-1)" problem that I'm >> having, >> but I'm not sure how to fix it. My Segway is turned on and connected. >> The >> results of "dmesg | grep FTDI" look promising. After that, I'm not sure >> what else to do to debug the problem... >> >> -Drew >> >> My code is exactly the same as the documentation found on this site: >> >> http://www.ftdichip.com/Support/Knowledgebase/index.html?ft_listdevices.htm >> ListDevices Function Documentation >> >> The results of the dmesg test: >> $ dmesg | grep FTDI >> [ 123.146256] USB Serial support registered for FTDI USB Serial Device >> [ 123.146325] ftdi_sio 1-6.3:1.0: FTDI USB Serial Device converter >> detected >> [ 123.146540] usb 1-6.3: FTDI USB Serial Device converter now attached to >> ttyUSB0 >> [ 123.146559] ftdi_sio: v1.5.0:USB FTDI Serial Converters Driver >> >> >> >> Todd Flyr wrote: >> > >> > >> > Hi, >> > I have an RMP 100 that I've been following the instructions for (using >> > ubuntu) and encountered the same issue you mentioned. I made the >> changes >> > that you suggested but I'm still not getting the connection completely >> set >> > up. When attempting to run the joystick.cfg, I'm getting "error (-1) >> > reading packet on channel 0" and "error on write" messages after >> > attempting to send the 0 speed information. I am not certain if this is >> a >> > canbus error or from player itself, but it is clearly not working. All >> > other aspects of the instructions seemed to work. I have the devices >> > connected via USB successfully. I'm wondering if there's something >> > obvious I've done wrong or if this is something you've encountered or if >> > this might be something specific to using the RMP 100. I am trying to >> use >> > it in balance mode, which might be making a difference. >> > >> > Any insight would help. Thanks in advance. >> > >> > -Todd >> > >> > >> > >> > Joshua S wrote: >> >> >> >> I have gotten things working, which required a slightly different >> setup. >> >> Because I didn't have any Makefile references to -lcanbus I had to >> >> initially modify <player-dir>/server/Makefile line to: >> >> LIBS = -lpthread -lrt -lnsl -lcrypto -lraw1394 -lz -lltdl -ldl -ljpeg >> >> -lGL -lGLU -lftd2xx >> >> >> >> I had problems at runtime because check_device exists in both >> >> player(setpwc_api) and in ftd2xx. I modified the function >> check_device() >> >> as it is defined in setpwc_api.[c/h] to setpwc_check_device() to keep >> >> ftd2xx from calling the wrong check_device. Next time I compile I will >> >> try to target the ftd2xx linking with more precision to avoid this >> >> problem. >> >> >> >> Thanks to everyone who worked on getting this together. >> >> >> >> Josh >> >> >> >> >> > >> >> -- >> View this message in context: >> http://old.nabble.com/Player-2.1.x-on-a-USB-segway-RMP-50-tp22007997p26835956.html >> Sent from the playerstage-users mailing list archive at Nabble.com. >> >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Playerstage-users mailing list >> Pla...@li... >> https://lists.sourceforge.net/lists/listinfo/playerstage-users >> > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > > |
From: Rich M. <jp...@gm...> - 2011-01-13 16:19:49
|
> -----Original Message----- > From: Wu Hengxin [mailto:wu....@gm...] > Sent: Wednesday, January 12, 2011 9:39 PM > To: pla...@li... > Subject: Re: [Playerstage-users] Player 2.1.x on a USB segway RMP-50 > > Greetings all > > The url http://www.ai.sri.com/~vincent/segway.php > <http://www.ai.sri.com/%7Evincent/segway.php> returns a forbidden > access. Is there a new url for it? > > Best Regards > > Hengxin Wu > Institute for Infocomm Research > A*star FYI, Player 3.0 supports communicating with the Segway RMPs over USB. Have you tried the rmp driver included in Player 3? Rich |