[chbot] Chchrobotics Digest, Vol 40, Issue 4
Kay edgecumbe
kayedgecumbe at hotmail.com
Thu Jan 6 16:51:21 GMT 2011
new batteries in the chair and some electrical repairs and the wife now has a going
to a show chair fits her perfectly
many thanks
> From: chchrobotics-request at lists.linuxnut.co.nz
> Subject: Chchrobotics Digest, Vol 40, Issue 4
> To: chchrobotics at lists.linuxnut.co.nz
> Date: Thu, 6 Jan 2011 12:00:03 +0000
>
> Send Chchrobotics mailing list submissions to
> chchrobotics at lists.linuxnut.co.nz
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.ourshack.com/mailman/listinfo/chchrobotics
> or, via email, send a message with subject or body 'help' to
> chchrobotics-request at lists.linuxnut.co.nz
>
> You can reach the person managing the list at
> chchrobotics-owner at lists.linuxnut.co.nz
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Chchrobotics digest..."
>
>
> Today's Topics:
>
> 1. Re: OT: Compiler help (Charles Manning)
> 2. Re: Electric wheelchair (Charles Manning)
> 3. Re: Electric wheelchair (Mark Atherton)
> 4. Re: OT: Compiler help (Andrew Errington)
> 5. Re: OT: Compiler help (Charles Manning)
> 6. Re: OT: Compiler help (Andrew Errington)
> 7. Re: OT: Compiler help (Charles Manning)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 6 Jan 2011 11:54:40 +1300
> From: Charles Manning <manningc2 at actrix.gen.nz>
> Subject: Re: [chbot] OT: Compiler help
> To: Christchurch Robotics <chchrobotics at lists.linuxnut.co.nz>
> Message-ID: <201101061154.40370.manningc2 at actrix.gen.nz>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Wednesday 05 January 2011 18:28:10 follower wrote:
> > On 5 January 2011 17:56, Andrew Errington <a.errington at lancaster.ac.uk>
> wrote:
> > > Unfortunately, the test code was compiled with a different product ID to
> > > the chip I have (same product, different configuration), so the test
> > > program won't run because it cannot find the device. (Grr!)
> >
> > In the short term, you could try using a hex editor to find the PID
> > and change it?
> >
>
> That *might* work. It depends on how the code was written.
>
> Of course the superior solution is to just use libusb and make a Linux version
> of the program.
>
> libusb should make this problem trial.
>
> -- Charles
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 6 Jan 2011 11:57:46 +1300
> From: Charles Manning <manningc2 at actrix.gen.nz>
> Subject: Re: [chbot] Electric wheelchair
> To: Christchurch Robotics <chchrobotics at lists.linuxnut.co.nz>
> Message-ID: <201101061157.46992.manningc2 at actrix.gen.nz>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Monday 03 January 2011 06:41:57 Mark Atherton wrote:
> > Just spotted at the local junk store
> >
> > Tucked under the stairs at Charity Barn / 522 Blenheim Rd /
> > -43.539042,172.559429
> >
> > No idea how much they want, but no harm asking or haggling, they are
> > good folks.
> >
> > In case you haven't been there, this place is junque by the cubic
> > metre - loads of old printers, monitors etc.
> >
> > Just like Super Shed, but without the class :)
> >
> > -Mark
>
> While I applaud scrounging, it seems poor form to strip an electric wheelchair
> that could be put to more productive use. Unless of course the wheelchair is
> no longer servicable.
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 06 Jan 2011 12:10:36 +1300
> From: Mark Atherton <markaren1 at xtra.co.nz>
> Subject: Re: [chbot] Electric wheelchair
> To: chchrobotics at lists.linuxnut.co.nz
> Message-ID:
> <20110105232414.USLZ16005.mta02.xtra.co.nz at mainmachine.xtra.co.nz>
> Content-Type: text/plain; charset="us-ascii"; format=flowed
>
> Don't worry, Kay has bought it. Sounds like he is going to race it
> which is far more useful than being stripped down :)
>
> At 11:57 a.m. 6/01/2011, Charles Manning wrote:
> >On Monday 03 January 2011 06:41:57 Mark Atherton wrote:
> > > Just spotted at the local junk store
> > >
> > > Tucked under the stairs at Charity Barn / 522 Blenheim Rd /
> > > -43.539042,172.559429
> > >
> > > No idea how much they want, but no harm asking or haggling, they are
> > > good folks.
> > >
> > > In case you haven't been there, this place is junque by the cubic
> > > metre - loads of old printers, monitors etc.
> > >
> > > Just like Super Shed, but without the class :)
> > >
> > > -Mark
> >
> >While I applaud scrounging, it seems poor form to strip an electric
> >wheelchair
> >that could be put to more productive use. Unless of course the wheelchair is
> >no longer servicable.
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 6 Jan 2011 09:01:13 +0900
> From: Andrew Errington <a.errington at lancaster.ac.uk>
> Subject: Re: [chbot] OT: Compiler help
> To: Christchurch Robotics <chchrobotics at lists.linuxnut.co.nz>
> Message-ID: <201101060901.13653.a.errington at lancaster.ac.uk>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Thu, 06 Jan 2011 07:54:40 Charles Manning wrote:
>
> > That *might* work. It depends on how the code was written.
> >
> > Of course the superior solution is to just use libusb and make a Linux
> > version of the program.
> >
> > libusb should make this problem trial.
>
> Yes and no. (I presume you mean 'trivial').
>
> I intend to use PyUSB, which is an easy wrapper for libusb, but the problem I
> have is knowing how to construct the data packet for the device.
>
> I can currently use PyUSB to read from the device and I can see the state of
> the GPIO lines (they are input by default).
>
> To control the GPIO I need to send two bytes, a data-direction byte (one bit
> per GPIO to set input or output) and the output data byte. I don't know the
> format of this data packet. Is it two bytes, or are there some overhead
> bytes? Which byte is the DDR, and which is the output? I have /some/
> information from the manufacturer, but not /this/ information. :(
>
> No regular software exists to control the GPIO, since no-one really uses the
> GPIO, so I can't just spy on some packets and parse them manually. I have to
> run the test program, which will generate packets that control the GPIO,
> which I can then spy on. I can't run the test program because it was
> compiled with the wrong product ID. I can't compile the test program because
> I have no compiler. I can't write my PyUSB program because I don't have the
> format of the data packet.
>
> And yes, I have asked the manufacturer for the specific information I need,
> but it is not forthcoming. I consider myself lucky to have what I have, and
> actually it's enough if I can get it to work.
>
> Best wishes,
>
> Andrew
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 6 Jan 2011 14:53:39 +1300
> From: Charles Manning <manningc2 at actrix.gen.nz>
> Subject: Re: [chbot] OT: Compiler help
> To: Christchurch Robotics <chchrobotics at lists.linuxnut.co.nz>
> Message-ID: <201101061453.39260.manningc2 at actrix.gen.nz>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Thursday 06 January 2011 13:01:13 Andrew Errington wrote:
> > On Thu, 06 Jan 2011 07:54:40 Charles Manning wrote:
> > > That *might* work. It depends on how the code was written.
> > >
> > > Of course the superior solution is to just use libusb and make a Linux
> > > version of the program.
> > >
> > > libusb should make this problem trial.
> >
> > Yes and no. (I presume you mean 'trivial').
>
> Yup, I did mean trivial, but it does seem a trial too :-).
>
> >
> > I intend to use PyUSB, which is an easy wrapper for libusb, but the problem
> > I have is knowing how to construct the data packet for the device.
> >
> > I can currently use PyUSB to read from the device and I can see the state
> > of the GPIO lines (they are input by default).
> >
> > To control the GPIO I need to send two bytes, a data-direction byte (one
> > bit per GPIO to set input or output) and the output data byte. I don't
> > know the format of this data packet. Is it two bytes, or are there some
> > overhead bytes? Which byte is the DDR, and which is the output? I have
> > /some/ information from the manufacturer, but not /this/ information. :(
> >
> > No regular software exists to control the GPIO, since no-one really uses
> > the GPIO, so I can't just spy on some packets and parse them manually. I
> > have to run the test program, which will generate packets that control the
> > GPIO, which I can then spy on. I can't run the test program because it was
> > compiled with the wrong product ID. I can't compile the test program
> > because I have no compiler. I can't write my PyUSB program because I don't
> > have the format of the data packet.
> >
> > And yes, I have asked the manufacturer for the specific information I need,
> > but it is not forthcoming. I consider myself lucky to have what I have,
> > and actually it's enough if I can get it to work.
>
> I re-read your doc and see the functions were in the library. Sorry, I thought
> those were in the source code.
>
> You use one of those usb snoopers to figure out what is going on.
>
> eg.
> http://benoit.papillault.free.fr/usbsnoop/
> http://sourceforge.net/projects/usbsnoop/
>
> -- Charles
>
>
>
>
>
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 6 Jan 2011 11:46:39 +0900 (KST)
> From: "Andrew Errington" <a.errington at lancaster.ac.uk>
> Subject: Re: [chbot] OT: Compiler help
> To: "Christchurch Robotics" <chchrobotics at lists.linuxnut.co.nz>
> Message-ID:
> <2080.114.52.23.74.1294281999.squirrel at webmail01.lancs.ac.uk>
> Content-Type: text/plain;charset=iso-8859-15
>
> On Thu, January 6, 2011 10:53, Charles Manning wrote:
> > On Thursday 06 January 2011 13:01:13 Andrew Errington wrote:
> >> Yes and no. (I presume you mean 'trivial').
> >>
> >
> > Yup, I did mean trivial, but it does seem a trial too :-).
> >
>
> Yes, the unintentional irony made me smile. :)
>
> <snip>
> >
> > I re-read your doc and see the functions were in the library. Sorry, I
> > thought those were in the source code.
>
> Yes, that is what is most frustrating. They gave me the source to use the
> library, but I need the source of the library itself.
>
> > You use one of those usb snoopers to figure out what is going on.
> >
> > eg. http://benoit.papillault.free.fr/usbsnoop/
> > http://sourceforge.net/projects/usbsnoop/
>
> Yes, that is the step after I get the test software compiled, so that I
> can make some packets worth snooping.
>
> Best wishes,
>
> Andrew
>
>
>
>
> ------------------------------
>
> Message: 7
> Date: Thu, 6 Jan 2011 15:58:01 +1300
> From: Charles Manning <manningc2 at actrix.gen.nz>
> Subject: Re: [chbot] OT: Compiler help
> To: Christchurch Robotics <chchrobotics at lists.linuxnut.co.nz>
> Message-ID: <201101061558.01394.manningc2 at actrix.gen.nz>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Thursday 06 January 2011 15:46:39 Andrew Errington wrote:
> > On Thu, January 6, 2011 10:53, Charles Manning wrote:
> > > On Thursday 06 January 2011 13:01:13 Andrew Errington wrote:
> > >> Yes and no. (I presume you mean 'trivial').
> > >
> > > Yup, I did mean trivial, but it does seem a trial too :-).
> >
> > Yes, the unintentional irony made me smile. :)
> >
> > <snip>
> >
> > > I re-read your doc and see the functions were in the library. Sorry, I
> > > thought those were in the source code.
> >
> > Yes, that is what is most frustrating. They gave me the source to use the
> > library, but I need the source of the library itself.
> >
> > > You use one of those usb snoopers to figure out what is going on.
> > >
> > > eg. http://benoit.papillault.free.fr/usbsnoop/
> > > http://sourceforge.net/projects/usbsnoop/
> >
> > Yes, that is the step after I get the test software compiled, so that I
> > can make some packets worth snooping.
>
>
> Andrew
>
> Another tack...
>
> Since you want to use python at the end anyway, how about this...
>
> From what you have written it seems you have a library. Depending on what sort
> of library it is, you can perhaps use ctypes to call the library from python.
>
> I do as little as possible with Windows, but I believe ctypes works under
> windows and can call DLLs.
>
> -- Charles
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Chchrobotics mailing list
> Chchrobotics at lists.linuxnut.co.nz
> http://lists.ourshack.com/mailman/listinfo/chchrobotics
> Mail Archives: http://lists.ourshack.com/pipermail/chchrobotics/
> Web site: http://kiwibots.org
> Meetings 3rd Monday of each month 6.30pm Science Alive Seminar Room
> Please edit your Subject line to reflect new content.
>
> End of Chchrobotics Digest, Vol 40, Issue 4
> *******************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ourshack.com/pipermail/chchrobotics/attachments/20110107/6cbfc03e/attachment-0001.htm
More information about the Chchrobotics
mailing list