From: Dongqing <don...@gm...> - 2008-01-09 17:39:16
|
configuration file: driver ( name "segwayrmp" provides ["position2d:0" "position3d:0" "power:0"] canio "kvaser" max_xspeed 4.5 max_yawspeed 80 ) driver ( name "sicklms200" provides ["laser:0"] port "/dev/ttyS0" ) driver ( name "vfh" requires ["position2d:0" "laser:0"] provides ["position2d:1"] safety_dist 0.10 distance_epsilon 0.3 angle_epsilon 5 ) ---------------------------------------------- code: #include <libplayerc++/playerc++.h> using namespace PlayerCc; int main(int argc, char **argv) { double newspeed = 0; double newturnrate = 0; /*********************** define the turn direction *****************/ // we throw exceptions on creation if we fail try { PlayerClient robot("localhost"); Position2dProxy pp(&robot, 0); Position2dProxy vfh(&robot, 1); pp.SetMotorEnable (true); vfh.SetMotorEnable (true); newspeed = 0.2; //m/s newturnrate = 0; player_pose_t pose; pose.px = 1.0; pose.py = 0; pose.pa = 0; vfh.SetSpeed(newspeed, newturnrate); vfh.GoTo(pose); } catch (PlayerCc::PlayerError e) { std::cerr << e << std::endl; return -1; } return 1; } ------------------------------------------------ compilation ok. running error: calling connect done playerc error : timed out waiting for server reply to request 1:0:3:3 playerc error : failed to get response Position2dProxy:: Position2dProxy()(-1): could not subscribe. I am not sure the way I subscribe the vfh is right or not. Thanks. Dongqing -- View this message in context: http://www.nabble.com/help-with-vfh-driver-tp14716531p14716531.html Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Toby C. <tco...@pl...> - 2008-01-10 21:20:31
|
Can you control the rmp with playerjoy or a simple client, simplify your config so you can isolate which driver is not behaving, Toby On 10/01/2008, Dongqing <don...@gm...> wrote: > > > configuration file: > > driver > ( > name "segwayrmp" > provides ["position2d:0" "position3d:0" "power:0"] > canio "kvaser" > max_xspeed 4.5 > max_yawspeed 80 > ) > > driver > ( > name "sicklms200" > provides ["laser:0"] > port "/dev/ttyS0" > ) > driver > ( > name "vfh" > requires ["position2d:0" "laser:0"] > provides ["position2d:1"] > safety_dist 0.10 > distance_epsilon 0.3 > angle_epsilon 5 > ) > ---------------------------------------------- > code: > > > > #include <libplayerc++/playerc++.h> > > using namespace PlayerCc; > > int main(int argc, char **argv) > { > double newspeed = 0; > double newturnrate = 0; > > /*********************** define the turn direction > *****************/ > > // we throw exceptions on creation if we fail > try > { > > PlayerClient robot("localhost"); > Position2dProxy pp(&robot, 0); > > > Position2dProxy vfh(&robot, 1); > > > pp.SetMotorEnable (true); > vfh.SetMotorEnable (true); > > > > newspeed = 0.2; //m/s > newturnrate = 0; > > player_pose_t pose; > pose.px = 1.0; > pose.py = 0; > pose.pa = 0; > > vfh.SetSpeed(newspeed, newturnrate); > vfh.GoTo(pose); > > > } > catch (PlayerCc::PlayerError e) > { > std::cerr << e << std::endl; > return -1; > } > return 1; > } > ------------------------------------------------ > > compilation ok. > running error: > calling connect > done > playerc error : timed out waiting for server reply to request 1:0:3:3 > playerc error : failed to get response > Position2dProxy:: Position2dProxy()(-1): could not subscribe. > > I am not sure the way I subscribe the vfh is right or not. > Thanks. > Dongqing > > -- > View this message in context: > http://www.nabble.com/help-with-vfh-driver-tp14716531p14716531.html > Sent from the playerstage-users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > -- This email is intended for the addressee only and may contain privileged and/or confidential information |
From: Dongqing <don...@gm...> - 2008-01-11 16:08:38
|
Hi Toby, Controlling my segway either joystick or a simple client program is ok. I am trying to test vfh on segway. I am not sure if I configured it correctly. It simply says cannot subscribe position2d of vfh. Dongqing Toby Collett-3 wrote: > > Can you control the rmp with playerjoy or a simple client, simplify your > config so you can isolate which driver is not behaving, > > Toby > > On 10/01/2008, Dongqing <don...@gm...> wrote: >> >> >> configuration file: >> >> driver >> ( >> name "segwayrmp" >> provides ["position2d:0" "position3d:0" "power:0"] >> canio "kvaser" >> max_xspeed 4.5 >> max_yawspeed 80 >> ) >> >> driver >> ( >> name "sicklms200" >> provides ["laser:0"] >> port "/dev/ttyS0" >> ) >> driver >> ( >> name "vfh" >> requires ["position2d:0" "laser:0"] >> provides ["position2d:1"] >> safety_dist 0.10 >> distance_epsilon 0.3 >> angle_epsilon 5 >> ) >> ---------------------------------------------- >> code: >> >> >> >> #include <libplayerc++/playerc++.h> >> >> using namespace PlayerCc; >> >> int main(int argc, char **argv) >> { >> double newspeed = 0; >> double newturnrate = 0; >> >> /*********************** define the turn direction >> *****************/ >> >> // we throw exceptions on creation if we fail >> try >> { >> >> PlayerClient robot("localhost"); >> Position2dProxy pp(&robot, 0); >> >> >> Position2dProxy vfh(&robot, 1); >> >> >> pp.SetMotorEnable (true); >> vfh.SetMotorEnable (true); >> >> >> >> newspeed = 0.2; //m/s >> newturnrate = 0; >> >> player_pose_t pose; >> pose.px = 1.0; >> pose.py = 0; >> pose.pa = 0; >> >> vfh.SetSpeed(newspeed, newturnrate); >> vfh.GoTo(pose); >> >> >> } >> catch (PlayerCc::PlayerError e) >> { >> std::cerr << e << std::endl; >> return -1; >> } >> return 1; >> } >> ------------------------------------------------ >> >> compilation ok. >> running error: >> calling connect >> done >> playerc error : timed out waiting for server reply to request 1:0:3:3 >> playerc error : failed to get response >> Position2dProxy:: Position2dProxy()(-1): could not subscribe. >> >> I am not sure the way I subscribe the vfh is right or not. >> Thanks. >> Dongqing >> >> -- >> View this message in context: >> http://www.nabble.com/help-with-vfh-driver-tp14716531p14716531.html >> Sent from the playerstage-users mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> >> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace >> _______________________________________________ >> Playerstage-users mailing list >> Pla...@li... >> https://lists.sourceforge.net/lists/listinfo/playerstage-users >> > > > > -- > This email is intended for the addressee only and may contain privileged > and/or confidential information > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > > -- View this message in context: http://www.nabble.com/help-with-vfh-driver-tp14716531p14759516.html Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Dongqing <don...@gm...> - 2008-01-11 16:20:35
|
Hi, Just try to make it clear. when I run # player *.cfg (including laser, segway, vfh). It is ok. But after a run the c code, it returned no subscribe. So maybe the subscribe code is not right. I did as follows: PlayerClient robot("localhost"); Position2dProxy pp(&robot, 0); LaserProxy lp(&robot, 0); Position2dProxy vfh(&robot, 1); .... Toby Collett-3 wrote: > > Can you control the rmp with playerjoy or a simple client, simplify your > config so you can isolate which driver is not behaving, > > Toby > > On 10/01/2008, Dongqing <don...@gm...> wrote: >> >> >> configuration file: >> >> driver >> ( >> name "segwayrmp" >> provides ["position2d:0" "position3d:0" "power:0"] >> canio "kvaser" >> max_xspeed 4.5 >> max_yawspeed 80 >> ) >> >> driver >> ( >> name "sicklms200" >> provides ["laser:0"] >> port "/dev/ttyS0" >> ) >> driver >> ( >> name "vfh" >> requires ["position2d:0" "laser:0"] >> provides ["position2d:1"] >> safety_dist 0.10 >> distance_epsilon 0.3 >> angle_epsilon 5 >> ) >> ---------------------------------------------- >> code: >> >> >> >> #include <libplayerc++/playerc++.h> >> >> using namespace PlayerCc; >> >> int main(int argc, char **argv) >> { >> double newspeed = 0; >> double newturnrate = 0; >> >> /*********************** define the turn direction >> *****************/ >> >> // we throw exceptions on creation if we fail >> try >> { >> >> PlayerClient robot("localhost"); >> Position2dProxy pp(&robot, 0); >> >> >> Position2dProxy vfh(&robot, 1); >> >> >> pp.SetMotorEnable (true); >> vfh.SetMotorEnable (true); >> >> >> >> newspeed = 0.2; //m/s >> newturnrate = 0; >> >> player_pose_t pose; >> pose.px = 1.0; >> pose.py = 0; >> pose.pa = 0; >> >> vfh.SetSpeed(newspeed, newturnrate); >> vfh.GoTo(pose); >> >> >> } >> catch (PlayerCc::PlayerError e) >> { >> std::cerr << e << std::endl; >> return -1; >> } >> return 1; >> } >> ------------------------------------------------ >> >> compilation ok. >> running error: >> calling connect >> done >> playerc error : timed out waiting for server reply to request 1:0:3:3 >> playerc error : failed to get response >> Position2dProxy:: Position2dProxy()(-1): could not subscribe. >> >> I am not sure the way I subscribe the vfh is right or not. >> Thanks. >> Dongqing >> >> -- >> View this message in context: >> http://www.nabble.com/help-with-vfh-driver-tp14716531p14716531.html >> Sent from the playerstage-users mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> >> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace >> _______________________________________________ >> Playerstage-users mailing list >> Pla...@li... >> https://lists.sourceforge.net/lists/listinfo/playerstage-users >> > > > > -- > This email is intended for the addressee only and may contain privileged > and/or confidential information > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > > -- View this message in context: http://www.nabble.com/help-with-vfh-driver-tp14716531p14759665.html Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Brian G. <br...@ge...> - 2008-01-14 23:46:34
|
On Jan 11, 2008, at 8:20 AM, Dongqing wrote: > But after a run the c code, it returned no subscribe. > So maybe the subscribe code is not right. > I did as follows: > > PlayerClient robot("localhost"); > Position2dProxy pp(&robot, 0); > LaserProxy lp(&robot, 0); > > Position2dProxy vfh(&robot, 1); Your code looks correct to me. Test it with with playerv: start playerv, and click on Devices->position2d:1 (vfh)->Subscribe. Does that work? Also, when you see the subscription error on the client side, what error messages (if any) do you see on the server side (i.e., the shell where you started player)? brian. > Toby Collett-3 wrote: >> >> Can you control the rmp with playerjoy or a simple client, >> simplify your >> config so you can isolate which driver is not behaving, >> >> Toby >> >> On 10/01/2008, Dongqing <don...@gm...> wrote: >>> >>> >>> configuration file: >>> >>> driver >>> ( >>> name "segwayrmp" >>> provides ["position2d:0" "position3d:0" "power:0"] >>> canio "kvaser" >>> max_xspeed 4.5 >>> max_yawspeed 80 >>> ) >>> >>> driver >>> ( >>> name "sicklms200" >>> provides ["laser:0"] >>> port "/dev/ttyS0" >>> ) >>> driver >>> ( >>> name "vfh" >>> requires ["position2d:0" "laser:0"] >>> provides ["position2d:1"] >>> safety_dist 0.10 >>> distance_epsilon 0.3 >>> angle_epsilon 5 >>> ) >>> ---------------------------------------------- >>> code: >>> >>> >>> >>> #include <libplayerc++/playerc++.h> >>> >>> using namespace PlayerCc; >>> >>> int main(int argc, char **argv) >>> { >>> double newspeed = 0; >>> double newturnrate = 0; >>> >>> /*********************** define the turn direction >>> *****************/ >>> >>> // we throw exceptions on creation if we fail >>> try >>> { >>> >>> PlayerClient robot("localhost"); >>> Position2dProxy pp(&robot, 0); >>> >>> >>> Position2dProxy vfh(&robot, 1); >>> >>> >>> pp.SetMotorEnable (true); >>> vfh.SetMotorEnable (true); >>> >>> >>> >>> newspeed = 0.2; //m/s >>> newturnrate = 0; >>> >>> player_pose_t pose; >>> pose.px = 1.0; >>> pose.py = 0; >>> pose.pa = 0; >>> >>> vfh.SetSpeed(newspeed, newturnrate); >>> vfh.GoTo(pose); >>> >>> >>> } >>> catch (PlayerCc::PlayerError e) >>> { >>> std::cerr << e << std::endl; >>> return -1; >>> } >>> return 1; >>> } >>> ------------------------------------------------ >>> >>> compilation ok. >>> running error: >>> calling connect >>> done >>> playerc error : timed out waiting for server reply to request >>> 1:0:3:3 >>> playerc error : failed to get response >>> Position2dProxy:: Position2dProxy()(-1): could not subscribe. >>> >>> I am not sure the way I subscribe the vfh is right or not. >>> Thanks. >>> Dongqing >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/help-with-vfh-driver-tp14716531p14716531.html >>> Sent from the playerstage-users mailing list archive at Nabble.com. >>> >>> >>> -------------------------------------------------------------------- >>> ----- >>> Check out the new SourceForge.net Marketplace. >>> It's the best place to buy or sell services for >>> just about anything Open Source. >>> >>> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/ >>> marketplace >>> _______________________________________________ >>> Playerstage-users mailing list >>> Pla...@li... >>> https://lists.sourceforge.net/lists/listinfo/playerstage-users >>> >> >> >> >> -- >> This email is intended for the addressee only and may contain >> privileged >> and/or confidential information >> >> --------------------------------------------------------------------- >> ---- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/ >> marketplace >> _______________________________________________ >> Playerstage-users mailing list >> Pla...@li... >> https://lists.sourceforge.net/lists/listinfo/playerstage-users >> >> > > -- > View this message in context: http://www.nabble.com/help-with-vfh- > driver-tp14716531p14759665.html > Sent from the playerstage-users mailing list archive at Nabble.com. > > > ---------------------------------------------------------------------- > --- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/ > marketplace > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users |
From: Dongqing <don...@gm...> - 2008-01-15 16:07:14
|
Hi Brian, Here is the messages: Step 1: [root@localhost config]# player seg_vfh.cfg * Part of the Player/Stage/Gazebo Project * [http://playerstage.sourceforge.net]. * Copyright (C) 2000 - 2006 Brian Gerkey, Richard Vaughan, Andrew Howard, * Nate Koenig, and contributors. Released under the GNU General Public * License. * Player comes with ABSOLUTELY NO WARRANTY. This is free software, and you * are welcome to redistribute it under certain conditions; see COPYING * for details. seg_vfh.cfg:32 warning: field [safety_dist] is defined but not used seg_vfh.cfg:34 warning: field [max_turnrate] is defined but not used seg_vfh.cfg:35 warning: field [free_space_cutoff] is defined but not used warning : timeout warning : timeout warning : timeout Listening on ports: 6665 ************************************************************* I have no idea why have so many warnings!!!!!!!!!! 2, Step 2: [root@localhost mycode]# playerv PlayerViewer 2.0.4 Connecting to [localhost:6665] calling connect done Available devices: localhost:6665 position2d:0 segwayrmp ready position3d:0 segwayrmp unsupported power:0 segwayrmp ready laser:0 sicklms200 ready position2d:1 vfh ready ************************************************************* 3, Step 3: As you told, I clicked on Devices->position2d:1 (vfh)->Subscribe The following error appears. But the step 2 seems vfh is ready???????? playerc error : timed out waiting for server reply to request 1:0:3:3 playerc error : failed to get response playerv : error in dev_position2d.c libplayerc error: failed to get response playerc error : timed out waiting for server reply to request 4:1:3:1 playerv : error in dev_position2d.c libplayerc error: timed out waiting for server reply to request 4:1:3:1 ********************************************************* Thanks for helping. Dongqing Brian Gerkey wrote: > > > On Jan 11, 2008, at 8:20 AM, Dongqing wrote: > >> But after a run the c code, it returned no subscribe. >> So maybe the subscribe code is not right. >> I did as follows: >> >> PlayerClient robot("localhost"); >> Position2dProxy pp(&robot, 0); >> LaserProxy lp(&robot, 0); >> >> Position2dProxy vfh(&robot, 1); > > Your code looks correct to me. Test it with with playerv: start > playerv, and click on Devices->position2d:1 (vfh)->Subscribe. Does > that work? > > Also, when you see the subscription error on the client side, what > error messages (if any) do you see on the server side (i.e., the > shell where you started player)? > > brian. > > >> Toby Collett-3 wrote: >>> >>> Can you control the rmp with playerjoy or a simple client, >>> simplify your >>> config so you can isolate which driver is not behaving, >>> >>> Toby >>> >>> On 10/01/2008, Dongqing <don...@gm...> wrote: >>>> >>>> >>>> configuration file: >>>> >>>> driver >>>> ( >>>> name "segwayrmp" >>>> provides ["position2d:0" "position3d:0" "power:0"] >>>> canio "kvaser" >>>> max_xspeed 4.5 >>>> max_yawspeed 80 >>>> ) >>>> >>>> driver >>>> ( >>>> name "sicklms200" >>>> provides ["laser:0"] >>>> port "/dev/ttyS0" >>>> ) >>>> driver >>>> ( >>>> name "vfh" >>>> requires ["position2d:0" "laser:0"] >>>> provides ["position2d:1"] >>>> safety_dist 0.10 >>>> distance_epsilon 0.3 >>>> angle_epsilon 5 >>>> ) >>>> ---------------------------------------------- >>>> code: >>>> >>>> >>>> >>>> #include <libplayerc++/playerc++.h> >>>> >>>> using namespace PlayerCc; >>>> >>>> int main(int argc, char **argv) >>>> { >>>> double newspeed = 0; >>>> double newturnrate = 0; >>>> >>>> /*********************** define the turn direction >>>> *****************/ >>>> >>>> // we throw exceptions on creation if we fail >>>> try >>>> { >>>> >>>> PlayerClient robot("localhost"); >>>> Position2dProxy pp(&robot, 0); >>>> >>>> >>>> Position2dProxy vfh(&robot, 1); >>>> >>>> >>>> pp.SetMotorEnable (true); >>>> vfh.SetMotorEnable (true); >>>> >>>> >>>> >>>> newspeed = 0.2; //m/s >>>> newturnrate = 0; >>>> >>>> player_pose_t pose; >>>> pose.px = 1.0; >>>> pose.py = 0; >>>> pose.pa = 0; >>>> >>>> vfh.SetSpeed(newspeed, newturnrate); >>>> vfh.GoTo(pose); >>>> >>>> >>>> } >>>> catch (PlayerCc::PlayerError e) >>>> { >>>> std::cerr << e << std::endl; >>>> return -1; >>>> } >>>> return 1; >>>> } >>>> ------------------------------------------------ >>>> >>>> compilation ok. >>>> running error: >>>> calling connect >>>> done >>>> playerc error : timed out waiting for server reply to request >>>> 1:0:3:3 >>>> playerc error : failed to get response >>>> Position2dProxy:: Position2dProxy()(-1): could not subscribe. >>>> >>>> I am not sure the way I subscribe the vfh is right or not. >>>> Thanks. >>>> Dongqing >>>> >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/help-with-vfh-driver-tp14716531p14716531.html >>>> Sent from the playerstage-users mailing list archive at Nabble.com. >>>> >>>> >>>> -------------------------------------------------------------------- >>>> ----- >>>> Check out the new SourceForge.net Marketplace. >>>> It's the best place to buy or sell services for >>>> just about anything Open Source. >>>> >>>> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/ >>>> marketplace >>>> _______________________________________________ >>>> Playerstage-users mailing list >>>> Pla...@li... >>>> https://lists.sourceforge.net/lists/listinfo/playerstage-users >>>> >>> >>> >>> >>> -- >>> This email is intended for the addressee only and may contain >>> privileged >>> and/or confidential information >>> >>> --------------------------------------------------------------------- >>> ---- >>> Check out the new SourceForge.net Marketplace. >>> It's the best place to buy or sell services for >>> just about anything Open Source. >>> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/ >>> marketplace >>> _______________________________________________ >>> Playerstage-users mailing list >>> Pla...@li... >>> https://lists.sourceforge.net/lists/listinfo/playerstage-users >>> >>> >> >> -- >> View this message in context: http://www.nabble.com/help-with-vfh- >> driver-tp14716531p14759665.html >> Sent from the playerstage-users mailing list archive at Nabble.com. >> >> >> ---------------------------------------------------------------------- >> --- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/ >> marketplace >> _______________________________________________ >> Playerstage-users mailing list >> Pla...@li... >> https://lists.sourceforge.net/lists/listinfo/playerstage-users > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > > -- View this message in context: http://www.nabble.com/help-with-vfh-driver-tp14716531p14841560.html Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Brian G. <br...@ge...> - 2008-01-17 16:55:12
|
On Jan 15, 2008, at 8:07 AM, Dongqing wrote: > > seg_vfh.cfg:32 warning: field [safety_dist] is defined but not used > seg_vfh.cfg:34 warning: field [max_turnrate] is defined but not used > seg_vfh.cfg:35 warning: field [free_space_cutoff] is defined but > not used > warning : timeout > warning : timeout > warning : timeout > Listening on ports: 6665 Looks like there's a problem with the connection to your SICK. You can get more debug info by looking in the file '.player'. It will tell you where those 'timeout' warnings are coming from. Try the following: - Add this line inside the vfh block of your .cfg file: alwayson 1 - Run player with extra debug info: $ player -d 9 seg_vfh.cfg This procedure will attempt to initialize vfh, and thus the segway and the SICK, at startup. It will likely fail; post the resulting output here and we'll try to help. As to the unused field warnings, that's because you're using obsolete field names. Many field names now include a suffix '_0ms' or '_1ms', to indicate the speeds at which they apply. Consult the vfh documentation: http://playerstage.sourceforge.net/doc/Player-2.0.0/player/ group__driver__vfh.html brian. |
From: Dongqing <don...@gm...> - 2008-01-17 19:48:20
|
Hi, After adding the alwayson driver in vfh #player -d 9 seg_vfh.cfg Laser initialising (/dev/ttyS0) connecting at 9600 sending configuration mode request to laser waiting for acknowledge warning : timeout sending configuration mode request to laser waiting for acknowledge warning : timeout sending configuration mode request to laser waiting for acknowledge warning : timeout connecting at 38400 sending configuration mode request to laser waiting for acknowledge SICK laser type [LMS200;301063;V02.30 ] at [/dev/ttyS0:38400] laser ready CAN bus initializing error : error on CAN Init error : unable to subscribe to position device error : initial subscription failed for device 4:1 error : failed to start alwayson drivers laser shutdown ********************************************** It seems laser connection is ok. Where I can find the *.player file to check the detail message? thanks. Dongqing On Jan 15, 2008, at 8:07 AM, Dongqing wrote: > > seg_vfh.cfg:32 warning: field [safety_dist] is defined but not used > seg_vfh.cfg:34 warning: field [max_turnrate] is defined but not used > seg_vfh.cfg:35 warning: field [free_space_cutoff] is defined but > not used > warning : timeout > warning : timeout > warning : timeout > Listening on ports: 6665 Looks like there's a problem with the connection to your SICK. You can get more debug info by looking in the file '.player'. It will tell you where those 'timeout' warnings are coming from. Try the following: - Add this line inside the vfh block of your .cfg file: alwayson 1 - Run player with extra debug info: $ player -d 9 seg_vfh.cfg This procedure will attempt to initialize vfh, and thus the segway and the SICK, at startup. It will likely fail; post the resulting output here and we'll try to help. As to the unused field warnings, that's because you're using obsolete field names. Many field names now include a suffix '_0ms' or '_1ms', to indicate the speeds at which they apply. Consult the vfh documentation: http://playerstage.sourceforge.net/doc/Player-2.0.0/player/ group__driver__vfh.html brian. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Playerstage-users mailing list Pla...@li... https://lists.sourceforge.net/lists/listinfo/playerstage-users -- View this message in context: http://www.nabble.com/help-with-vfh-driver-tp14716531p14930763.html Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Toby C. <tco...@pl...> - 2008-01-17 19:51:37
|
possibly you should try adding the alwayson to the laser block rather than the vfh block. This will cause the laser to initialise when player starts and then by the time you connect to vfh it should be ready to run. Toby On 18/01/2008, Dongqing <don...@gm...> wrote: > > > Hi, > > After adding the alwayson driver in vfh > > #player -d 9 seg_vfh.cfg > > Laser initialising (/dev/ttyS0) > connecting at 9600 > sending configuration mode request to laser > waiting for acknowledge > warning : timeout > sending configuration mode request to laser > waiting for acknowledge > warning : timeout > sending configuration mode request to laser > waiting for acknowledge > warning : timeout > connecting at 38400 > sending configuration mode request to laser > waiting for acknowledge > SICK laser type [LMS200;301063;V02.30 ] at [/dev/ttyS0:38400] > laser ready > CAN bus initializing > error : error on CAN Init > error : unable to subscribe to position device > error : initial subscription failed for device 4:1 > error : failed to start alwayson drivers > laser shutdown > > ********************************************** > It seems laser connection is ok. > Where I can find the *.player file to check the detail message? > > thanks. > Dongqing > > > > On Jan 15, 2008, at 8:07 AM, Dongqing wrote: > > > > > seg_vfh.cfg:32 warning: field [safety_dist] is defined but not used > > seg_vfh.cfg:34 warning: field [max_turnrate] is defined but not used > > seg_vfh.cfg:35 warning: field [free_space_cutoff] is defined but > > not used > > warning : timeout > > warning : timeout > > warning : timeout > > Listening on ports: 6665 > > Looks like there's a problem with the connection to your SICK. You > can get more debug info by looking in the file '.player'. It will > tell you where those 'timeout' warnings are coming from. > > Try the following: > > - Add this line inside the vfh block of your .cfg file: > alwayson 1 > > - Run player with extra debug info: > $ player -d 9 seg_vfh.cfg > > This procedure will attempt to initialize vfh, and thus the segway > and the SICK, at startup. It will likely fail; post the resulting > output here and we'll try to help. > > As to the unused field warnings, that's because you're using obsolete > field names. Many field names now include a suffix '_0ms' or '_1ms', > to indicate the speeds at which they apply. Consult the vfh > documentation: > > http://playerstage.sourceforge.net/doc/Player-2.0.0/player/ > group__driver__vfh.html > > brian. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > > > > -- > View this message in context: > http://www.nabble.com/help-with-vfh-driver-tp14716531p14930763.html > Sent from the playerstage-users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > -- This email is intended for the addressee only and may contain privileged and/or confidential information |
From: Dongqing <don...@gm...> - 2008-01-17 21:01:17
|
Hi Toby, You may right. The problem is, initially, I only have alwayson in the laser block. The detailed message is as follows: #player -d 9 seg_vfh.cfg Laser initialising (/dev/ttyS0) connecting at 9600 sending configuration mode request to laser waiting for acknowledge laser operating at 9600; changing to 38400 SICK laser type [LMS200;301063;V02.30 ] at [/dev/ttyS0:38400] laser ready Listening on ports: 6665 receiving data #it seems laser is fine. After running the client code, the following error appears. accepted client 0 on port 6665, fd 6 CAN bus initializing error : error on CAN Init warning : subscription failed for device 4:0 read() read zero bytes failed to read from client 0 closing connection to client 0 on port 6665 **************************************************** It seems the problem comes from the CAN bus. But without vfh, I run segway no problem. Vfh and segwayrmp may not work together. Dongqing #and the error from the clent code is: [root@localhost mycode]# ./motion3 calling connect done playerc error : requested [1] access, but got [3] access Position2dProxy::Position2dProxy()(-1) : could not subscribe Toby Collett-3 wrote: > > possibly you should try adding the alwayson to the laser block rather than > the vfh block. This will cause the laser to initialise when player starts > and then by the time you connect to vfh it should be ready to run. > > Toby > > On 18/01/2008, Dongqing <don...@gm...> wrote: >> >> >> Hi, >> >> After adding the alwayson driver in vfh >> >> #player -d 9 seg_vfh.cfg >> >> Laser initialising (/dev/ttyS0) >> connecting at 9600 >> sending configuration mode request to laser >> waiting for acknowledge >> warning : timeout >> sending configuration mode request to laser >> waiting for acknowledge >> warning : timeout >> sending configuration mode request to laser >> waiting for acknowledge >> warning : timeout >> connecting at 38400 >> sending configuration mode request to laser >> waiting for acknowledge >> SICK laser type [LMS200;301063;V02.30 ] at [/dev/ttyS0:38400] >> laser ready >> CAN bus initializing >> error : error on CAN Init >> error : unable to subscribe to position device >> error : initial subscription failed for device 4:1 >> error : failed to start alwayson drivers >> laser shutdown >> >> ********************************************** >> It seems laser connection is ok. >> Where I can find the *.player file to check the detail message? >> >> thanks. >> Dongqing >> >> >> >> On Jan 15, 2008, at 8:07 AM, Dongqing wrote: >> >> > >> > seg_vfh.cfg:32 warning: field [safety_dist] is defined but not used >> > seg_vfh.cfg:34 warning: field [max_turnrate] is defined but not used >> > seg_vfh.cfg:35 warning: field [free_space_cutoff] is defined but >> > not used >> > warning : timeout >> > warning : timeout >> > warning : timeout >> > Listening on ports: 6665 >> >> Looks like there's a problem with the connection to your SICK. You >> can get more debug info by looking in the file '.player'. It will >> tell you where those 'timeout' warnings are coming from. >> >> Try the following: >> >> - Add this line inside the vfh block of your .cfg file: >> alwayson 1 >> >> - Run player with extra debug info: >> $ player -d 9 seg_vfh.cfg >> >> This procedure will attempt to initialize vfh, and thus the segway >> and the SICK, at startup. It will likely fail; post the resulting >> output here and we'll try to help. >> >> As to the unused field warnings, that's because you're using obsolete >> field names. Many field names now include a suffix '_0ms' or '_1ms', >> to indicate the speeds at which they apply. Consult the vfh >> documentation: >> >> http://playerstage.sourceforge.net/doc/Player-2.0.0/player/ >> group__driver__vfh.html >> >> brian. >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Playerstage-users mailing list >> Pla...@li... >> https://lists.sourceforge.net/lists/listinfo/playerstage-users >> >> >> >> -- >> View this message in context: >> http://www.nabble.com/help-with-vfh-driver-tp14716531p14930763.html >> Sent from the playerstage-users mailing list archive at Nabble.com. >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Playerstage-users mailing list >> Pla...@li... >> https://lists.sourceforge.net/lists/listinfo/playerstage-users >> > > > > -- > This email is intended for the addressee only and may contain privileged > and/or confidential information > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > > -- View this message in context: http://www.nabble.com/help-with-vfh-driver-tp14716531p14933117.html Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Brian G. <br...@ge...> - 2008-01-17 23:58:59
|
On Jan 17, 2008, at 1:01 PM, Dongqing wrote: > After running the client code, > the following error appears. > > accepted client 0 on port 6665, fd 6 > CAN bus initializing > error : error on CAN Init > warning : subscription failed for device 4:0 > read() read zero bytes > failed to read from client 0 > closing connection to client 0 on port 6665 > > **************************************************** > It seems the problem comes from the CAN bus. But without vfh, I run > segway > no problem. > Vfh and segwayrmp may not work together. That's odd. Try adding 'alwayson 1' to the segwayrmp and sicklms200 drivers, but not the vfh driver. Then subscribe to vfh from a client. If that works, then perhaps there's some timing issue to be debugged. brian. |
From: Dongqing <don...@gm...> - 2008-01-18 16:30:40
|
Hi, I add the alwayson driver to the segwayrmp, and remove it from vfh driver. #player -d 9 seg_vfh.cfg CAN bus initializing starting main loop Laser initialising (/dev/ttyS0) connecting at 9600 sending configuration mode request to laser got data from rmp waiting for acknowledge warning : timeout sending configuration mode request to laser waiting for acknowledge warning : timeout sending configuration mode request to laser waiting for acknowledge warning : timeout connecting at 38400 sending configuration mode request to laser waiting for acknowledge SICK laser type [LMS200;301063;V02.30 ] at [/dev/ttyS0:38400] laser ready Listening on ports: 6665 receiving data ----------------------------------------------------------------------- Then I run the client # ./motion3 calling connect done playerc error : queue overflow; discarding packets playerc error : queue overflow; discarding packets playerc error : queue overflow; discarding packets playerc error : queue overflow; discarding packets playerc error : queue overflow; discarding packets ------------------------------------------------------ Then player output the following: accepted client 0 on port 6665, fd 8 warning : tried to push onto a full message queue error : tried to push 1/1 from 4:0 warning : tried to push onto a full message queue error : tried to push 1/1 from 4:0 warning : tried to push onto a full message queue error : tried to push 1/1 from 4:0 warning : tried to push onto a full message queue error : tried to push 1/1 from 4:0 warning : tried to push onto a full message queue error : tried to push 1/1 from 4:0 --------------------------------------------------------- I tried # playerv --laser:0 --position2d:0 --position2d:1 Similar error appears. Dongqing Brian Gerkey wrote: > > > On Jan 17, 2008, at 1:01 PM, Dongqing wrote: > >> After running the client code, >> the following error appears. >> >> accepted client 0 on port 6665, fd 6 >> CAN bus initializing >> error : error on CAN Init >> warning : subscription failed for device 4:0 >> read() read zero bytes >> failed to read from client 0 >> closing connection to client 0 on port 6665 >> >> **************************************************** >> It seems the problem comes from the CAN bus. But without vfh, I run >> segway >> no problem. >> Vfh and segwayrmp may not work together. > > That's odd. Try adding 'alwayson 1' to the segwayrmp and sicklms200 > drivers, but not the vfh driver. Then subscribe to vfh from a client. > > If that works, then perhaps there's some timing issue to be debugged. > > brian. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > > -- View this message in context: http://www.nabble.com/help-with-vfh-driver-tp14716531p14952945.html Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Brian G. <br...@ge...> - 2008-01-18 00:03:10
|
On Jan 17, 2008, at 11:47 AM, Dongqing wrote: > > Where I can find the *.player file to check the detail message? In whatever directory you run player, it creates a file called .player, containing all debug information. Each run of player will append lines to this file, so you may find it easier to delete it, run player to generate the error, then open the file. brian. |
From: Brian G. <br...@ge...> - 2008-02-06 22:11:12
|
It looks like the segwayrmp driver is publishing data *way* too fast. There should probably be some logic added to SegwayRMP::Main() to choke back the data rate. Unfortunately, I don't have the hardware available to test with... brian. Dongqing wrote: > Hi, > > I add the alwayson driver to the segwayrmp, and remove it from vfh driver. > #player -d 9 seg_vfh.cfg > > CAN bus initializing > starting main loop > Laser initialising (/dev/ttyS0) > connecting at 9600 > sending configuration mode request to laser > got data from rmp > waiting for acknowledge > warning : timeout > sending configuration mode request to laser > waiting for acknowledge > warning : timeout > sending configuration mode request to laser > waiting for acknowledge > warning : timeout > connecting at 38400 > sending configuration mode request to laser > waiting for acknowledge > SICK laser type [LMS200;301063;V02.30 ] at [/dev/ttyS0:38400] > laser ready > Listening on ports: 6665 > receiving data > > ----------------------------------------------------------------------- > Then I run the client > # ./motion3 > calling connect > done > playerc error : queue overflow; discarding packets > playerc error : queue overflow; discarding packets > playerc error : queue overflow; discarding packets > playerc error : queue overflow; discarding packets > playerc error : queue overflow; discarding packets > > ------------------------------------------------------ > Then player output the following: > > accepted client 0 on port 6665, fd 8 > warning : tried to push onto a full message queue > error : tried to push 1/1 from 4:0 > warning : tried to push onto a full message queue > error : tried to push 1/1 from 4:0 > warning : tried to push onto a full message queue > error : tried to push 1/1 from 4:0 > warning : tried to push onto a full message queue > error : tried to push 1/1 from 4:0 > warning : tried to push onto a full message queue > error : tried to push 1/1 from 4:0 > > --------------------------------------------------------- > I tried # playerv --laser:0 --position2d:0 --position2d:1 > > Similar error appears. > > > Dongqing > > > > Brian Gerkey wrote: >> >> On Jan 17, 2008, at 1:01 PM, Dongqing wrote: >> >>> After running the client code, >>> the following error appears. >>> >>> accepted client 0 on port 6665, fd 6 >>> CAN bus initializing >>> error : error on CAN Init >>> warning : subscription failed for device 4:0 >>> read() read zero bytes >>> failed to read from client 0 >>> closing connection to client 0 on port 6665 >>> >>> **************************************************** >>> It seems the problem comes from the CAN bus. But without vfh, I run >>> segway >>> no problem. >>> Vfh and segwayrmp may not work together. >> That's odd. Try adding 'alwayson 1' to the segwayrmp and sicklms200 >> drivers, but not the vfh driver. Then subscribe to vfh from a client. >> >> If that works, then perhaps there's some timing issue to be debugged. >> >> brian. >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Playerstage-users mailing list >> Pla...@li... >> https://lists.sourceforge.net/lists/listinfo/playerstage-users >> >> > |
From: Dongqing <don...@gm...> - 2008-02-07 02:00:35
|
Do you mean there maybe some bug in the segwayrmp driver? Brian Gerkey wrote: > > It looks like the segwayrmp driver is publishing data *way* too fast. > There should probably be some logic added to SegwayRMP::Main() to choke > back the data rate. Unfortunately, I don't have the hardware available > to test with... > > brian. > > Dongqing wrote: >> Hi, >> >> I add the alwayson driver to the segwayrmp, and remove it from vfh >> driver. >> #player -d 9 seg_vfh.cfg >> >> CAN bus initializing >> starting main loop >> Laser initialising (/dev/ttyS0) >> connecting at 9600 >> sending configuration mode request to laser >> got data from rmp >> waiting for acknowledge >> warning : timeout >> sending configuration mode request to laser >> waiting for acknowledge >> warning : timeout >> sending configuration mode request to laser >> waiting for acknowledge >> warning : timeout >> connecting at 38400 >> sending configuration mode request to laser >> waiting for acknowledge >> SICK laser type [LMS200;301063;V02.30 ] at [/dev/ttyS0:38400] >> laser ready >> Listening on ports: 6665 >> receiving data >> >> ----------------------------------------------------------------------- >> Then I run the client >> # ./motion3 >> calling connect >> done >> playerc error : queue overflow; discarding packets >> playerc error : queue overflow; discarding packets >> playerc error : queue overflow; discarding packets >> playerc error : queue overflow; discarding packets >> playerc error : queue overflow; discarding packets >> >> ------------------------------------------------------ >> Then player output the following: >> >> accepted client 0 on port 6665, fd 8 >> warning : tried to push onto a full message queue >> error : tried to push 1/1 from 4:0 >> warning : tried to push onto a full message queue >> error : tried to push 1/1 from 4:0 >> warning : tried to push onto a full message queue >> error : tried to push 1/1 from 4:0 >> warning : tried to push onto a full message queue >> error : tried to push 1/1 from 4:0 >> warning : tried to push onto a full message queue >> error : tried to push 1/1 from 4:0 >> >> --------------------------------------------------------- >> I tried # playerv --laser:0 --position2d:0 --position2d:1 >> >> Similar error appears. >> >> >> Dongqing >> >> >> >> Brian Gerkey wrote: >>> >>> On Jan 17, 2008, at 1:01 PM, Dongqing wrote: >>> >>>> After running the client code, >>>> the following error appears. >>>> >>>> accepted client 0 on port 6665, fd 6 >>>> CAN bus initializing >>>> error : error on CAN Init >>>> warning : subscription failed for device 4:0 >>>> read() read zero bytes >>>> failed to read from client 0 >>>> closing connection to client 0 on port 6665 >>>> >>>> **************************************************** >>>> It seems the problem comes from the CAN bus. But without vfh, I run >>>> segway >>>> no problem. >>>> Vfh and segwayrmp may not work together. >>> That's odd. Try adding 'alwayson 1' to the segwayrmp and sicklms200 >>> drivers, but not the vfh driver. Then subscribe to vfh from a client. >>> >>> If that works, then perhaps there's some timing issue to be debugged. >>> >>> brian. >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2008. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> Playerstage-users mailing list >>> Pla...@li... >>> https://lists.sourceforge.net/lists/listinfo/playerstage-users >>> >>> >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users > > -- View this message in context: http://www.nabble.com/help-with-vfh-driver-tp14716531p15326039.html Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Brian G. <br...@ge...> - 2008-03-03 21:14:29
|
On Feb 6, 2008, at 6:00 PM, Dongqing wrote: > > Do you mean there maybe some bug in the segwayrmp driver? Yes, it looks that way. It will probably be necessary to modify the segwayrmp driver code. It's in player/server/drivers/mixed/rmp/ segwayrmp.cc. brian. > Brian Gerkey wrote: >> >> It looks like the segwayrmp driver is publishing data *way* too fast. >> There should probably be some logic added to SegwayRMP::Main() to >> choke >> back the data rate. Unfortunately, I don't have the hardware >> available >> to test with... >> >> brian. >> >> Dongqing wrote: >>> Hi, >>> >>> I add the alwayson driver to the segwayrmp, and remove it from vfh >>> driver. >>> #player -d 9 seg_vfh.cfg >>> >>> CAN bus initializing >>> starting main loop >>> Laser initialising (/dev/ttyS0) >>> connecting at 9600 >>> sending configuration mode request to laser >>> got data from rmp >>> waiting for acknowledge >>> warning : timeout >>> sending configuration mode request to laser >>> waiting for acknowledge >>> warning : timeout >>> sending configuration mode request to laser >>> waiting for acknowledge >>> warning : timeout >>> connecting at 38400 >>> sending configuration mode request to laser >>> waiting for acknowledge >>> SICK laser type [LMS200;301063;V02.30 ] at [/dev/ttyS0:38400] >>> laser ready >>> Listening on ports: 6665 >>> receiving data >>> >>> ----------------------------------------------------------------------- >>> Then I run the client >>> # ./motion3 >>> calling connect >>> done >>> playerc error : queue overflow; discarding packets >>> playerc error : queue overflow; discarding packets >>> playerc error : queue overflow; discarding packets >>> playerc error : queue overflow; discarding packets >>> playerc error : queue overflow; discarding packets >>> >>> ------------------------------------------------------ >>> Then player output the following: >>> >>> accepted client 0 on port 6665, fd 8 >>> warning : tried to push onto a full message queue >>> error : tried to push 1/1 from 4:0 >>> warning : tried to push onto a full message queue >>> error : tried to push 1/1 from 4:0 >>> warning : tried to push onto a full message queue >>> error : tried to push 1/1 from 4:0 >>> warning : tried to push onto a full message queue >>> error : tried to push 1/1 from 4:0 >>> warning : tried to push onto a full message queue >>> error : tried to push 1/1 from 4:0 >>> >>> --------------------------------------------------------- >>> I tried # playerv --laser:0 --position2d:0 --position2d:1 >>> >>> Similar error appears. >>> >>> >>> Dongqing >>> >>> >>> >>> Brian Gerkey wrote: >>>> >>>> On Jan 17, 2008, at 1:01 PM, Dongqing wrote: >>>> >>>>> After running the client code, >>>>> the following error appears. >>>>> >>>>> accepted client 0 on port 6665, fd 6 >>>>> CAN bus initializing >>>>> error : error on CAN Init >>>>> warning : subscription failed for device 4:0 >>>>> read() read zero bytes >>>>> failed to read from client 0 >>>>> closing connection to client 0 on port 6665 >>>>> >>>>> **************************************************** >>>>> It seems the problem comes from the CAN bus. But without vfh, I >>>>> run >>>>> segway >>>>> no problem. >>>>> Vfh and segwayrmp may not work together. >>>> That's odd. Try adding 'alwayson 1' to the segwayrmp and >>>> sicklms200 >>>> drivers, but not the vfh driver. Then subscribe to vfh from a >>>> client. >>>> >>>> If that works, then perhaps there's some timing issue to be >>>> debugged. >>>> >>>> brian. >>>> >>>> ------------------------------------------------------------------------- >>>> This SF.net email is sponsored by: Microsoft >>>> Defy all challenges. Microsoft(R) Visual Studio 2008. >>>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>>> _______________________________________________ >>>> Playerstage-users mailing list >>>> Pla...@li... >>>> https://lists.sourceforge.net/lists/listinfo/playerstage-users >>>> >>>> >>> >> >> >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> _______________________________________________ >> Playerstage-users mailing list >> Pla...@li... >> https://lists.sourceforge.net/lists/listinfo/playerstage-users >> >> > > -- > View this message in context: http://www.nabble.com/help-with-vfh-driver-tp14716531p15326039.html > Sent from the playerstage-users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users |