From: V. C. <ko...@gm...> - 2008-07-08 17:48:29
|
Hi everyone... Sorry for bothering everyone... but even after changing the transfer rate it didn't work... thanks in advance, Víctor Costa da Silva Campos >Message: 2 >Date: Fri, 4 Jul 2008 16:45:37 -0400 >From: "Kevin Barry" <ba...@gm...> >Subject: Re: [Playerstage-users] Problem sick lms 200 - ubuntu 8.04 >To: pla...@li... >Message-ID: > <c8d...@ma...> >Content-Type: text/plain; charset=ISO-8859-1 > >I think 9600 transfer rate might not work, try this: > > > driver ( > name "sicklms200" > provides ["laser:0"] > port "/dev/ttyUSB0" > connect_rate 9600 38400 > transfer_rate 38400 > delay 45 > retry 100 > alwayson 1 > ) > > |
From: Eric K. <eek...@ps...> - 2008-07-08 18:44:52
|
I am also experiencing continued lack of success. Yesterday I did an experiment where it looked like the LMS was responding, but Player kept reporting that it was not getting an acknowledge. This is just a judgment call on my part based on the length of time the led on my serial to usb converter flashes. If the LMS is not responding, the led will only flash for a short period due to the send from Player. Since I have failed to get this to work on the RS-232 port and the USB converter, I'm still at a loss. Is there anyone using a current distribution that has the LMS200 working. I am using 2.6.25.9-40.fc8. I also built a custom kernel version 2.6.25.9 that did not help. Eric On Tue, Jul 8, 2008 at 1:48 PM, Víctor Costa <ko...@gm...> wrote: > Hi everyone... > > Sorry for bothering everyone... but even after changing the transfer rate it > didn't work... > > thanks in advance, > > Víctor Costa da Silva Campos > >>Message: 2 >>Date: Fri, 4 Jul 2008 16:45:37 -0400 >>From: "Kevin Barry" <ba...@gm...> >>Subject: Re: [Playerstage-users] Problem sick lms 200 - ubuntu 8.04 >>To: pla...@li... >>Message-ID: >> <c8d...@ma...> >>Content-Type: text/plain; charset=ISO-8859-1 >> >>I think 9600 transfer rate might not work, try this: >> >> >> driver ( >> name "sicklms200" >> provides ["laser:0"] >> port "/dev/ttyUSB0" >> connect_rate 9600 38400 >> transfer_rate 38400 >> delay 45 >> retry 100 >> alwayson 1 >> ) >> >> > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Playerstage-developers mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-developers > > |
From: Geoffrey B. <gb...@ki...> - 2008-07-08 23:11:14
|
Have you tried the gbxsickacfr driver yet? Geoff Eric Keller wrote: > I am also experiencing continued lack of success. > Yesterday I did an experiment where it looked like > the LMS was responding, but Player kept reporting > that it was not getting an acknowledge. This is just > a judgment call on my part based on the length of time > the led on my serial to usb converter flashes. If the > LMS is not responding, the led will only flash for a short > period due to the send from Player. > > Since I have failed to get this to work on the RS-232 > port and the USB converter, I'm still at a loss. > > Is there anyone using a current distribution that has > the LMS200 working. I am using 2.6.25.9-40.fc8. > I also built a custom kernel version 2.6.25.9 > that did not help. > > Eric > > > On Tue, Jul 8, 2008 at 1:48 PM, Víctor Costa <ko...@gm...> wrote: >> Hi everyone... >> >> Sorry for bothering everyone... but even after changing the transfer rate it >> didn't work... >> >> thanks in advance, >> >> Víctor Costa da Silva Campos >> >>> Message: 2 >>> Date: Fri, 4 Jul 2008 16:45:37 -0400 >>> From: "Kevin Barry" <ba...@gm...> >>> Subject: Re: [Playerstage-users] Problem sick lms 200 - ubuntu 8.04 >>> To: pla...@li... >>> Message-ID: >>> <c8d...@ma...> >>> Content-Type: text/plain; charset=ISO-8859-1 >>> >>> I think 9600 transfer rate might not work, try this: >>> >>> >>> driver ( >>> name "sicklms200" >>> provides ["laser:0"] >>> port "/dev/ttyUSB0" >>> connect_rate 9600 38400 >>> transfer_rate 38400 >>> delay 45 >>> retry 100 >>> alwayson 1 >>> ) |
From: Eric K. <eek...@ps...> - 2008-07-09 15:42:15
|
Installing that brings me back to the day of failing dependency checks, google search, installing dependency, failing dependency checks, google search, installing dependency..... and then configure still fails with: configure:60656: result: - gbxsickacfr -- couldn't find required package GbxSickAcfr >= 0.0.1 I just installed Gearbox 1.0 and it says it installed GbxSickAfcr. Eric On Tue, Jul 8, 2008 at 7:11 PM, Geoffrey Biggs <gb...@ki...> wrote: > Have you tried the gbxsickacfr driver yet? > > Geoff > |
From: Fred L. <ff...@ab...> - 2008-07-09 15:59:39
|
On Wednesday 09 Jul 2008, Eric Keller wrote: > Installing that brings me back to the day of failing dependency > checks, google search, installing dependency, failing dependency > checks, google search, installing dependency..... > > and then configure still fails with: > configure:60656: result: - gbxsickacfr -- couldn't find required > package GbxSickAcfr >= 0.0.1 > > I just installed Gearbox 1.0 and it says it installed GbxSickAfcr. If I remember well, you have to explicitly put the gearbox pkg-config directory (/usr/local/lib/pkg-config/gearbox) in the PKG_CONFIG_PATH env variable because gearbox uses a subdir rather than the main dir. If you are using gentoo, as I do, I also had to install the manual way rather than using their gentoo ebuild because it didn't install most of the stuff... Hope this helps. Fred > > > Eric > > On Tue, Jul 8, 2008 at 7:11 PM, Geoffrey Biggs <gb...@ki...> wrote: > > Have you tried the gbxsickacfr driver yet? > > > > Geoff > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Playerstage-developers mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-developers |
From: Eric K. <eek...@ps...> - 2008-07-09 16:53:51
|
On Tue, Jul 8, 2008 at 7:11 PM, Geoffrey Biggs <gb...@ki...> wrote: > Have you tried the gbxsickacfr driver yet? > > Geoff After much suffering, I get this: debug: Connecting to laser on serial port /dev/ttyUSB0 debug: TrivialStatus::setMaxHeartbeatInterval(): Adding new subsystem: 'LaserSerialHandler' info: Driver: Trying to connect at 38400 baud. debug: SerialDeviceHandler: Changing baud rate and flushing. debug: Driver: Trying to get laser status with baudrate 38400 (try number 0 of 2) debug: Driver: requesting send REQUEST_LMS_STATUS(0x31) telegram: [ 02 00 01 00 31 15 12 ] debug: Driver: Guessed the baud rate! debug: Driver: Turning continuous mode off debug: Driver: requesting send SWITCH_OPERATING_MODE(0x20) telegram: [ 02 00 02 00 20 25 35 08 ] debug: Driver: requesting send REQUEST_ERROR_OR_TEST_MESSAGE(0x32) telegram: [ 02 00 01 00 32 16 12 ] debug: Driver: requesting send REQUEST_OPERATING_DATA_COUNTER(0x35) telegram: [ 02 00 03 00 35 00 00 64 32 ] warn: Driver::waitForResponseType(): While waiting for ACK_REQUEST_OPERATING_DATA_COUNTER, received unexpected response: type: RESP_INCORRECT_COMMAND(0x92) status: 0x10: STATUS_OK, IMPLAUSIBLE_MEASURED_VALUES data: [none] warn: TrivialStatus: LaserSerialHandler issued warning : 'SerialDeviceHandler: Received abnormal response: type: RESP_INCORRECT_COMMAND(0x92) status: 0x10: STATUS_OK, IMPLAUSIBLE_MEASURED_VALUES data: [none]' warn: during initLaser(): No response to command REQUEST_OPERATING_DATA_COUNTER(0x35) debug: LaserSerialHandler: dropping out from run() debug: TrivialStatus::removeSubsystem(): Removing existing subsystem: 'LaserSerialHandler' error : GbxSickAcfr: Failed to initialise laser device: No response to command REQUEST_OPERATING_DATA_COUNTER(0x35) error : initial subscription failed for device ranger:0 error : failed to start alwayson drivers |
From: gbiggs <gb...@ki...> - 2008-07-10 00:36:21
|
Unfortunately, I can't help you with problems with that library, as I didn't write it and don't have hardware to try it with. If you post to the gearbox mailing list, the developers who wrote it will be able to help you. No doubt they could explain what all that output means in no time, too. :) Geoff Eric Keller wrote: > On Tue, Jul 8, 2008 at 7:11 PM, Geoffrey Biggs <gb...@ki...> wrote: >> Have you tried the gbxsickacfr driver yet? >> >> Geoff > > After much suffering, I get this: > > debug: Connecting to laser on serial port /dev/ttyUSB0 > debug: TrivialStatus::setMaxHeartbeatInterval(): Adding new subsystem: > 'LaserSerialHandler' > info: Driver: Trying to connect at 38400 baud. > debug: SerialDeviceHandler: Changing baud rate and flushing. > debug: Driver: Trying to get laser status with baudrate 38400 (try > number 0 of 2) > > debug: Driver: requesting send REQUEST_LMS_STATUS(0x31) > telegram: [ 02 00 01 00 31 15 12 ] > debug: Driver: Guessed the baud rate! > debug: Driver: Turning continuous mode off > debug: Driver: requesting send SWITCH_OPERATING_MODE(0x20) > telegram: [ 02 00 02 00 20 25 35 08 ] > debug: Driver: requesting send REQUEST_ERROR_OR_TEST_MESSAGE(0x32) > telegram: [ 02 00 01 00 32 16 12 ] > debug: Driver: requesting send REQUEST_OPERATING_DATA_COUNTER(0x35) > telegram: [ 02 00 03 00 35 00 00 64 32 ] > warn: Driver::waitForResponseType(): While waiting for > ACK_REQUEST_OPERATING_DATA_COUNTER, received unexpected response: > type: RESP_INCORRECT_COMMAND(0x92) > status: 0x10: STATUS_OK, IMPLAUSIBLE_MEASURED_VALUES > data: [none] > warn: TrivialStatus: LaserSerialHandler issued warning : > 'SerialDeviceHandler: Received abnormal response: > type: RESP_INCORRECT_COMMAND(0x92) > status: 0x10: STATUS_OK, IMPLAUSIBLE_MEASURED_VALUES > data: [none]' > warn: during initLaser(): No response to command > REQUEST_OPERATING_DATA_COUNTER(0x35) > debug: LaserSerialHandler: dropping out from run() > debug: TrivialStatus::removeSubsystem(): Removing existing subsystem: > 'LaserSerialHandler' > error : GbxSickAcfr: Failed to initialise laser device: No response > to command REQUEST_OPERATING_DATA_COUNTER(0x35) > > error : initial subscription failed for device ranger:0 > error : failed to start alwayson drivers |
From: Fred L. <ff...@ab...> - 2008-07-09 08:09:28
|
On Tuesday 08 Jul 2008, Eric Keller wrote: > I am also experiencing continued lack of success. > Yesterday I did an experiment where it looked like > the LMS was responding, but Player kept reporting > that it was not getting an acknowledge. This is just > a judgment call on my part based on the length of time > the led on my serial to usb converter flashes. If the > LMS is not responding, the led will only flash for a short > period due to the send from Player. > > Since I have failed to get this to work on the RS-232 > port and the USB converter, I'm still at a loss. > > Is there anyone using a current distribution that has > the LMS200 working. I have. This is player 2.1.1, with a 2.6.24 kernel on "real" RS232 ports. Fred > I am using 2.6.25.9-40.fc8. > I also built a custom kernel version 2.6.25.9 > that did not help. > > Eric > > On Tue, Jul 8, 2008 at 1:48 PM, Víctor Costa <ko...@gm...> wrote: > > Hi everyone... > > > > Sorry for bothering everyone... but even after changing the transfer rate > > it didn't work... > > > > thanks in advance, > > > > Víctor Costa da Silva Campos > > > >>Message: 2 > >>Date: Fri, 4 Jul 2008 16:45:37 -0400 > >>From: "Kevin Barry" <ba...@gm...> > >>Subject: Re: [Playerstage-users] Problem sick lms 200 - ubuntu 8.04 > >>To: pla...@li... > >>Message-ID: > >> <c8d...@ma...> > >>Content-Type: text/plain; charset=ISO-8859-1 > >> > >>I think 9600 transfer rate might not work, try this: > >> > >> > >> driver ( > >> name "sicklms200" > >> provides ["laser:0"] > >> port "/dev/ttyUSB0" > >> connect_rate 9600 38400 > >> transfer_rate 38400 > >> delay 45 > >> retry 100 > >> alwayson 1 > >> ) > > > > ------------------------------------------------------------------------- > > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > > Studies have shown that voting for your favorite open source project, > > along with a healthy diet, reduces your potential for chronic lameness > > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > > _______________________________________________ > > Playerstage-developers mailing list > > Pla...@li... > > https://lists.sourceforge.net/lists/listinfo/playerstage-developers > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Playerstage-developers mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-developers |
From: Eric K. <eek...@ps...> - 2008-07-09 13:30:04
|
Fred, Thanks, that's very helpful. One of our guys got the LMS to work on another computer. Although he had to start player twice. Eric On Wed, Jul 9, 2008 at 4:09 AM, Fred Labrosse <ff...@ab...> wrote: > On Tuesday 08 Jul 2008, Eric Keller wrote: >> Is there anyone using a current distribution that has >> the LMS200 working. > > I have. This is player 2.1.1, with a 2.6.24 kernel on "real" RS232 ports. > > Fred > |
From: Fred L. <ff...@ab...> - 2008-07-09 08:10:38
|
On Wednesday 09 Jul 2008, Geoffrey Biggs wrote: > Have you tried the gbxsickacfr driver yet? The problem with that driver is that it implements ranger, rather than laser and does not provide the position data, only range data... Probably not much to do to "fix" that, but this is yet another thing to do... ;-). Fred > > Geoff > > Eric Keller wrote: > > I am also experiencing continued lack of success. > > Yesterday I did an experiment where it looked like > > the LMS was responding, but Player kept reporting > > that it was not getting an acknowledge. This is just > > a judgment call on my part based on the length of time > > the led on my serial to usb converter flashes. If the > > LMS is not responding, the led will only flash for a short > > period due to the send from Player. > > > > Since I have failed to get this to work on the RS-232 > > port and the USB converter, I'm still at a loss. > > > > Is there anyone using a current distribution that has > > the LMS200 working. I am using 2.6.25.9-40.fc8. > > I also built a custom kernel version 2.6.25.9 > > that did not help. > > > > Eric > > > > On Tue, Jul 8, 2008 at 1:48 PM, Víctor Costa <ko...@gm...> wrote: > >> Hi everyone... > >> > >> Sorry for bothering everyone... but even after changing the transfer > >> rate it didn't work... > >> > >> thanks in advance, > >> > >> Víctor Costa da Silva Campos > >> > >>> Message: 2 > >>> Date: Fri, 4 Jul 2008 16:45:37 -0400 > >>> From: "Kevin Barry" <ba...@gm...> > >>> Subject: Re: [Playerstage-users] Problem sick lms 200 - ubuntu 8.04 > >>> To: pla...@li... > >>> Message-ID: > >>> <c8d...@ma...> > >>> Content-Type: text/plain; charset=ISO-8859-1 > >>> > >>> I think 9600 transfer rate might not work, try this: > >>> > >>> > >>> driver ( > >>> name "sicklms200" > >>> provides ["laser:0"] > >>> port "/dev/ttyUSB0" > >>> connect_rate 9600 38400 > >>> transfer_rate 38400 > >>> delay 45 > >>> retry 100 > >>> alwayson 1 > >>> ) > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Playerstage-developers mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-developers |
From: Fred L. <ff...@ab...> - 2008-07-09 09:04:39
|
On Wednesday 09 Jul 2008, gbiggs wrote: > The ranger interface is the replacement for the laser, sonar and IR > interfaces I feel this is a good move. I always wondered why they were different. > (which will be deprecated in 2.2). Which means that either ranger will get these functions that laser was providing and all will be fine, or that users will have to go around the lack of these. Any idea which way it's gonna go? Fred > > Geoff > > Fred Labrosse wrote: > > On Wednesday 09 Jul 2008, Geoffrey Biggs wrote: > >> Have you tried the gbxsickacfr driver yet? > > > > The problem with that driver is that it implements ranger, rather than > > laser and does not provide the position data, only range data... > > Probably not much to do to "fix" that, but this is yet another thing to > > do... ;-). > > > > Fred > > > >> Geoff > >> > >> Eric Keller wrote: > >>> I am also experiencing continued lack of success. > >>> Yesterday I did an experiment where it looked like > >>> the LMS was responding, but Player kept reporting > >>> that it was not getting an acknowledge. This is just > >>> a judgment call on my part based on the length of time > >>> the led on my serial to usb converter flashes. If the > >>> LMS is not responding, the led will only flash for a short > >>> period due to the send from Player. > >>> > >>> Since I have failed to get this to work on the RS-232 > >>> port and the USB converter, I'm still at a loss. > >>> > >>> Is there anyone using a current distribution that has > >>> the LMS200 working. I am using 2.6.25.9-40.fc8. > >>> I also built a custom kernel version 2.6.25.9 > >>> that did not help. > >>> > >>> Eric > >>> > >>> On Tue, Jul 8, 2008 at 1:48 PM, Víctor Costa <ko...@gm...> wrote: > >>>> Hi everyone... > >>>> > >>>> Sorry for bothering everyone... but even after changing the transfer > >>>> rate it didn't work... > >>>> > >>>> thanks in advance, > >>>> > >>>> Víctor Costa da Silva Campos > >>>> > >>>>> Message: 2 > >>>>> Date: Fri, 4 Jul 2008 16:45:37 -0400 > >>>>> From: "Kevin Barry" <ba...@gm...> > >>>>> Subject: Re: [Playerstage-users] Problem sick lms 200 - ubuntu 8.04 > >>>>> To: pla...@li... > >>>>> Message-ID: > >>>>> <c8d...@ma...> > >>>>> Content-Type: text/plain; charset=ISO-8859-1 > >>>>> > >>>>> I think 9600 transfer rate might not work, try this: > >>>>> > >>>>> > >>>>> driver ( > >>>>> name "sicklms200" > >>>>> provides ["laser:0"] > >>>>> port "/dev/ttyUSB0" > >>>>> connect_rate 9600 38400 > >>>>> transfer_rate 38400 > >>>>> delay 45 > >>>>> retry 100 > >>>>> alwayson 1 > >>>>> ) > >> > >> ------------------------------------------------------------------------ > >>- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > >> Studies have shown that voting for your favorite open source project, > >> along with a healthy diet, reduces your potential for chronic lameness > >> and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > >> _______________________________________________ > >> Playerstage-developers mailing list > >> Pla...@li... > >> https://lists.sourceforge.net/lists/listinfo/playerstage-developers > > > > ------------------------------------------------------------------------- > > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > > Studies have shown that voting for your favorite open source project, > > along with a healthy diet, reduces your potential for chronic lameness > > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > > _______________________________________________ > > Playerstage-developers mailing list > > Pla...@li... > > https://lists.sourceforge.net/lists/listinfo/playerstage-developers > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Playerstage-developers mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-developers |
From: gbiggs <gb...@ki...> - 2008-07-09 08:14:15
|
The ranger interface is the replacement for the laser, sonar and IR interfaces (which will be deprecated in 2.2). Geoff Fred Labrosse wrote: > On Wednesday 09 Jul 2008, Geoffrey Biggs wrote: >> Have you tried the gbxsickacfr driver yet? > > The problem with that driver is that it implements ranger, rather than laser > and does not provide the position data, only range data... Probably not much > to do to "fix" that, but this is yet another thing to do... ;-). > > Fred > > >> Geoff >> >> Eric Keller wrote: >>> I am also experiencing continued lack of success. >>> Yesterday I did an experiment where it looked like >>> the LMS was responding, but Player kept reporting >>> that it was not getting an acknowledge. This is just >>> a judgment call on my part based on the length of time >>> the led on my serial to usb converter flashes. If the >>> LMS is not responding, the led will only flash for a short >>> period due to the send from Player. >>> >>> Since I have failed to get this to work on the RS-232 >>> port and the USB converter, I'm still at a loss. >>> >>> Is there anyone using a current distribution that has >>> the LMS200 working. I am using 2.6.25.9-40.fc8. >>> I also built a custom kernel version 2.6.25.9 >>> that did not help. >>> >>> Eric >>> >>> On Tue, Jul 8, 2008 at 1:48 PM, Víctor Costa <ko...@gm...> wrote: >>>> Hi everyone... >>>> >>>> Sorry for bothering everyone... but even after changing the transfer >>>> rate it didn't work... >>>> >>>> thanks in advance, >>>> >>>> Víctor Costa da Silva Campos >>>> >>>>> Message: 2 >>>>> Date: Fri, 4 Jul 2008 16:45:37 -0400 >>>>> From: "Kevin Barry" <ba...@gm...> >>>>> Subject: Re: [Playerstage-users] Problem sick lms 200 - ubuntu 8.04 >>>>> To: pla...@li... >>>>> Message-ID: >>>>> <c8d...@ma...> >>>>> Content-Type: text/plain; charset=ISO-8859-1 >>>>> >>>>> I think 9600 transfer rate might not work, try this: >>>>> >>>>> >>>>> driver ( >>>>> name "sicklms200" >>>>> provides ["laser:0"] >>>>> port "/dev/ttyUSB0" >>>>> connect_rate 9600 38400 >>>>> transfer_rate 38400 >>>>> delay 45 >>>>> retry 100 >>>>> alwayson 1 >>>>> ) >> ------------------------------------------------------------------------- >> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! >> Studies have shown that voting for your favorite open source project, >> along with a healthy diet, reduces your potential for chronic lameness >> and boredom. Vote Now at http://www.sourceforge.net/community/cca08 >> _______________________________________________ >> Playerstage-developers mailing list >> Pla...@li... >> https://lists.sourceforge.net/lists/listinfo/playerstage-developers > > > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Playerstage-developers mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-developers > |
From: gbiggs <gb...@ki...> - 2008-07-09 09:13:24
|
Well, the plan that I put in the roadmap a long time ago is as follows: "Deprecate the laser, sonar and ir interfaces in favour of the ranger interface. Change all drivers to use the ranger interface, and provide rangertolaser, rangertosonar and rangertoir drivers for backwards compatibility of clients." I never had any comments on this, but I suspect this is because noone reads the roadmap. :) I had a look at the position thing. The position of each scan is calculated by the client library, not the individual drivers. The ranger interface doesn't currently do this, but I'll be fixing that soon. Apart from that, I don't think there is anything that isn't provided by the ranger interface but is by the laser, sonar or IR interfaces (that can't be provided as properties by individual drivers). The ranger interface is actually significantly more flexible, allowing for multi-sensor sensors (like the two independent arrays of sonar sensors on a B21r), full 3D pose information, individual sensor element pose information, and stuff like that. It was designed to address the shortcomings that Toby and I had found in the older interfaces over the years. Geoff Fred Labrosse wrote: > On Wednesday 09 Jul 2008, gbiggs wrote: >> The ranger interface is the replacement for the laser, sonar and IR >> interfaces > > I feel this is a good move. I always wondered why they were different. > >> (which will be deprecated in 2.2). > > Which means that either ranger will get these functions that laser was > providing and all will be fine, or that users will have to go around the lack > of these. > > Any idea which way it's gonna go? > > Fred > > >> Geoff >> >> Fred Labrosse wrote: >>> On Wednesday 09 Jul 2008, Geoffrey Biggs wrote: >>>> Have you tried the gbxsickacfr driver yet? >>> The problem with that driver is that it implements ranger, rather than >>> laser and does not provide the position data, only range data... >>> Probably not much to do to "fix" that, but this is yet another thing to >>> do... ;-). >>> >>> Fred >>> >>>> Geoff >>>> >>>> Eric Keller wrote: >>>>> I am also experiencing continued lack of success. >>>>> Yesterday I did an experiment where it looked like >>>>> the LMS was responding, but Player kept reporting >>>>> that it was not getting an acknowledge. This is just >>>>> a judgment call on my part based on the length of time >>>>> the led on my serial to usb converter flashes. If the >>>>> LMS is not responding, the led will only flash for a short >>>>> period due to the send from Player. >>>>> >>>>> Since I have failed to get this to work on the RS-232 >>>>> port and the USB converter, I'm still at a loss. >>>>> >>>>> Is there anyone using a current distribution that has >>>>> the LMS200 working. I am using 2.6.25.9-40.fc8. >>>>> I also built a custom kernel version 2.6.25.9 >>>>> that did not help. >>>>> >>>>> Eric >>>>> >>>>> On Tue, Jul 8, 2008 at 1:48 PM, Víctor Costa <ko...@gm...> wrote: >>>>>> Hi everyone... >>>>>> >>>>>> Sorry for bothering everyone... but even after changing the transfer >>>>>> rate it didn't work... >>>>>> >>>>>> thanks in advance, >>>>>> >>>>>> Víctor Costa da Silva Campos >>>>>> >>>>>>> Message: 2 >>>>>>> Date: Fri, 4 Jul 2008 16:45:37 -0400 >>>>>>> From: "Kevin Barry" <ba...@gm...> >>>>>>> Subject: Re: [Playerstage-users] Problem sick lms 200 - ubuntu 8.04 >>>>>>> To: pla...@li... >>>>>>> Message-ID: >>>>>>> <c8d...@ma...> >>>>>>> Content-Type: text/plain; charset=ISO-8859-1 >>>>>>> >>>>>>> I think 9600 transfer rate might not work, try this: >>>>>>> >>>>>>> >>>>>>> driver ( >>>>>>> name "sicklms200" >>>>>>> provides ["laser:0"] >>>>>>> port "/dev/ttyUSB0" >>>>>>> connect_rate 9600 38400 >>>>>>> transfer_rate 38400 >>>>>>> delay 45 >>>>>>> retry 100 >>>>>>> alwayson 1 >>>>>>> ) >>>> ------------------------------------------------------------------------ >>>> - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! >>>> Studies have shown that voting for your favorite open source project, >>>> along with a healthy diet, reduces your potential for chronic lameness >>>> and boredom. Vote Now at http://www.sourceforge.net/community/cca08 >>>> _______________________________________________ >>>> Playerstage-developers mailing list >>>> Pla...@li... >>>> https://lists.sourceforge.net/lists/listinfo/playerstage-developers >>> ------------------------------------------------------------------------- >>> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! >>> Studies have shown that voting for your favorite open source project, >>> along with a healthy diet, reduces your potential for chronic lameness >>> and boredom. Vote Now at http://www.sourceforge.net/community/cca08 >>> _______________________________________________ >>> Playerstage-developers mailing list >>> Pla...@li... >>> https://lists.sourceforge.net/lists/listinfo/playerstage-developers >> ------------------------------------------------------------------------- >> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! >> Studies have shown that voting for your favorite open source project, >> along with a healthy diet, reduces your potential for chronic lameness >> and boredom. Vote Now at http://www.sourceforge.net/community/cca08 >> _______________________________________________ >> Playerstage-developers mailing list >> Pla...@li... >> https://lists.sourceforge.net/lists/listinfo/playerstage-developers > > > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Playerstage-developers mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-developers > |
From: Fred L. <ff...@ab...> - 2008-07-09 09:20:29
|
On Wednesday 09 Jul 2008, gbiggs wrote: > Well, the plan that I put in the roadmap a long time ago is as follows: > > "Deprecate the laser, sonar and ir interfaces in favour of the ranger > interface. Change all drivers to use the ranger interface, and provide > rangertolaser, rangertosonar and rangertoir drivers for backwards > compatibility of clients." > > I never had any comments on this, but I suspect this is because noone > reads the roadmap. :) > > I had a look at the position thing. The position of each scan is > calculated by the client library, not the individual drivers. You mean libplayerc (and the c++ wrapper)? > The ranger > interface doesn't currently do this, but I'll be fixing that soon. Apart > from that, I don't think there is anything that isn't provided by the > ranger interface but is by the laser, sonar or IR interfaces (that can't > be provided as properties by individual drivers). The ranger interface > is actually significantly more flexible, allowing for multi-sensor > sensors (like the two independent arrays of sonar sensors on a B21r), > full 3D pose information, individual sensor element pose information, > and stuff like that. It was designed to address the shortcomings that > Toby and I had found in the older interfaces over the years. I like all that. Fred |
From: gbiggs <gb...@ki...> - 2008-07-10 00:34:39
|
Fred Labrosse wrote: > If I remember well, you have to explicitly put the gearbox pkg-config > directory (/usr/local/lib/pkg-config/gearbox) in the PKG_CONFIG_PATH env > variable because gearbox uses a subdir rather than the main dir. Yeah, that was us getting a little over-enthusiastic with sub-directories... It's been fixed in SVN for a while, so it'll be fixed in the next release (due pretty soon). > If you are using gentoo, as I do, I also had to install the manual way rather > than using their gentoo ebuild because it didn't install most of the stuff... And that's me being lazy and forgetting to update the ebuild. :) By the way, you are allowed to post to the gearbox mailing list when you encounter problems... We're not going to be able to fix them if no one tells us about them, just like how Player wouldn't be able to fix issues its users have if no one posted about them to this list. Geoff |
From: Fred L. <ff...@ab...> - 2008-07-10 07:27:15
|
On Thu, 10 July, 2008 1:34 am, gbiggs wrote: > Fred Labrosse wrote: >> If I remember well, you have to explicitly put the gearbox pkg-config >> directory (/usr/local/lib/pkg-config/gearbox) in the PKG_CONFIG_PATH env >> variable because gearbox uses a subdir rather than the main dir. > > Yeah, that was us getting a little over-enthusiastic with > sub-directories... It's been fixed in SVN for a while, so it'll be fixed > in the next release (due pretty soon). So you are behind that one as well! > >> If you are using gentoo, as I do, I also had to install the manual way >> rather >> than using their gentoo ebuild because it didn't install most of the >> stuff... > > And that's me being lazy and forgetting to update the ebuild. :) > > By the way, you are allowed to post to the gearbox mailing list when you > encounter problems... We're not going to be able to fix them if no one > tells us about them, just like how Player wouldn't be able to fix issues > its users have if no one posted about them to this list. I know. It's just that when I was fighting this I was in a bit of a rush and then forgot. Talking about the ebuild, it was rather difficult to find as not linked anywhere. Fred |
From: V. C. <ko...@gm...> - 2008-07-10 20:20:53
|
Hi there everyone... After a long evening of trials, I've been able to install gearbox and the gbxsickacfr driver for player 2.1.1... Unfortunately, it doesn't accepts the delay option and I couldn't make the lms200 work with it... Has anyone had any success into using the lms200 on any player version? I've tried doing everything you guys said... And the kernel we're using here is 2.6.24-19-generic.... If anyone has had any success and could mail me or the list saying what is it that they've done in order for the lms200 to work with a RS232 I'd be very grateful... Thanks in advance, Víctor Costa da Silva Campos On Thu, Jul 10, 2008 at 4:27 AM, Fred Labrosse <ff...@ab...> wrote: > On Thu, 10 July, 2008 1:34 am, gbiggs wrote: > > Fred Labrosse wrote: > >> If I remember well, you have to explicitly put the gearbox pkg-config > >> directory (/usr/local/lib/pkg-config/gearbox) in the PKG_CONFIG_PATH env > >> variable because gearbox uses a subdir rather than the main dir. > > > > Yeah, that was us getting a little over-enthusiastic with > > sub-directories... It's been fixed in SVN for a while, so it'll be fixed > > in the next release (due pretty soon). > > So you are behind that one as well! > > > > >> If you are using gentoo, as I do, I also had to install the manual way > >> rather > >> than using their gentoo ebuild because it didn't install most of the > >> stuff... > > > > And that's me being lazy and forgetting to update the ebuild. :) > > > > By the way, you are allowed to post to the gearbox mailing list when you > > encounter problems... We're not going to be able to fix them if no one > > tells us about them, just like how Player wouldn't be able to fix issues > > its users have if no one posted about them to this list. > > I know. It's just that when I was fighting this I was in a bit of a rush > and then forgot. > > Talking about the ebuild, it was rather difficult to find as not linked > anywhere. > > Fred > > > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Playerstage-developers mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-developers > |
From: Fred L. <ff...@ab...> - 2008-07-11 08:05:08
|
On Thursday 10 Jul 2008, Víctor Costa wrote: > Hi there everyone... After a long evening of trials, I've been able to > install gearbox and the gbxsickacfr driver for player 2.1.1... > Unfortunately, it doesn't accepts the delay option and I couldn't make the > lms200 work with it... Has anyone had any success into using the lms200 on > any player version? I've tried doing everything you guys said... And the > kernel we're using here is 2.6.24-19-generic.... If anyone has had any > success and could mail me or the list saying what is it that they've done > in order for the lms200 to work with a RS232 I'd be very grateful... Here's what I've done: switched from player 2.0.5 to player 2.1.1 and it worked. What exactly does not work? What does it do (or not)? Fred |
From: V. C. <ko...@gm...> - 2008-07-11 16:56:42
|
I've tried switching from player 2.0.5 to 2.1.1 and it still doesn't work... The player server is unable to connect to the server and it times out... I've tried using the lms200 driver and also the gbxsickacfr driver and both of them times out and are unable to connect to the lms 200... Therefore I'm unable to use the laser... It is only working in one of the notebooks from our lab running Ubuntu 7.04. It used to work with the others notebooks and with the desktop computers from the lab, but since we've updated them from Ubuntu 7.04 it stopped working... We were hoping we could update it to Ubuntu 8.04 too... But, because of this problem, we have been unable to use player in any Ubuntu newer than 7.04 (it isn't working in 7.10 either).... Sorry for bothering everyone, Víctor Costa da Silva Campos On Fri, Jul 11, 2008 at 5:05 AM, Fred Labrosse <ff...@ab...> wrote: > On Thursday 10 Jul 2008, Víctor Costa wrote: > > Hi there everyone... After a long evening of trials, I've been able to > > install gearbox and the gbxsickacfr driver for player 2.1.1... > > Unfortunately, it doesn't accepts the delay option and I couldn't make > the > > lms200 work with it... Has anyone had any success into using the lms200 > on > > any player version? I've tried doing everything you guys said... And the > > kernel we're using here is 2.6.24-19-generic.... If anyone has had any > > success and could mail me or the list saying what is it that they've done > > in order for the lms200 to work with a RS232 I'd be very grateful... > > Here's what I've done: switched from player 2.0.5 to player 2.1.1 and it > worked. > > What exactly does not work? What does it do (or not)? > > Fred > > ------------------------------------------------------------------------- > Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! > Studies have shown that voting for your favorite open source project, > along with a healthy diet, reduces your potential for chronic lameness > and boredom. Vote Now at http://www.sourceforge.net/community/cca08 > _______________________________________________ > Playerstage-developers mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-developers > |
From: Patrick B. <pb...@cs...> - 2008-10-01 20:25:06
|
Víctor Costa wrote: > I've tried switching from player 2.0.5 to 2.1.1 and it still doesn't > work... The player server is unable to connect to the server and it > times out... But, because of this problem, we have been unable to > use player in any Ubuntu newer than 7.04 (it isn't working in 7.10 > either).... > I've just submitted a huge patch to the Player sicklmls200 driver that should fix these problems -- these issues are due to the driver, not the Linux kernel you are running (its just that newer kernels run faster which makes the bug more apparent). Additionally, the patched driver should save the life of these devices by not flashing the configuration every time player runs -- only when the configuration is different than what's stored on the device. https://sourceforge.net/tracker/?func=detail&atid=433166&aid=2136885&group_id=42445 I have tested this in Player > 2.1. I'm not sure if the patch applies to Player 2.0.x. Good luck, Patrick Beeson |
From: Patrick B. <pb...@cs...> - 2008-09-23 22:47:26
|
Víctor Costa wrote: > I've tried switching from player 2.0.5 to 2.1.1 and it still doesn't > work... The player server is unable to connect to the server and it > times out... I've tried using the lms200 driver and also the > gbxsickacfr driver and both of them times out and are unable to > connect to the lms 200... Therefore I'm unable to use the laser... It > is only working in one of the notebooks from our lab running Ubuntu > 7.04. It used to work with the others notebooks and with the desktop > computers from the lab, but since we've updated them from Ubuntu 7.04 > it stopped working... We were hoping we could update it to Ubuntu > 8.04 too... But, because of this problem, we have been unable to use > player in any Ubuntu newer than 7.04 (it isn't working in 7.10 > either).... Víctor, Here's my take: The new Ubuntu distro use linux kernels that have dynamic ticks enabled, which means that the clocks can run at high clock speeds when necessary but when no apps are running will run the clock slower to save power (for things like laptops). I've found that what this means is that code that has poorly written timeouts no longer work ---- a usleep(1) used to mean sleep for 4 ms (with 250Hz kernels), but now means sleep 1 ms if you have a dynamic ticks kernel -- which Ubuntu 8.04 does. usleep 1 also sleeps for 1ms if you run Ubuntu with the real-time kernel. In general, for drivers that needs to run across platforms (i.e. on systems that have different clock speeds), its better to grab the system clock time and check it until the appropriate itme goes by instead of using something like usleep, which runs differently on different kernels. I've dealt with this for homebrewed Player drivers recently by increasing thresholds that were tuned on an older kernel where 250Hz clock meant usleep(1) meant a 4ms wait. Theorectically increasing timeouts by 4 works, but you can get away with smaller increases. One driver I investigated was a locally changed version of the Player 2.0.x sicklms200 driver. I got the Player 2.0.x sicklms driver working by increasing the timeouts that are < 3000 (sent to ReadFromLaser() in the sicklms200.cc source) to 3000 (or three seconds). I haven't tried the Player 2.1.1 sicklms200 driver extensively, but I plan to do that Friday, I want to submit a patch to allow a config file option to set the laser into high availability mode so that it won't reset when it gets dazzled (a small patch). If I run into timeout issues there, I can easily compare it to our local version of the 2.0.x source that I already increased the timeouts on, and I'll get back to you later. Patrick Beeson |
From: Patrick B. <pb...@cs...> - 2008-09-23 22:56:46
|
Víctor, Of course another reasonable option to try would be to change the Player 2.1.1 source to do usleep(4000) wait 4ms, which should be equivalent to the usleep(1000) that ran on older 250Hz kernels without the dynamic ticks option. I might try this on Friday. If that works, I might try to make a sicklms patch that does loop and call usleep(1000) N times, instead loops calling usleep until the correct number of seconds have passed, this means it'll loop more times through for faster kernels and fewer times for slower kernels. Patrick Beeson wrote: > Víctor Costa wrote: >> I've tried switching from player 2.0.5 to 2.1.1 and it still doesn't >> work... The player server is unable to connect to the server and it >> times out... I've tried using the lms200 driver and also the >> gbxsickacfr driver and both of them times out and are unable to >> connect to the lms 200... Therefore I'm unable to use the laser... It >> is only working in one of the notebooks from our lab running Ubuntu >> 7.04. It used to work with the others notebooks and with the desktop >> computers from the lab, but since we've updated them from Ubuntu 7.04 >> it stopped working... We were hoping we could update it to Ubuntu >> 8.04 too... But, because of this problem, we have been unable to use >> player in any Ubuntu newer than 7.04 (it isn't working in 7.10 >> either).... > > Víctor, > > Here's my take: > > The new Ubuntu distro use linux kernels that have dynamic ticks enabled, > which means that the clocks can run at high clock speeds when necessary > but when no apps are running will run the clock slower to save power > (for things like laptops). > > I've found that what this means is that code that has poorly written > timeouts no longer work ---- a usleep(1) used to mean sleep for 4 ms > (with 250Hz kernels), but now means sleep 1 ms if you have a dynamic > ticks kernel -- which Ubuntu 8.04 does. usleep 1 also sleeps for 1ms if > you run Ubuntu with the real-time kernel. > > In general, for drivers that needs to run across platforms (i.e. on > systems that have different clock speeds), its better to grab the system > clock time and check it until the appropriate itme goes by instead of > using something like usleep, which runs differently on different kernels. > > I've dealt with this for homebrewed Player drivers recently by > increasing thresholds that were tuned on an older kernel where 250Hz > clock meant usleep(1) meant a 4ms wait. Theorectically increasing > timeouts by 4 works, but you can get away with smaller increases. > > One driver I investigated was a locally changed version of the Player > 2.0.x sicklms200 driver. I got the Player 2.0.x sicklms driver working > by increasing the timeouts that are < 3000 (sent to ReadFromLaser() in > the sicklms200.cc source) to 3000 (or three seconds). > > I haven't tried the Player 2.1.1 sicklms200 driver extensively, but I > plan to do that Friday, I want to submit a patch to allow a config file > option to set the laser into high availability mode so that it won't > reset when it gets dazzled (a small patch). If I run into timeout > issues there, I can easily compare it to our local version of the 2.0.x > source that I already increased the timeouts on, and I'll get back to > you later. > > > Patrick Beeson > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Playerstage-developers mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/playerstage-developers > |
From: Fred L. <ff...@ab...> - 2008-09-24 09:47:37
|
On Tuesday 23 Sep 2008, Patrick Beeson wrote: > Víctor, > > Of course another reasonable option to try would be to change the Player > 2.1.1 source to do usleep(4000) wait 4ms, which should be equivalent to > the usleep(1000) that ran on older 250Hz kernels without the dynamic > ticks option. > > I might try this on Friday. If that works, I might try to make a > sicklms patch that does loop and call usleep(1000) N times, instead > loops calling usleep until the correct number of seconds have passed, > this means it'll loop more times through for faster kernels and fewer > times for slower kernels. Surely there must be better to do than loop waiting for the right amount of time to have elapsed. This makes the thread do some processing for nothing, therefore not freeing any processing time for anything else. I'm not sure why the lms200 driver is sleeping (I didn't look at the code much), but could this be replaced by careful use of select? I seem to remember somebody submitting a patch to that effect. Or maybe I didn't understand what you meant, in which case sorry. Fred |
From: Paul O. <new...@ki...> - 2008-09-24 09:57:19
|
On Wed, 24 Sep 2008, Fred Labrosse wrote: > > Surely there must be better to do than loop waiting for the right amount of > time to have elapsed. This makes the thread do some processing for nothing, > therefore not freeing any processing time for anything else. You can always put some little sleep call inside that loop so it won't be busy looping all the time. |
From: Fred L. <ff...@ab...> - 2008-09-24 10:05:21
|
On Wednesday 24 Sep 2008, Paul Osmialowski wrote: > On Wed, 24 Sep 2008, Fred Labrosse wrote: > > Surely there must be better to do than loop waiting for the right amount > > of time to have elapsed. This makes the thread do some processing for > > nothing, therefore not freeing any processing time for anything else. > > You can always put some little sleep call inside that loop so it won't be > busy looping all the time. You are right, but still, a loop is set up (which takes time) and wakes up the thread for nothing. Fred |