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