From: XRobots <ja...@xr...> - 2007-09-09 16:23:18
|
I have a SICK PLS101-312 which I have had working with the SICK user software under Windows - I can monitor the scan / perform diags and generally set the config as you'd expect. However, booting to Linux on the same PC with the same serial port and cable etc I have some issues getting the PLS to work under Player with the 'sickpls' driver. I have also tried another install of Player on a totally separate Linux PC but the issue is eactly the same. My config file is as follows, for now I have no other robotic hardware connected: driver ( name "sickpls" provides ["laser:0"] port "/dev/ttyS0" rate 38400 ) The baud rate is correct as I already set this to be permananent with the SICK user software under Windows. When I start Player using this config file and run playerv I can see the 'laser:0 (sickpls)' on the menu of devices and I can click on 'Subscribe'. The terminal window that I have run player from displays the following messages: Listening on ports: 6665 accepted client 0 on port 6665, fd 5 Laser initialising (/dev/ttyS0) LASER: change TERM speed: 38400 LASER: RLD: writing scan data LASER: RLD: waiting for ACK LASER: RLD: scan data OK laser ready LASER: RLD: writing scan data LASER: RLD: waiting for ACK LASER: RLD: scan data OK So that looks ok to me I think(?). However, the playerv window then hangs and I cannot see any laser ranges or click on the menus anymore. The only way to get out is to kill the terminal window that I launched playerv from. If I leave playerv running (in a hung state) for a while, eventually the terminal I launched playerv from displays: playerc error : queue overflow; discarding packets ...a lot of times. Does anyone have a SICK PLS working ok with Player who can tell me what I need to change - I assume that there's either a cfg file issue or the config of the PLS itself needs changing through the SICK user software?. thanks -- View this message in context: http://www.nabble.com/SICK-PLS-config-issue-tf4409923.html#a12580400 Sent from the playerstage-users mailing list archive at Nabble.com. |
From: XRobots <ja...@xr...> - 2007-09-09 21:21:27
|
A little update after I have been tinkering around, but still not fixed: I have added the line 'resolution 100' to the config file, although the resolution of the laser is 0.5 degrees so it should really be left at the default of 50. Now I get a lot more messages in the terminal that I launched Player from as follows: error : no reply from laser LASER: RLD: writing scan data LASER: RLD: waiting for ACK After about 4 of these a partial scan appears in playerv and the menus start to work again, but then I get a message that says: error : unexpected packet type ...and everything stops, leaving a corrupted looking scan in playernav. So it looks like some sort of comms error, although I don't know why it won't work with the correct setting for resolution in the config file - it still just hangs after the message I posted in the previous message. Does anyone know if the 'sickpls' driver was written for the PLS101-312 or one of the other models (PLS101-112 etc)?. This is on Player 2.0.3 but I can't see a bug / fix report for this between 2.0.3 and 2.0.4 thanks XRobots wrote: > > I have a SICK PLS101-312 which I have had working with the SICK user > software under Windows - I can monitor the scan / perform diags and > generally set the config as you'd expect. However, booting to Linux on the > same PC with the same serial port and cable etc I have some issues getting > the PLS to work under Player with the 'sickpls' driver. I have also tried > another install of Player on a totally separate Linux PC but the issue is > eactly the same. > > My config file is as follows, for now I have no other robotic hardware > connected: > > driver > ( > name "sickpls" > provides ["laser:0"] > port "/dev/ttyS0" > rate 38400 > ) > > The baud rate is correct as I already set this to be permananent with the > SICK user software under Windows. > > When I start Player using this config file and run playerv I can see the > 'laser:0 (sickpls)' on the menu of devices and I can click on 'Subscribe'. > The terminal window that I have run player from displays the following > messages: > > Listening on ports: 6665 > accepted client 0 on port 6665, fd 5 > Laser initialising (/dev/ttyS0) > LASER: change TERM speed: 38400 > LASER: RLD: writing scan data > LASER: RLD: waiting for ACK > LASER: RLD: scan data OK > laser ready > LASER: RLD: writing scan data > LASER: RLD: waiting for ACK > LASER: RLD: scan data OK > > So that looks ok to me I think(?). However, the playerv window then hangs > and I cannot see any laser ranges or click on the menus anymore. The only > way to get out is to kill the terminal window that I launched playerv > from. > > If I leave playerv running (in a hung state) for a while, eventually the > terminal I launched playerv from displays: > > playerc error : queue overflow; discarding packets > > ...a lot of times. > > Does anyone have a SICK PLS working ok with Player who can tell me what I > need to change - I assume that there's either a cfg file issue or the > config of the PLS itself needs changing through the SICK user software?. > > I am using Ubuntu 6.06 LTS and Player 2.0.3 (I can't see a bug report or > fix for this between 2.0.3 and 2.0.4) > > thanks > > > > > -- View this message in context: http://www.nabble.com/SICK-PLS-config-issue-tf4409923.html#a12583338 Sent from the playerstage-users mailing list archive at Nabble.com. |
From: XRobots <ja...@xr...> - 2007-09-13 17:35:21
|
I have now tried a USB-RS422 interface, which again works fine with the SICK Windows user software. However, the results with Player are exactly identical. Does anybody have any idea whatsoever which hardware is really supported by the 'sickpls' driver or any idea what the config of it should be? ...anything? thanks XRobots wrote: > > A little update after I have been tinkering around, but still not fixed: > > I have added the line 'resolution 100' to the config file, although the > resolution of the laser is 0.5 degrees so it should really be left at the > default of 50. Now I get a lot more messages in the terminal that I > launched Player from as follows: > > error : no reply from laser > LASER: RLD: writing scan data > LASER: RLD: waiting for ACK > > After about 4 of these a partial scan appears in playerv and the menus > start to work again, but then I get a message that says: > > error : unexpected packet type > > ...and everything stops, leaving a corrupted looking scan in playernav. > So it looks like some sort of comms error, although I don't know why it > won't work with the correct setting for resolution in the config file - it > still just hangs after the message I posted in the previous message. > > Does anyone know if the 'sickpls' driver was written for the PLS101-312 or > one of the other models (PLS101-112 etc)?. > > This is on Player 2.0.3 but I can't see a bug / fix report for this > between 2.0.3 and 2.0.4 > > thanks > > > XRobots wrote: >> >> I have a SICK PLS101-312 which I have had working with the SICK user >> software under Windows - I can monitor the scan / perform diags and >> generally set the config as you'd expect. However, booting to Linux on >> the same PC with the same serial port and cable etc I have some issues >> getting the PLS to work under Player with the 'sickpls' driver. I have >> also tried another install of Player on a totally separate Linux PC but >> the issue is eactly the same. >> >> My config file is as follows, for now I have no other robotic hardware >> connected: >> >> driver >> ( >> name "sickpls" >> provides ["laser:0"] >> port "/dev/ttyS0" >> rate 38400 >> ) >> >> The baud rate is correct as I already set this to be permananent with the >> SICK user software under Windows. >> >> When I start Player using this config file and run playerv I can see the >> 'laser:0 (sickpls)' on the menu of devices and I can click on >> 'Subscribe'. The terminal window that I have run player from displays the >> following messages: >> >> Listening on ports: 6665 >> accepted client 0 on port 6665, fd 5 >> Laser initialising (/dev/ttyS0) >> LASER: change TERM speed: 38400 >> LASER: RLD: writing scan data >> LASER: RLD: waiting for ACK >> LASER: RLD: scan data OK >> laser ready >> LASER: RLD: writing scan data >> LASER: RLD: waiting for ACK >> LASER: RLD: scan data OK >> >> So that looks ok to me I think(?). However, the playerv window then hangs >> and I cannot see any laser ranges or click on the menus anymore. The only >> way to get out is to kill the terminal window that I launched playerv >> from. >> >> If I leave playerv running (in a hung state) for a while, eventually the >> terminal I launched playerv from displays: >> >> playerc error : queue overflow; discarding packets >> >> ...a lot of times. >> >> Does anyone have a SICK PLS working ok with Player who can tell me what I >> need to change - I assume that there's either a cfg file issue or the >> config of the PLS itself needs changing through the SICK user software?. >> >> I am using Ubuntu 6.06 LTS and Player 2.0.3 (I can't see a bug report or >> fix for this between 2.0.3 and 2.0.4) >> >> thanks >> >> >> >> >> > > -- View this message in context: http://www.nabble.com/SICK-PLS-config-issue-tf4409923.html#a12659796 Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Richard v. <va...@cs...> - 2007-09-13 18:01:05
|
Things to look at: * It's possible that the problem is with playerv, and not the driver. Have you tried using another laser client, e.g. "playerprint laser"? * Is it the Player server or a client that produces the "unexpected packet type" error? It may be helpful to break the program in the debugger at that point, and find what the packet type is and post a backtrace here to provide some clues. Richard/ On 13-Sep-07, at 10:35 AM, XRobots wrote: > > I have now tried a USB-RS422 interface, which again works fine with > the SICK > Windows user software. However, the results with Player are exactly > identical. > > Does anybody have any idea whatsoever which hardware is really > supported by > the 'sickpls' driver or any idea what the config of it should be? > > ...anything? > > thanks > > > > XRobots wrote: >> >> A little update after I have been tinkering around, but still not >> fixed: >> >> I have added the line 'resolution 100' to the config file, >> although the >> resolution of the laser is 0.5 degrees so it should really be left >> at the >> default of 50. Now I get a lot more messages in the terminal that I >> launched Player from as follows: >> >> error : no reply from laser >> LASER: RLD: writing scan data >> LASER: RLD: waiting for ACK >> >> After about 4 of these a partial scan appears in playerv and the >> menus >> start to work again, but then I get a message that says: >> >> error : unexpected packet type >> >> ...and everything stops, leaving a corrupted looking scan in >> playernav. >> So it looks like some sort of comms error, although I don't know >> why it >> won't work with the correct setting for resolution in the config >> file - it >> still just hangs after the message I posted in the previous message. >> >> Does anyone know if the 'sickpls' driver was written for the >> PLS101-312 or >> one of the other models (PLS101-112 etc)?. >> >> This is on Player 2.0.3 but I can't see a bug / fix report for this >> between 2.0.3 and 2.0.4 >> >> thanks >> >> >> XRobots wrote: >>> >>> I have a SICK PLS101-312 which I have had working with the SICK user >>> software under Windows - I can monitor the scan / perform diags and >>> generally set the config as you'd expect. However, booting to >>> Linux on >>> the same PC with the same serial port and cable etc I have some >>> issues >>> getting the PLS to work under Player with the 'sickpls' driver. I >>> have >>> also tried another install of Player on a totally separate Linux >>> PC but >>> the issue is eactly the same. >>> >>> My config file is as follows, for now I have no other robotic >>> hardware >>> connected: >>> >>> driver >>> ( >>> name "sickpls" >>> provides ["laser:0"] >>> port "/dev/ttyS0" >>> rate 38400 >>> ) >>> >>> The baud rate is correct as I already set this to be permananent >>> with the >>> SICK user software under Windows. >>> >>> When I start Player using this config file and run playerv I can >>> see the >>> 'laser:0 (sickpls)' on the menu of devices and I can click on >>> 'Subscribe'. The terminal window that I have run player from >>> displays the >>> following messages: >>> >>> Listening on ports: 6665 >>> accepted client 0 on port 6665, fd 5 >>> Laser initialising (/dev/ttyS0) >>> LASER: change TERM speed: 38400 >>> LASER: RLD: writing scan data >>> LASER: RLD: waiting for ACK >>> LASER: RLD: scan data OK >>> laser ready >>> LASER: RLD: writing scan data >>> LASER: RLD: waiting for ACK >>> LASER: RLD: scan data OK >>> >>> So that looks ok to me I think(?). However, the playerv window >>> then hangs >>> and I cannot see any laser ranges or click on the menus anymore. >>> The only >>> way to get out is to kill the terminal window that I launched >>> playerv >>> from. >>> >>> If I leave playerv running (in a hung state) for a while, >>> eventually the >>> terminal I launched playerv from displays: >>> >>> playerc error : queue overflow; discarding packets >>> >>> ...a lot of times. >>> >>> Does anyone have a SICK PLS working ok with Player who can tell >>> me what I >>> need to change - I assume that there's either a cfg file issue or >>> the >>> config of the PLS itself needs changing through the SICK user >>> software?. >>> >>> I am using Ubuntu 6.06 LTS and Player 2.0.3 (I can't see a bug >>> report or >>> fix for this between 2.0.3 and 2.0.4) >>> >>> thanks >>> >>> >>> >>> >>> >> >> > > -- > View this message in context: http://www.nabble.com/SICK-PLS-config- > issue-tf4409923.html#a12659796 > 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 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users |
From: XRobots <ja...@xr...> - 2007-09-13 18:30:35
|
Thanks for your reply Richard. I had previously tried the 'laserobstacleavoid' program with the laser sat on top of my WBR914 robot which otherwise works fine (for all it's own devices) - although it drove straight forward and crashed which made me think that there was incorrect or no laser data. However, I've now tried 'playerprint laser' and you suggest, and this produces some data which looks good and changes and you wave you hand in front of it - at least it doesn't hang, horray!. So it looks like the issue may be with playerv as you say. The 'unexpected packet type error' was from the terminal window where player itself was running, but this was only with the resolution forced to 100 which is incorrect for that device, so only to be expected I suppose. It was just the only way through tinkering that I could get anything out of playerv and the laser together. So I'll guess I'll progress with testing the VFH driver and see if I can get my 914 to avoid obstacles now that I know the data/comms appears to be actually working. So watch out for the next instalment of: http://www.914pcbots.com/community/index.php?option=com_content&task=view&id=323&Itemid=65 thanks again -James Richard vaughan wrote: > > Things to look at: > > * It's possible that the problem is with playerv, and not the driver. > Have you tried using another laser client, e.g. "playerprint laser"? > > * Is it the Player server or a client that produces the "unexpected > packet type" error? It may be helpful to break the program in the > debugger at that point, and find what the packet type is and post a > backtrace here to provide some clues. > > Richard/ > > On 13-Sep-07, at 10:35 AM, XRobots wrote: > >> >> I have now tried a USB-RS422 interface, which again works fine with >> the SICK >> Windows user software. However, the results with Player are exactly >> identical. >> >> Does anybody have any idea whatsoever which hardware is really >> supported by >> the 'sickpls' driver or any idea what the config of it should be? >> >> ...anything? >> >> thanks >> >> >> >> XRobots wrote: >>> >>> A little update after I have been tinkering around, but still not >>> fixed: >>> >>> I have added the line 'resolution 100' to the config file, >>> although the >>> resolution of the laser is 0.5 degrees so it should really be left >>> at the >>> default of 50. Now I get a lot more messages in the terminal that I >>> launched Player from as follows: >>> >>> error : no reply from laser >>> LASER: RLD: writing scan data >>> LASER: RLD: waiting for ACK >>> >>> After about 4 of these a partial scan appears in playerv and the >>> menus >>> start to work again, but then I get a message that says: >>> >>> error : unexpected packet type >>> >>> ...and everything stops, leaving a corrupted looking scan in >>> playernav. >>> So it looks like some sort of comms error, although I don't know >>> why it >>> won't work with the correct setting for resolution in the config >>> file - it >>> still just hangs after the message I posted in the previous message. >>> >>> Does anyone know if the 'sickpls' driver was written for the >>> PLS101-312 or >>> one of the other models (PLS101-112 etc)?. >>> >>> This is on Player 2.0.3 but I can't see a bug / fix report for this >>> between 2.0.3 and 2.0.4 >>> >>> thanks >>> >>> >>> XRobots wrote: >>>> >>>> I have a SICK PLS101-312 which I have had working with the SICK user >>>> software under Windows - I can monitor the scan / perform diags and >>>> generally set the config as you'd expect. However, booting to >>>> Linux on >>>> the same PC with the same serial port and cable etc I have some >>>> issues >>>> getting the PLS to work under Player with the 'sickpls' driver. I >>>> have >>>> also tried another install of Player on a totally separate Linux >>>> PC but >>>> the issue is eactly the same. >>>> >>>> My config file is as follows, for now I have no other robotic >>>> hardware >>>> connected: >>>> >>>> driver >>>> ( >>>> name "sickpls" >>>> provides ["laser:0"] >>>> port "/dev/ttyS0" >>>> rate 38400 >>>> ) >>>> >>>> The baud rate is correct as I already set this to be permananent >>>> with the >>>> SICK user software under Windows. >>>> >>>> When I start Player using this config file and run playerv I can >>>> see the >>>> 'laser:0 (sickpls)' on the menu of devices and I can click on >>>> 'Subscribe'. The terminal window that I have run player from >>>> displays the >>>> following messages: >>>> >>>> Listening on ports: 6665 >>>> accepted client 0 on port 6665, fd 5 >>>> Laser initialising (/dev/ttyS0) >>>> LASER: change TERM speed: 38400 >>>> LASER: RLD: writing scan data >>>> LASER: RLD: waiting for ACK >>>> LASER: RLD: scan data OK >>>> laser ready >>>> LASER: RLD: writing scan data >>>> LASER: RLD: waiting for ACK >>>> LASER: RLD: scan data OK >>>> >>>> So that looks ok to me I think(?). However, the playerv window >>>> then hangs >>>> and I cannot see any laser ranges or click on the menus anymore. >>>> The only >>>> way to get out is to kill the terminal window that I launched >>>> playerv >>>> from. >>>> >>>> If I leave playerv running (in a hung state) for a while, >>>> eventually the >>>> terminal I launched playerv from displays: >>>> >>>> playerc error : queue overflow; discarding packets >>>> >>>> ...a lot of times. >>>> >>>> Does anyone have a SICK PLS working ok with Player who can tell >>>> me what I >>>> need to change - I assume that there's either a cfg file issue or >>>> the >>>> config of the PLS itself needs changing through the SICK user >>>> software?. >>>> >>>> I am using Ubuntu 6.06 LTS and Player 2.0.3 (I can't see a bug >>>> report or >>>> fix for this between 2.0.3 and 2.0.4) >>>> >>>> thanks >>>> >>>> >>>> >>>> >>>> >>> >>> >> >> -- >> View this message in context: http://www.nabble.com/SICK-PLS-config- >> issue-tf4409923.html#a12659796 >> 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 2005. >> 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 2005. > 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/SICK-PLS-config-issue-tf4409923.html#a12660783 Sent from the playerstage-users mailing list archive at Nabble.com. |
From: XRobots <ja...@xr...> - 2007-09-13 18:40:38
|
I should add that my playerv works ok with the IR sensors in my WBR914 robot - the ranges are rendered correctly and in real time, I can drive around etc, hence I didn't suspect that it was an issue with playerv beforehand. Any ideas why playerv would hang with just the laser?. I'd have thought that someone would have noticed before since 'laser' is quite widely used, unless it's related specifically to the 'sickpls' driver, which maybe in less common use than the 'sicklms200' driver for instance... XRobots wrote: > > Thanks for your reply Richard. > > I had previously tried the 'laserobstacleavoid' program with the laser sat > on top of my WBR914 robot which otherwise works fine (for all it's own > devices) - although it drove straight forward and crashed which made me > think that there was incorrect or no laser data. > > However, I've now tried 'playerprint laser' and you suggest, and this > produces some data which looks good and changes and you wave you hand in > front of it - at least it doesn't hang, horray!. So it looks like the > issue may be with playerv as you say. > > The 'unexpected packet type error' was from the terminal window where > player itself was running, but this was only with the resolution forced to > 100 which is incorrect for that device, so only to be expected I suppose. > It was just the only way through tinkering that I could get anything out > of playerv and the laser together. > > So I'll guess I'll progress with testing the VFH driver and see if I can > get my 914 to avoid obstacles now that I know the data/comms appears to be > actually working. > > So watch out for the next instalment of: > > http://www.914pcbots.com/community/index.php?option=com_content&task=view&id=323&Itemid=65 > > thanks again > -James > > > > > > Richard vaughan wrote: >> >> Things to look at: >> >> * It's possible that the problem is with playerv, and not the driver. >> Have you tried using another laser client, e.g. "playerprint laser"? >> >> * Is it the Player server or a client that produces the "unexpected >> packet type" error? It may be helpful to break the program in the >> debugger at that point, and find what the packet type is and post a >> backtrace here to provide some clues. >> >> Richard/ >> >> On 13-Sep-07, at 10:35 AM, XRobots wrote: >> >>> >>> I have now tried a USB-RS422 interface, which again works fine with >>> the SICK >>> Windows user software. However, the results with Player are exactly >>> identical. >>> >>> Does anybody have any idea whatsoever which hardware is really >>> supported by >>> the 'sickpls' driver or any idea what the config of it should be? >>> >>> ...anything? >>> >>> thanks >>> >>> >>> >>> XRobots wrote: >>>> >>>> A little update after I have been tinkering around, but still not >>>> fixed: >>>> >>>> I have added the line 'resolution 100' to the config file, >>>> although the >>>> resolution of the laser is 0.5 degrees so it should really be left >>>> at the >>>> default of 50. Now I get a lot more messages in the terminal that I >>>> launched Player from as follows: >>>> >>>> error : no reply from laser >>>> LASER: RLD: writing scan data >>>> LASER: RLD: waiting for ACK >>>> >>>> After about 4 of these a partial scan appears in playerv and the >>>> menus >>>> start to work again, but then I get a message that says: >>>> >>>> error : unexpected packet type >>>> >>>> ...and everything stops, leaving a corrupted looking scan in >>>> playernav. >>>> So it looks like some sort of comms error, although I don't know >>>> why it >>>> won't work with the correct setting for resolution in the config >>>> file - it >>>> still just hangs after the message I posted in the previous message. >>>> >>>> Does anyone know if the 'sickpls' driver was written for the >>>> PLS101-312 or >>>> one of the other models (PLS101-112 etc)?. >>>> >>>> This is on Player 2.0.3 but I can't see a bug / fix report for this >>>> between 2.0.3 and 2.0.4 >>>> >>>> thanks >>>> >>>> >>>> XRobots wrote: >>>>> >>>>> I have a SICK PLS101-312 which I have had working with the SICK user >>>>> software under Windows - I can monitor the scan / perform diags and >>>>> generally set the config as you'd expect. However, booting to >>>>> Linux on >>>>> the same PC with the same serial port and cable etc I have some >>>>> issues >>>>> getting the PLS to work under Player with the 'sickpls' driver. I >>>>> have >>>>> also tried another install of Player on a totally separate Linux >>>>> PC but >>>>> the issue is eactly the same. >>>>> >>>>> My config file is as follows, for now I have no other robotic >>>>> hardware >>>>> connected: >>>>> >>>>> driver >>>>> ( >>>>> name "sickpls" >>>>> provides ["laser:0"] >>>>> port "/dev/ttyS0" >>>>> rate 38400 >>>>> ) >>>>> >>>>> The baud rate is correct as I already set this to be permananent >>>>> with the >>>>> SICK user software under Windows. >>>>> >>>>> When I start Player using this config file and run playerv I can >>>>> see the >>>>> 'laser:0 (sickpls)' on the menu of devices and I can click on >>>>> 'Subscribe'. The terminal window that I have run player from >>>>> displays the >>>>> following messages: >>>>> >>>>> Listening on ports: 6665 >>>>> accepted client 0 on port 6665, fd 5 >>>>> Laser initialising (/dev/ttyS0) >>>>> LASER: change TERM speed: 38400 >>>>> LASER: RLD: writing scan data >>>>> LASER: RLD: waiting for ACK >>>>> LASER: RLD: scan data OK >>>>> laser ready >>>>> LASER: RLD: writing scan data >>>>> LASER: RLD: waiting for ACK >>>>> LASER: RLD: scan data OK >>>>> >>>>> So that looks ok to me I think(?). However, the playerv window >>>>> then hangs >>>>> and I cannot see any laser ranges or click on the menus anymore. >>>>> The only >>>>> way to get out is to kill the terminal window that I launched >>>>> playerv >>>>> from. >>>>> >>>>> If I leave playerv running (in a hung state) for a while, >>>>> eventually the >>>>> terminal I launched playerv from displays: >>>>> >>>>> playerc error : queue overflow; discarding packets >>>>> >>>>> ...a lot of times. >>>>> >>>>> Does anyone have a SICK PLS working ok with Player who can tell >>>>> me what I >>>>> need to change - I assume that there's either a cfg file issue or >>>>> the >>>>> config of the PLS itself needs changing through the SICK user >>>>> software?. >>>>> >>>>> I am using Ubuntu 6.06 LTS and Player 2.0.3 (I can't see a bug >>>>> report or >>>>> fix for this between 2.0.3 and 2.0.4) >>>>> >>>>> thanks >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >>> -- >>> View this message in context: http://www.nabble.com/SICK-PLS-config- >>> issue-tf4409923.html#a12659796 >>> 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 2005. >>> 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 2005. >> 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/SICK-PLS-config-issue-tf4409923.html#a12660977 Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Richard v. <va...@cs...> - 2007-09-13 19:40:38
|
There's a laser rescale driver that converts N samples onto M samples. It may be that VFH and playerv make some poor assumptions about the number of samples, or maybe the FOV. You can investigate and possibly work around that by using the rescaling driver. Richard/ On 13-Sep-07, at 11:30 AM, XRobots wrote: > > Thanks for your reply Richard. > > I had previously tried the 'laserobstacleavoid' program with the > laser sat > on top of my WBR914 robot which otherwise works fine (for all it's own > devices) - although it drove straight forward and crashed which > made me > think that there was incorrect or no laser data. > > However, I've now tried 'playerprint laser' and you suggest, and this > produces some data which looks good and changes and you wave you > hand in > front of it - at least it doesn't hang, horray!. So it looks like > the issue > may be with playerv as you say. > > The 'unexpected packet type error' was from the terminal window > where player > itself was running, but this was only with the resolution forced to > 100 > which is incorrect for that device, so only to be expected I > suppose. It was > just the only way through tinkering that I could get anything out > of playerv > and the laser together. > > So I'll guess I'll progress with testing the VFH driver and see if > I can get > my 914 to avoid obstacles now that I know the data/comms appears to be > actually working. > > So watch out for the next instalment of: > > http://www.914pcbots.com/community/index.php? > option=com_content&task=view&id=323&Itemid=65 > > thanks again > -James > > > > > > Richard vaughan wrote: >> >> Things to look at: >> >> * It's possible that the problem is with playerv, and not the driver. >> Have you tried using another laser client, e.g. "playerprint laser"? >> >> * Is it the Player server or a client that produces the "unexpected >> packet type" error? It may be helpful to break the program in the >> debugger at that point, and find what the packet type is and post a >> backtrace here to provide some clues. >> >> Richard/ >> >> On 13-Sep-07, at 10:35 AM, XRobots wrote: >> >>> >>> I have now tried a USB-RS422 interface, which again works fine with >>> the SICK >>> Windows user software. However, the results with Player are exactly >>> identical. >>> >>> Does anybody have any idea whatsoever which hardware is really >>> supported by >>> the 'sickpls' driver or any idea what the config of it should be? >>> >>> ...anything? >>> >>> thanks >>> >>> >>> >>> XRobots wrote: >>>> >>>> A little update after I have been tinkering around, but still not >>>> fixed: >>>> >>>> I have added the line 'resolution 100' to the config file, >>>> although the >>>> resolution of the laser is 0.5 degrees so it should really be left >>>> at the >>>> default of 50. Now I get a lot more messages in the terminal that I >>>> launched Player from as follows: >>>> >>>> error : no reply from laser >>>> LASER: RLD: writing scan data >>>> LASER: RLD: waiting for ACK >>>> >>>> After about 4 of these a partial scan appears in playerv and the >>>> menus >>>> start to work again, but then I get a message that says: >>>> >>>> error : unexpected packet type >>>> >>>> ...and everything stops, leaving a corrupted looking scan in >>>> playernav. >>>> So it looks like some sort of comms error, although I don't know >>>> why it >>>> won't work with the correct setting for resolution in the config >>>> file - it >>>> still just hangs after the message I posted in the previous >>>> message. >>>> >>>> Does anyone know if the 'sickpls' driver was written for the >>>> PLS101-312 or >>>> one of the other models (PLS101-112 etc)?. >>>> >>>> This is on Player 2.0.3 but I can't see a bug / fix report for this >>>> between 2.0.3 and 2.0.4 >>>> >>>> thanks >>>> >>>> >>>> XRobots wrote: >>>>> >>>>> I have a SICK PLS101-312 which I have had working with the SICK >>>>> user >>>>> software under Windows - I can monitor the scan / perform diags >>>>> and >>>>> generally set the config as you'd expect. However, booting to >>>>> Linux on >>>>> the same PC with the same serial port and cable etc I have some >>>>> issues >>>>> getting the PLS to work under Player with the 'sickpls' driver. I >>>>> have >>>>> also tried another install of Player on a totally separate Linux >>>>> PC but >>>>> the issue is eactly the same. >>>>> >>>>> My config file is as follows, for now I have no other robotic >>>>> hardware >>>>> connected: >>>>> >>>>> driver >>>>> ( >>>>> name "sickpls" >>>>> provides ["laser:0"] >>>>> port "/dev/ttyS0" >>>>> rate 38400 >>>>> ) >>>>> >>>>> The baud rate is correct as I already set this to be permananent >>>>> with the >>>>> SICK user software under Windows. >>>>> >>>>> When I start Player using this config file and run playerv I can >>>>> see the >>>>> 'laser:0 (sickpls)' on the menu of devices and I can click on >>>>> 'Subscribe'. The terminal window that I have run player from >>>>> displays the >>>>> following messages: >>>>> >>>>> Listening on ports: 6665 >>>>> accepted client 0 on port 6665, fd 5 >>>>> Laser initialising (/dev/ttyS0) >>>>> LASER: change TERM speed: 38400 >>>>> LASER: RLD: writing scan data >>>>> LASER: RLD: waiting for ACK >>>>> LASER: RLD: scan data OK >>>>> laser ready >>>>> LASER: RLD: writing scan data >>>>> LASER: RLD: waiting for ACK >>>>> LASER: RLD: scan data OK >>>>> >>>>> So that looks ok to me I think(?). However, the playerv window >>>>> then hangs >>>>> and I cannot see any laser ranges or click on the menus anymore. >>>>> The only >>>>> way to get out is to kill the terminal window that I launched >>>>> playerv >>>>> from. >>>>> >>>>> If I leave playerv running (in a hung state) for a while, >>>>> eventually the >>>>> terminal I launched playerv from displays: >>>>> >>>>> playerc error : queue overflow; discarding packets >>>>> >>>>> ...a lot of times. >>>>> >>>>> Does anyone have a SICK PLS working ok with Player who can tell >>>>> me what I >>>>> need to change - I assume that there's either a cfg file issue or >>>>> the >>>>> config of the PLS itself needs changing through the SICK user >>>>> software?. >>>>> >>>>> I am using Ubuntu 6.06 LTS and Player 2.0.3 (I can't see a bug >>>>> report or >>>>> fix for this between 2.0.3 and 2.0.4) >>>>> >>>>> thanks >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> >>> -- >>> View this message in context: http://www.nabble.com/SICK-PLS-config- >>> issue-tf4409923.html#a12659796 >>> 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 2005. >>> 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 2005. >> 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/SICK-PLS-config- > issue-tf4409923.html#a12660783 > 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 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users |
From: Toby C. <tco...@pl...> - 2007-09-13 20:03:21
|
Playerv could be relying on a configuration request that is not supported by that particular laser driver (for a long time stage and the lms200 were the most commonly used laser devices, and the interface is somewhat tailored to the lms200). Have a look at the playerv code for the laser interface and check out what requests it makes at its start up, it may be silently failing on a rejected config request. Toby On 14/09/2007, Richard vaughan <va...@cs...> wrote: > > > There's a laser rescale driver that converts N samples onto M > samples. It may be that VFH and playerv make some poor assumptions > about the number of samples, or maybe the FOV. You can investigate > and possibly work around that by using the rescaling driver. > > Richard/ > > On 13-Sep-07, at 11:30 AM, XRobots wrote: > > > > > Thanks for your reply Richard. > > > > I had previously tried the 'laserobstacleavoid' program with the > > laser sat > > on top of my WBR914 robot which otherwise works fine (for all it's own > > devices) - although it drove straight forward and crashed which > > made me > > think that there was incorrect or no laser data. > > > > However, I've now tried 'playerprint laser' and you suggest, and this > > produces some data which looks good and changes and you wave you > > hand in > > front of it - at least it doesn't hang, horray!. So it looks like > > the issue > > may be with playerv as you say. > > > > The 'unexpected packet type error' was from the terminal window > > where player > > itself was running, but this was only with the resolution forced to > > 100 > > which is incorrect for that device, so only to be expected I > > suppose. It was > > just the only way through tinkering that I could get anything out > > of playerv > > and the laser together. > > > > So I'll guess I'll progress with testing the VFH driver and see if > > I can get > > my 914 to avoid obstacles now that I know the data/comms appears to be > > actually working. > > > > So watch out for the next instalment of: > > > > http://www.914pcbots.com/community/index.php? > > option=com_content&task=view&id=323&Itemid=65 > > > > thanks again > > -James > > > > > > > > > > > > Richard vaughan wrote: > >> > >> Things to look at: > >> > >> * It's possible that the problem is with playerv, and not the driver. > >> Have you tried using another laser client, e.g. "playerprint laser"? > >> > >> * Is it the Player server or a client that produces the "unexpected > >> packet type" error? It may be helpful to break the program in the > >> debugger at that point, and find what the packet type is and post a > >> backtrace here to provide some clues. > >> > >> Richard/ > >> > >> On 13-Sep-07, at 10:35 AM, XRobots wrote: > >> > >>> > >>> I have now tried a USB-RS422 interface, which again works fine with > >>> the SICK > >>> Windows user software. However, the results with Player are exactly > >>> identical. > >>> > >>> Does anybody have any idea whatsoever which hardware is really > >>> supported by > >>> the 'sickpls' driver or any idea what the config of it should be? > >>> > >>> ...anything? > >>> > >>> thanks > >>> > >>> > >>> > >>> XRobots wrote: > >>>> > >>>> A little update after I have been tinkering around, but still not > >>>> fixed: > >>>> > >>>> I have added the line 'resolution 100' to the config file, > >>>> although the > >>>> resolution of the laser is 0.5 degrees so it should really be left > >>>> at the > >>>> default of 50. Now I get a lot more messages in the terminal that I > >>>> launched Player from as follows: > >>>> > >>>> error : no reply from laser > >>>> LASER: RLD: writing scan data > >>>> LASER: RLD: waiting for ACK > >>>> > >>>> After about 4 of these a partial scan appears in playerv and the > >>>> menus > >>>> start to work again, but then I get a message that says: > >>>> > >>>> error : unexpected packet type > >>>> > >>>> ...and everything stops, leaving a corrupted looking scan in > >>>> playernav. > >>>> So it looks like some sort of comms error, although I don't know > >>>> why it > >>>> won't work with the correct setting for resolution in the config > >>>> file - it > >>>> still just hangs after the message I posted in the previous > >>>> message. > >>>> > >>>> Does anyone know if the 'sickpls' driver was written for the > >>>> PLS101-312 or > >>>> one of the other models (PLS101-112 etc)?. > >>>> > >>>> This is on Player 2.0.3 but I can't see a bug / fix report for this > >>>> between 2.0.3 and 2.0.4 > >>>> > >>>> thanks > >>>> > >>>> > >>>> XRobots wrote: > >>>>> > >>>>> I have a SICK PLS101-312 which I have had working with the SICK > >>>>> user > >>>>> software under Windows - I can monitor the scan / perform diags > >>>>> and > >>>>> generally set the config as you'd expect. However, booting to > >>>>> Linux on > >>>>> the same PC with the same serial port and cable etc I have some > >>>>> issues > >>>>> getting the PLS to work under Player with the 'sickpls' driver. I > >>>>> have > >>>>> also tried another install of Player on a totally separate Linux > >>>>> PC but > >>>>> the issue is eactly the same. > >>>>> > >>>>> My config file is as follows, for now I have no other robotic > >>>>> hardware > >>>>> connected: > >>>>> > >>>>> driver > >>>>> ( > >>>>> name "sickpls" > >>>>> provides ["laser:0"] > >>>>> port "/dev/ttyS0" > >>>>> rate 38400 > >>>>> ) > >>>>> > >>>>> The baud rate is correct as I already set this to be permananent > >>>>> with the > >>>>> SICK user software under Windows. > >>>>> > >>>>> When I start Player using this config file and run playerv I can > >>>>> see the > >>>>> 'laser:0 (sickpls)' on the menu of devices and I can click on > >>>>> 'Subscribe'. The terminal window that I have run player from > >>>>> displays the > >>>>> following messages: > >>>>> > >>>>> Listening on ports: 6665 > >>>>> accepted client 0 on port 6665, fd 5 > >>>>> Laser initialising (/dev/ttyS0) > >>>>> LASER: change TERM speed: 38400 > >>>>> LASER: RLD: writing scan data > >>>>> LASER: RLD: waiting for ACK > >>>>> LASER: RLD: scan data OK > >>>>> laser ready > >>>>> LASER: RLD: writing scan data > >>>>> LASER: RLD: waiting for ACK > >>>>> LASER: RLD: scan data OK > >>>>> > >>>>> So that looks ok to me I think(?). However, the playerv window > >>>>> then hangs > >>>>> and I cannot see any laser ranges or click on the menus anymore. > >>>>> The only > >>>>> way to get out is to kill the terminal window that I launched > >>>>> playerv > >>>>> from. > >>>>> > >>>>> If I leave playerv running (in a hung state) for a while, > >>>>> eventually the > >>>>> terminal I launched playerv from displays: > >>>>> > >>>>> playerc error : queue overflow; discarding packets > >>>>> > >>>>> ...a lot of times. > >>>>> > >>>>> Does anyone have a SICK PLS working ok with Player who can tell > >>>>> me what I > >>>>> need to change - I assume that there's either a cfg file issue or > >>>>> the > >>>>> config of the PLS itself needs changing through the SICK user > >>>>> software?. > >>>>> > >>>>> I am using Ubuntu 6.06 LTS and Player 2.0.3 (I can't see a bug > >>>>> report or > >>>>> fix for this between 2.0.3 and 2.0.4) > >>>>> > >>>>> thanks > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>> > >>>> > >>> > >>> -- > >>> View this message in context: http://www.nabble.com/SICK-PLS-config- > >>> issue-tf4409923.html#a12659796 > >>> 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 2005. > >>> 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 2005. > >> 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/SICK-PLS-config- > > issue-tf4409923.html#a12660783 > > 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 2005. > > 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 2005. > 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: XRobots <ja...@xr...> - 2007-09-14 17:32:44
|
I've now tried the laser out with the example Python script that is supplied with the Python client library. With the laser stuff stripped out it makes my WBR914 robot turn around and back again as it should. However, when I use it as it comes to read the laser geometry it hangs at this point (so I get the robot size printed but nothing further). After about 30 seconds the message appears in the window where I ran the script from that says something along the lines of 'queue overflow: discarding packets' - a lot of times. Obviously playerv is not being used here so it seems that the only common thing is the 'sickpls' driver. "playerprint laser" still shows me some raw data however. Does anyone else actually have a working SICK PLS with Player?. Unfortunately I'm not clever enough to debug the code myself ;-) thanks Toby Collett-3 wrote: > > Playerv could be relying on a configuration request that is not supported > by > that particular laser driver (for a long time stage and the lms200 were > the > most commonly used laser devices, and the interface is somewhat tailored > to > the lms200). > > Have a look at the playerv code for the laser interface and check out what > requests it makes at its start up, it may be silently failing on a > rejected > config request. > > Toby > > On 14/09/2007, Richard vaughan <va...@cs...> wrote: >> >> >> There's a laser rescale driver that converts N samples onto M >> samples. It may be that VFH and playerv make some poor assumptions >> about the number of samples, or maybe the FOV. You can investigate >> and possibly work around that by using the rescaling driver. >> >> Richard/ >> >> On 13-Sep-07, at 11:30 AM, XRobots wrote: >> >> > >> > Thanks for your reply Richard. >> > >> > I had previously tried the 'laserobstacleavoid' program with the >> > laser sat >> > on top of my WBR914 robot which otherwise works fine (for all it's own >> > devices) - although it drove straight forward and crashed which >> > made me >> > think that there was incorrect or no laser data. >> > >> > However, I've now tried 'playerprint laser' and you suggest, and this >> > produces some data which looks good and changes and you wave you >> > hand in >> > front of it - at least it doesn't hang, horray!. So it looks like >> > the issue >> > may be with playerv as you say. >> > >> > The 'unexpected packet type error' was from the terminal window >> > where player >> > itself was running, but this was only with the resolution forced to >> > 100 >> > which is incorrect for that device, so only to be expected I >> > suppose. It was >> > just the only way through tinkering that I could get anything out >> > of playerv >> > and the laser together. >> > >> > So I'll guess I'll progress with testing the VFH driver and see if >> > I can get >> > my 914 to avoid obstacles now that I know the data/comms appears to be >> > actually working. >> > >> > So watch out for the next instalment of: >> > >> > http://www.914pcbots.com/community/index.php? >> > option=com_content&task=view&id=323&Itemid=65 >> > >> > thanks again >> > -James >> > >> > >> > >> > >> > >> > Richard vaughan wrote: >> >> >> >> Things to look at: >> >> >> >> * It's possible that the problem is with playerv, and not the driver. >> >> Have you tried using another laser client, e.g. "playerprint laser"? >> >> >> >> * Is it the Player server or a client that produces the "unexpected >> >> packet type" error? It may be helpful to break the program in the >> >> debugger at that point, and find what the packet type is and post a >> >> backtrace here to provide some clues. >> >> >> >> Richard/ >> >> >> >> On 13-Sep-07, at 10:35 AM, XRobots wrote: >> >> >> >>> >> >>> I have now tried a USB-RS422 interface, which again works fine with >> >>> the SICK >> >>> Windows user software. However, the results with Player are exactly >> >>> identical. >> >>> >> >>> Does anybody have any idea whatsoever which hardware is really >> >>> supported by >> >>> the 'sickpls' driver or any idea what the config of it should be? >> >>> >> >>> ...anything? >> >>> >> >>> thanks >> >>> >> >>> >> >>> >> >>> XRobots wrote: >> >>>> >> >>>> A little update after I have been tinkering around, but still not >> >>>> fixed: >> >>>> >> >>>> I have added the line 'resolution 100' to the config file, >> >>>> although the >> >>>> resolution of the laser is 0.5 degrees so it should really be left >> >>>> at the >> >>>> default of 50. Now I get a lot more messages in the terminal that I >> >>>> launched Player from as follows: >> >>>> >> >>>> error : no reply from laser >> >>>> LASER: RLD: writing scan data >> >>>> LASER: RLD: waiting for ACK >> >>>> >> >>>> After about 4 of these a partial scan appears in playerv and the >> >>>> menus >> >>>> start to work again, but then I get a message that says: >> >>>> >> >>>> error : unexpected packet type >> >>>> >> >>>> ...and everything stops, leaving a corrupted looking scan in >> >>>> playernav. >> >>>> So it looks like some sort of comms error, although I don't know >> >>>> why it >> >>>> won't work with the correct setting for resolution in the config >> >>>> file - it >> >>>> still just hangs after the message I posted in the previous >> >>>> message. >> >>>> >> >>>> Does anyone know if the 'sickpls' driver was written for the >> >>>> PLS101-312 or >> >>>> one of the other models (PLS101-112 etc)?. >> >>>> >> >>>> This is on Player 2.0.3 but I can't see a bug / fix report for this >> >>>> between 2.0.3 and 2.0.4 >> >>>> >> >>>> thanks >> >>>> >> >>>> >> >>>> XRobots wrote: >> >>>>> >> >>>>> I have a SICK PLS101-312 which I have had working with the SICK >> >>>>> user >> >>>>> software under Windows - I can monitor the scan / perform diags >> >>>>> and >> >>>>> generally set the config as you'd expect. However, booting to >> >>>>> Linux on >> >>>>> the same PC with the same serial port and cable etc I have some >> >>>>> issues >> >>>>> getting the PLS to work under Player with the 'sickpls' driver. I >> >>>>> have >> >>>>> also tried another install of Player on a totally separate Linux >> >>>>> PC but >> >>>>> the issue is eactly the same. >> >>>>> >> >>>>> My config file is as follows, for now I have no other robotic >> >>>>> hardware >> >>>>> connected: >> >>>>> >> >>>>> driver >> >>>>> ( >> >>>>> name "sickpls" >> >>>>> provides ["laser:0"] >> >>>>> port "/dev/ttyS0" >> >>>>> rate 38400 >> >>>>> ) >> >>>>> >> >>>>> The baud rate is correct as I already set this to be permananent >> >>>>> with the >> >>>>> SICK user software under Windows. >> >>>>> >> >>>>> When I start Player using this config file and run playerv I can >> >>>>> see the >> >>>>> 'laser:0 (sickpls)' on the menu of devices and I can click on >> >>>>> 'Subscribe'. The terminal window that I have run player from >> >>>>> displays the >> >>>>> following messages: >> >>>>> >> >>>>> Listening on ports: 6665 >> >>>>> accepted client 0 on port 6665, fd 5 >> >>>>> Laser initialising (/dev/ttyS0) >> >>>>> LASER: change TERM speed: 38400 >> >>>>> LASER: RLD: writing scan data >> >>>>> LASER: RLD: waiting for ACK >> >>>>> LASER: RLD: scan data OK >> >>>>> laser ready >> >>>>> LASER: RLD: writing scan data >> >>>>> LASER: RLD: waiting for ACK >> >>>>> LASER: RLD: scan data OK >> >>>>> >> >>>>> So that looks ok to me I think(?). However, the playerv window >> >>>>> then hangs >> >>>>> and I cannot see any laser ranges or click on the menus anymore. >> >>>>> The only >> >>>>> way to get out is to kill the terminal window that I launched >> >>>>> playerv >> >>>>> from. >> >>>>> >> >>>>> If I leave playerv running (in a hung state) for a while, >> >>>>> eventually the >> >>>>> terminal I launched playerv from displays: >> >>>>> >> >>>>> playerc error : queue overflow; discarding packets >> >>>>> >> >>>>> ...a lot of times. >> >>>>> >> >>>>> Does anyone have a SICK PLS working ok with Player who can tell >> >>>>> me what I >> >>>>> need to change - I assume that there's either a cfg file issue or >> >>>>> the >> >>>>> config of the PLS itself needs changing through the SICK user >> >>>>> software?. >> >>>>> >> >>>>> I am using Ubuntu 6.06 LTS and Player 2.0.3 (I can't see a bug >> >>>>> report or >> >>>>> fix for this between 2.0.3 and 2.0.4) >> >>>>> >> >>>>> thanks >> >>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>> >> >>>> >> >>> >> >>> -- >> >>> View this message in context: http://www.nabble.com/SICK-PLS-config- >> >>> issue-tf4409923.html#a12659796 >> >>> 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 2005. >> >>> 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 2005. >> >> 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/SICK-PLS-config- >> > issue-tf4409923.html#a12660783 >> > 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 2005. >> > 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 2005. >> 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 2005. > 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/SICK-PLS-config-issue-tf4409923.html#a12680353 Sent from the playerstage-users mailing list archive at Nabble.com. |
From: Richard v. <va...@cs...> - 2007-09-14 17:47:52
|
Looks like Toby was correct and the PLS does not provide geometry information. That's not a bug - devices are not *required* to support that, but it is assumed by playerv. Most robot control code doesn't need this information dynamically, unless you want to support a variety of robot configurations. You may be able to get by with the driver as it is, but without playerv/nav. If you want to use these tools you need to extend the driver. It may not be as hard as you think. Look at the lms200 driver for an example. Richard/ On 14-Sep-07, at 10:32 AM, XRobots wrote: > > I've now tried the laser out with the example Python script that is > supplied > with the Python client library. With the laser stuff stripped out > it makes > my WBR914 robot turn around and back again as it should. > > However, when I use it as it comes to read the laser geometry it > hangs at > this point (so I get the robot size printed but nothing further). > After > about 30 seconds the message appears in the window where I ran the > script > from that says something along the lines of 'queue overflow: > discarding > packets' - a lot of times. > > Obviously playerv is not being used here so it seems that the only > common > thing is the 'sickpls' driver. "playerprint laser" still shows me > some raw > data however. > > Does anyone else actually have a working SICK PLS with Player?. > Unfortunately I'm not clever enough to debug the code myself ;-) > > thanks > > > > > Toby Collett-3 wrote: >> >> Playerv could be relying on a configuration request that is not >> supported >> by >> that particular laser driver (for a long time stage and the lms200 >> were >> the >> most commonly used laser devices, and the interface is somewhat >> tailored >> to >> the lms200). >> >> Have a look at the playerv code for the laser interface and check >> out what >> requests it makes at its start up, it may be silently failing on a >> rejected >> config request. >> >> Toby >> >> On 14/09/2007, Richard vaughan <va...@cs...> wrote: >>> >>> >>> There's a laser rescale driver that converts N samples onto M >>> samples. It may be that VFH and playerv make some poor assumptions >>> about the number of samples, or maybe the FOV. You can investigate >>> and possibly work around that by using the rescaling driver. >>> >>> Richard/ >>> >>> On 13-Sep-07, at 11:30 AM, XRobots wrote: >>> >>>> >>>> Thanks for your reply Richard. >>>> >>>> I had previously tried the 'laserobstacleavoid' program with the >>>> laser sat >>>> on top of my WBR914 robot which otherwise works fine (for all >>>> it's own >>>> devices) - although it drove straight forward and crashed which >>>> made me >>>> think that there was incorrect or no laser data. >>>> >>>> However, I've now tried 'playerprint laser' and you suggest, and >>>> this >>>> produces some data which looks good and changes and you wave you >>>> hand in >>>> front of it - at least it doesn't hang, horray!. So it looks like >>>> the issue >>>> may be with playerv as you say. >>>> >>>> The 'unexpected packet type error' was from the terminal window >>>> where player >>>> itself was running, but this was only with the resolution forced to >>>> 100 >>>> which is incorrect for that device, so only to be expected I >>>> suppose. It was >>>> just the only way through tinkering that I could get anything out >>>> of playerv >>>> and the laser together. >>>> >>>> So I'll guess I'll progress with testing the VFH driver and see if >>>> I can get >>>> my 914 to avoid obstacles now that I know the data/comms appears >>>> to be >>>> actually working. >>>> >>>> So watch out for the next instalment of: >>>> >>>> http://www.914pcbots.com/community/index.php? >>>> option=com_content&task=view&id=323&Itemid=65 >>>> >>>> thanks again >>>> -James >>>> >>>> >>>> >>>> >>>> >>>> Richard vaughan wrote: >>>>> >>>>> Things to look at: >>>>> >>>>> * It's possible that the problem is with playerv, and not the >>>>> driver. >>>>> Have you tried using another laser client, e.g. "playerprint >>>>> laser"? >>>>> >>>>> * Is it the Player server or a client that produces the >>>>> "unexpected >>>>> packet type" error? It may be helpful to break the program in the >>>>> debugger at that point, and find what the packet type is and >>>>> post a >>>>> backtrace here to provide some clues. >>>>> >>>>> Richard/ >>>>> >>>>> On 13-Sep-07, at 10:35 AM, XRobots wrote: >>>>> >>>>>> >>>>>> I have now tried a USB-RS422 interface, which again works fine >>>>>> with >>>>>> the SICK >>>>>> Windows user software. However, the results with Player are >>>>>> exactly >>>>>> identical. >>>>>> >>>>>> Does anybody have any idea whatsoever which hardware is really >>>>>> supported by >>>>>> the 'sickpls' driver or any idea what the config of it should be? >>>>>> >>>>>> ...anything? >>>>>> >>>>>> thanks >>>>>> >>>>>> >>>>>> >>>>>> XRobots wrote: >>>>>>> >>>>>>> A little update after I have been tinkering around, but still >>>>>>> not >>>>>>> fixed: >>>>>>> >>>>>>> I have added the line 'resolution 100' to the config file, >>>>>>> although the >>>>>>> resolution of the laser is 0.5 degrees so it should really be >>>>>>> left >>>>>>> at the >>>>>>> default of 50. Now I get a lot more messages in the terminal >>>>>>> that I >>>>>>> launched Player from as follows: >>>>>>> >>>>>>> error : no reply from laser >>>>>>> LASER: RLD: writing scan data >>>>>>> LASER: RLD: waiting for ACK >>>>>>> >>>>>>> After about 4 of these a partial scan appears in playerv and the >>>>>>> menus >>>>>>> start to work again, but then I get a message that says: >>>>>>> >>>>>>> error : unexpected packet type >>>>>>> >>>>>>> ...and everything stops, leaving a corrupted looking scan in >>>>>>> playernav. >>>>>>> So it looks like some sort of comms error, although I don't know >>>>>>> why it >>>>>>> won't work with the correct setting for resolution in the config >>>>>>> file - it >>>>>>> still just hangs after the message I posted in the previous >>>>>>> message. >>>>>>> >>>>>>> Does anyone know if the 'sickpls' driver was written for the >>>>>>> PLS101-312 or >>>>>>> one of the other models (PLS101-112 etc)?. >>>>>>> >>>>>>> This is on Player 2.0.3 but I can't see a bug / fix report >>>>>>> for this >>>>>>> between 2.0.3 and 2.0.4 >>>>>>> >>>>>>> thanks >>>>>>> >>>>>>> >>>>>>> XRobots wrote: >>>>>>>> >>>>>>>> I have a SICK PLS101-312 which I have had working with the SICK >>>>>>>> user >>>>>>>> software under Windows - I can monitor the scan / perform diags >>>>>>>> and >>>>>>>> generally set the config as you'd expect. However, booting to >>>>>>>> Linux on >>>>>>>> the same PC with the same serial port and cable etc I have some >>>>>>>> issues >>>>>>>> getting the PLS to work under Player with the 'sickpls' >>>>>>>> driver. I >>>>>>>> have >>>>>>>> also tried another install of Player on a totally separate >>>>>>>> Linux >>>>>>>> PC but >>>>>>>> the issue is eactly the same. >>>>>>>> >>>>>>>> My config file is as follows, for now I have no other robotic >>>>>>>> hardware >>>>>>>> connected: >>>>>>>> >>>>>>>> driver >>>>>>>> ( >>>>>>>> name "sickpls" >>>>>>>> provides ["laser:0"] >>>>>>>> port "/dev/ttyS0" >>>>>>>> rate 38400 >>>>>>>> ) >>>>>>>> >>>>>>>> The baud rate is correct as I already set this to be >>>>>>>> permananent >>>>>>>> with the >>>>>>>> SICK user software under Windows. >>>>>>>> >>>>>>>> When I start Player using this config file and run playerv I >>>>>>>> can >>>>>>>> see the >>>>>>>> 'laser:0 (sickpls)' on the menu of devices and I can click on >>>>>>>> 'Subscribe'. The terminal window that I have run player from >>>>>>>> displays the >>>>>>>> following messages: >>>>>>>> >>>>>>>> Listening on ports: 6665 >>>>>>>> accepted client 0 on port 6665, fd 5 >>>>>>>> Laser initialising (/dev/ttyS0) >>>>>>>> LASER: change TERM speed: 38400 >>>>>>>> LASER: RLD: writing scan data >>>>>>>> LASER: RLD: waiting for ACK >>>>>>>> LASER: RLD: scan data OK >>>>>>>> laser ready >>>>>>>> LASER: RLD: writing scan data >>>>>>>> LASER: RLD: waiting for ACK >>>>>>>> LASER: RLD: scan data OK >>>>>>>> >>>>>>>> So that looks ok to me I think(?). However, the playerv window >>>>>>>> then hangs >>>>>>>> and I cannot see any laser ranges or click on the menus >>>>>>>> anymore. >>>>>>>> The only >>>>>>>> way to get out is to kill the terminal window that I launched >>>>>>>> playerv >>>>>>>> from. >>>>>>>> >>>>>>>> If I leave playerv running (in a hung state) for a while, >>>>>>>> eventually the >>>>>>>> terminal I launched playerv from displays: >>>>>>>> >>>>>>>> playerc error : queue overflow; discarding packets >>>>>>>> >>>>>>>> ...a lot of times. >>>>>>>> >>>>>>>> Does anyone have a SICK PLS working ok with Player who can tell >>>>>>>> me what I >>>>>>>> need to change - I assume that there's either a cfg file >>>>>>>> issue or >>>>>>>> the >>>>>>>> config of the PLS itself needs changing through the SICK user >>>>>>>> software?. >>>>>>>> >>>>>>>> I am using Ubuntu 6.06 LTS and Player 2.0.3 (I can't see a bug >>>>>>>> report or >>>>>>>> fix for this between 2.0.3 and 2.0.4) >>>>>>>> >>>>>>>> thanks >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: http://www.nabble.com/SICK-PLS- >>>>>> config- >>>>>> issue-tf4409923.html#a12659796 >>>>>> 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 2005. >>>>>> 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 2005. >>>>> 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/SICK-PLS- >>>> config- >>>> issue-tf4409923.html#a12660783 >>>> 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 2005. >>>> 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 2005. >>> 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 2005. >> 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/SICK-PLS-config- > issue-tf4409923.html#a12680353 > 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 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Playerstage-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-users |
From: XRobots <ja...@xr...> - 2007-09-14 18:32:08
|
Ok, so I took the getting laser geometry and printing laser pose part out of the script and now it runs until the end turning the robot as it should. However it doesn't seem to print any laser range data - it just prints a line after each "Robot pose: (-0.000, -0.000, <value>)" line, that says "Partial laser scan:" but with no values after it. The terminal window where player is running from says "warning: encoding failed on message from 6:0 with type 1:1" a few times, and eventually "Read checksum error", then "Error resetting event status". Presumably this should work though, to at least display the laser range data? thanks Richard vaughan wrote: > > > Looks like Toby was correct and the PLS does not provide geometry > information. > That's not a bug - devices are not *required* to support that, but it > is assumed by playerv. Most robot control code doesn't need this > information dynamically, unless you want to support a variety of > robot configurations. You may be able to get by with the driver as it > is, but without playerv/nav. > > If you want to use these tools you need to extend the driver. It may > not be as hard as you think. Look at the lms200 driver for an example. > > Richard/ > > On 14-Sep-07, at 10:32 AM, XRobots wrote: > >> >> I've now tried the laser out with the example Python script that is >> supplied >> with the Python client library. With the laser stuff stripped out >> it makes >> my WBR914 robot turn around and back again as it should. >> >> However, when I use it as it comes to read the laser geometry it >> hangs at >> this point (so I get the robot size printed but nothing further). >> After >> about 30 seconds the message appears in the window where I ran the >> script >> from that says something along the lines of 'queue overflow: >> discarding >> packets' - a lot of times. >> >> Obviously playerv is not being used here so it seems that the only >> common >> thing is the 'sickpls' driver. "playerprint laser" still shows me >> some raw >> data however. >> >> Does anyone else actually have a working SICK PLS with Player?. >> Unfortunately I'm not clever enough to debug the code myself ;-) >> >> thanks >> >> >> >> >> Toby Collett-3 wrote: >>> >>> Playerv could be relying on a configuration request that is not >>> supported >>> by >>> that particular laser driver (for a long time stage and the lms200 >>> were >>> the >>> most commonly used laser devices, and the interface is somewhat >>> tailored >>> to >>> the lms200). >>> >>> Have a look at the playerv code for the laser interface and check >>> out what >>> requests it makes at its start up, it may be silently failing on a >>> rejected >>> config request. >>> >>> Toby >>> >>> On 14/09/2007, Richard vaughan <va...@cs...> wrote: >>>> >>>> >>>> There's a laser rescale driver that converts N samples onto M >>>> samples. It may be that VFH and playerv make some poor assumptions >>>> about the number of samples, or maybe the FOV. You can investigate >>>> and possibly work around that by using the rescaling driver. >>>> >>>> Richard/ >>>> >>>> On 13-Sep-07, at 11:30 AM, XRobots wrote: >>>> >>>>> >>>>> Thanks for your reply Richard. >>>>> >>>>> I had previously tried the 'laserobstacleavoid' program with the >>>>> laser sat >>>>> on top of my WBR914 robot which otherwise works fine (for all >>>>> it's own >>>>> devices) - although it drove straight forward and crashed which >>>>> made me >>>>> think that there was incorrect or no laser data. >>>>> >>>>> However, I've now tried 'playerprint laser' and you suggest, and >>>>> this >>>>> produces some data which looks good and changes and you wave you >>>>> hand in >>>>> front of it - at least it doesn't hang, horray!. So it looks like >>>>> the issue >>>>> may be with playerv as you say. >>>>> >>>>> The 'unexpected packet type error' was from the terminal window >>>>> where player >>>>> itself was running, but this was only with the resolution forced to >>>>> 100 >>>>> which is incorrect for that device, so only to be expected I >>>>> suppose. It was >>>>> just the only way through tinkering that I could get anything out >>>>> of playerv >>>>> and the laser together. >>>>> >>>>> So I'll guess I'll progress with testing the VFH driver and see if >>>>> I can get >>>>> my 914 to avoid obstacles now that I know the data/comms appears >>>>> to be >>>>> actually working. >>>>> >>>>> So watch out for the next instalment of: >>>>> >>>>> http://www.914pcbots.com/community/index.php? >>>>> option=com_content&task=view&id=323&Itemid=65 >>>>> >>>>> thanks again >>>>> -James >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> Richard vaughan wrote: >>>>>> >>>>>> Things to look at: >>>>>> >>>>>> * It's possible that the problem is with playerv, and not the >>>>>> driver. >>>>>> Have you tried using another laser client, e.g. "playerprint >>>>>> laser"? >>>>>> >>>>>> * Is it the Player server or a client that produces the >>>>>> "unexpected >>>>>> packet type" error? It may be helpful to break the program in the >>>>>> debugger at that point, and find what the packet type is and >>>>>> post a >>>>>> backtrace here to provide some clues. >>>>>> >>>>>> Richard/ >>>>>> >>>>>> On 13-Sep-07, at 10:35 AM, XRobots wrote: >>>>>> >>>>>>> >>>>>>> I have now tried a USB-RS422 interface, which again works fine >>>>>>> with >>>>>>> the SICK >>>>>>> Windows user software. However, the results with Player are >>>>>>> exactly >>>>>>> identical. >>>>>>> >>>>>>> Does anybody have any idea whatsoever which hardware is really >>>>>>> supported by >>>>>>> the 'sickpls' driver or any idea what the config of it should be? >>>>>>> >>>>>>> ...anything? >>>>>>> >>>>>>> thanks >>>>>>> >>>>>>> >>>>>>> >>>>>>> XRobots wrote: >>>>>>>> >>>>>>>> A little update after I have been tinkering around, but still >>>>>>>> not >>>>>>>> fixed: >>>>>>>> >>>>>>>> I have added the line 'resolution 100' to the config file, >>>>>>>> although the >>>>>>>> resolution of the laser is 0.5 degrees so it should really be >>>>>>>> left >>>>>>>> at the >>>>>>>> default of 50. Now I get a lot more messages in the terminal >>>>>>>> that I >>>>>>>> launched Player from as follows: >>>>>>>> >>>>>>>> error : no reply from laser >>>>>>>> LASER: RLD: writing scan data >>>>>>>> LASER: RLD: waiting for ACK >>>>>>>> >>>>>>>> After about 4 of these a partial scan appears in playerv and the >>>>>>>> menus >>>>>>>> start to work again, but then I get a message that says: >>>>>>>> >>>>>>>> error : unexpected packet type >>>>>>>> >>>>>>>> ...and everything stops, leaving a corrupted looking scan in >>>>>>>> playernav. >>>>>>>> So it looks like some sort of comms error, although I don't know >>>>>>>> why it >>>>>>>> won't work with the correct setting for resolution in the config >>>>>>>> file - it >>>>>>>> still just hangs after the message I posted in the previous >>>>>>>> message. >>>>>>>> >>>>>>>> Does anyone know if the 'sickpls' driver was written for the >>>>>>>> PLS101-312 or >>>>>>>> one of the other models (PLS101-112 etc)?. >>>>>>>> >>>>>>>> This is on Player 2.0.3 but I can't see a bug / fix report >>>>>>>> for this >>>>>>>> between 2.0.3 and 2.0.4 >>>>>>>> >>>>>>>> thanks >>>>>>>> >>>>>>>> >>>>>>>> XRobots wrote: >>>>>>>>> >>>>>>>>> I have a SICK PLS101-312 which I have had working with the SICK >>>>>>>>> user >>>>>>>>> software under Windows - I can monitor the scan / perform diags >>>>>>>>> and >>>>>>>>> generally set the config as you'd expect. However, booting to >>>>>>>>> Linux on >>>>>>>>> the same PC with the same serial port and cable etc I have some >>>>>>>>> issues >>>>>>>>> getting the PLS to work under Player with the 'sickpls' >>>>>>>>> driver. I >>>>>>>>> have >>>>>>>>> also tried another install of Player on a totally separate >>>>>>>>> Linux >>>>>>>>> PC but >>>>>>>>> the issue is eactly the same. >>>>>>>>> >>>>>>>>> My config file is as follows, for now I have no other robotic >>>>>>>>> hardware >>>>>>>>> connected: >>>>>>>>> >>>>>>>>> driver >>>>>>>>> ( >>>>>>>>> name "sickpls" >>>>>>>>> provides ["laser:0"] >>>>>>>>> port "/dev/ttyS0" >>>>>>>>> rate 38400 >>>>>>>>> ) >>>>>>>>> >>>>>>>>> The baud rate is correct as I already set this to be >>>>>>>>> permananent >>>>>>>>> with the >>>>>>>>> SICK user software under Windows. >>>>>>>>> >>>>>>>>> When I start Player using this config file and run playerv I >>>>>>>>> can >>>>>>>>> see the >>>>>>>>> 'laser:0 (sickpls)' on the menu of devices and I can click on >>>>>>>>> 'Subscribe'. The terminal window that I have run player from >>>>>>>>> displays the >>>>>>>>> following messages: >>>>>>>>> >>>>>>>>> Listening on ports: 6665 >>>>>>>>> accepted client 0 on port 6665, fd 5 >>>>>>>>> Laser initialising (/dev/ttyS0) >>>>>>>>> LASER: change TERM speed: 38400 >>>>>>>>> LASER: RLD: writing scan data >>>>>>>>> LASER: RLD: waiting for ACK >>>>>>>>> LASER: RLD: scan data OK >>>>>>>>> laser ready >>>>>>>>> LASER: RLD: writing scan data >>>>>>>>> LASER: RLD: waiting for ACK >>>>>>>>> LASER: RLD: scan data OK >>>>>>>>> >>>>>>>>> So that looks ok to me I think(?). However, the playerv window >>>>>>>>> then hangs >>>>>>>>> and I cannot see any laser ranges or click on the menus >>>>>>>>> anymore. >>>>>>>>> The only >>>>>>>>> way to get out is to kill the terminal window that I launched >>>>>>>>> playerv >>>>>>>>> from. >>>>>>>>> >>>>>>>>> If I leave playerv running (in a hung state) for a while, >>>>>>>>> eventually the >>>>>>>>> terminal I launched playerv from displays: >>>>>>>>> >>>>>>>>> playerc error : queue overflow; discarding packets >>>>>>>>> >>>>>>>>> ...a lot of times. >>>>>>>>> >>>>>>>>> Does anyone have a SICK PLS working ok with Player who can tell >>>>>>>>> me what I >>>>>>>>> need to change - I assume that there's either a cfg file >>>>>>>>> issue or >>>>>>>>> the >>>>>>>>> config of the PLS itself needs changing through the SICK user >>>>>>>>> software?. >>>>>>>>> >>>>>>>>> I am using Ubuntu 6.06 LTS and Player 2.0.3 (I can't see a bug >>>>>>>>> report or >>>>>>>>> fix for this between 2.0.3 and 2.0.4) >>>>>>>>> >>>>>>>>> thanks >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> View this message in context: http://www.nabble.com/SICK-PLS- >>>>>>> config- >>>>>>> issue-tf4409923.html#a12659796 >>>>>>> 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 2005. >>>>>>> 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 2005. >>>>>> 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/SICK-PLS- >>>>> config- >>>>> issue-tf4409923.html#a12660783 >>>>> 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 2005. >>>>> 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 2005. >>>> 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 2005. >>> 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/SICK-PLS-config- >> issue-tf4409923.html#a12680353 >> 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 2005. >> 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 2005. > 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/SICK-PLS-config-issue-tf4409923.html#a12681377 Sent from the playerstage-users mailing list archive at Nabble.com. |