PGDT Serial interface cable ...USB Alternative :D

[woodygb]

2 of the boards in the selection I sent BM had that number on the board... AND a stick on label...
20111216 0804 u2
1009015221 0804 u2

this may no longer be in your lead.

[brax]

2 of the boards in the selection I sent BM had that number on the board... AND a stick on label...
20111216 0804 u2
1009015221 0804 u2

this may no longer be in your lead.

Sticker inside usb case reads 903120452
no additional numbers or letters on sticker.

peace
brax

[woodygb]

Cheers ...that maybe info enough for me to chase the board origin/type.

Oh...did it say MAXTON anywhere?

[brax]

[quote="woodygb"
Oh...did it say MAXTON anywhere?[/quote]

yes on the board it said

"MAXTON
0804-u2"

[woodygb]

DOH!

[Burgerman]

Meaning?

[woodygb]

The DOH! means that I should READ the posts ...as the info requested was already there.

[Frostie Flake]

I've looked at a completly different control system. What I have done some preliminary design on is a networked system that can be connected via Ethernet or WiFi. (obviously you want to disable WiFi) avawhen using chair programming and no firewall enabled. With the fire wall enabled a complete communication system can be configured with both Ethernet and WiFi connectivity for an onboard mil spec mini server.

Controller code can be managed via a Java embeded Virtual Machine interface that works in resltime. I have begun to also create connectivity for other devices via Ethernet or USB. My ultimate goal is to us iPad and/or iPhone where WiFi is not available. Also Panasonic makes a mil spec computer that would be also a good choice when in very rugged environment.
Radio control of the chair has also been of interest where both mine and my wife's chair can be tucked away in the back of the Mercedes Sprinter. A lift system moves my wife and I to driver and passenger seats.

[Burgerman]

I think you might need to start at the beginning, because I am lost!

I already have a radio controlled setup for my powerchairs.

Can you explain what controllers your chairs have, how or why you need this other stuff?

And since I dont think its related to this ongoing thread about a programming cable can you start a new thread? Thanks!

[expresso]

Hi - does anyone know the status of when working cables will be ready ?

i am in need of one --

thanks -

[woodygb]

B.M. is kindly continuing to help in this endeavour.

The current leads that I have don't connect on his puter ( Win7 64 bit ) and PILOT+...
The current leads that I have connect fine on MY puter ( Win XP ) and PILOT no plus...

I need to eliminate a variable .... to this end I've posted him the PILOT that I use for COMMS testing.

The only difference is then the puter and the O.S.

The logic now goes like this IF B.M. plugs in and can connect to the PILOT ..then it's the PILOT that must use a slightly different COMMS protocol to the PILOT+ and I need to chase around and track down the exact spec of the first KPG-4 lead.

IF B.M. can't connect then it's more than likely a driver problem ... the PL2303 Chip Driver is a complete knightmare it comes in various flavours for different O.S. ...and even if it say's that it is installed correctly it may not work for a specific application, thus entailing a hunt for one of the driver versions that will.

[woodygb]

IF I was starting again I'd probably have a look at the USB9097 1 Wire Adapter which appears to use a different chip set made by ChipHead and driver CH341.

[woodygb]

I might as well continue with an explanation of my confusion on the apparent failure of the original KPG leads .

Malamar has a lead ...in fact two .. a KPG based lead and an ICOM based lead.... neither of these will connect to his controller despite the driver appearing to be installed correctly.

I've attempted to help via private messages but he isn't very computer savvy and I'm not that familiar with WIN 7 ( In Spanish!) .... he has been very understanding and has happily paid for the first cable ...I'm refusing payment for the second.

B.M. has made two ICOM based interface leads ( these are single or one wire comms protocol leads ) ... neither of his work... but the same lead works for me with the PILOT ( no plus ) controller.


The first lead I purchased via Radio Arena was a KPG-4 (6 Pin plug ) and had 4 wires in the lead ... the red wasn't connected at the board thus it was a 3 wire RX TX and GND and was tested by B.M. as working fine.

The KPG-46 lead ..( 8 pin plug ) SHOULD be exactly the same ,as the only difference ...according to a web search ...is the socket on the Kenwood Radios that it is intended to program.... in fact you can use the 6 pin plug in the 8 pin socket ..the connections match IF you insert the 6 pin plug into the left of the 8 pin socket ( pin 6 = pin 8 )

kpg plugs.GIF (3.34 KiB) Viewed 10391 times

I started this project with the realisation that I'd need to spend a few pounds and a deal of time in trying to find an interface solution .. the time I can afford... the initial outlay was fine as it was my choice and kept me occupied ... to date I'm approx £150 out of pocket.

I'm still happy to spend a few pounds trying to sort this out but I'm loathe to buy anymore leads till it is ...
Sorry to disappoint people but making and shipping leads that refuse to work for others is pointless.

[Ashley G]

I might as well continue with an explanation of my confusion on the apparent failure of the original KPG leads.

Personally, I am very glad that you did, thank you. I haven't been able to add anything constructive, but I am reading with much interest.

Sorry to disappoint people but making and shipping leads that refuse to work for others is pointless.

Can't argue with that reasoning, but I genuinely hope folk appreciate the value of your efforts to date. It isn't just something which could benefit many of us - it happens to be something which is a complete PITA for those of us affected and it would have been - may yet be - one enormous poke in the eye for wheeliebin manufacturers if and when you suss it.

Regards

Asjhley

[woodygb]

DOH! ...

IF you insert the 6 pin plug into the left of the 8 pin socket ( pin 6 = pin 8 )

IF you insert the 6 pin plug into the 8 pin socket ( pin 6 = pin 7 )

[Burgerman]

He HAS sussed it once, as tested by myself! Cant understand why its now changed...

[woodygb]

He HAS sussed it once, as tested by myself! Cant understand why its now changed...

Possibly a different batch/build of KPG leads / USB boards.

Hopefully you'll recieve the PILOT today or tomorrow and testing will throw some light on which direction to take.

[woodygb]

I've also PM 'ed both SEGREEN and NICK99 ... who both have working leads ...asking for the specs on their puters and the installed driver version.
BRAX has already given his ...

driver details.
ser2pl.sys
Prolific 12/1/2003 version 2.0.0.24
Windows 7 32bit.

[Burgerman]

I would like the original mini disk. I should have copied it.

[woodygb]

I did .... but it's mixed in a folder now with various other alternatives.

I have uploaded what I believe are the original files here.

http://sdrv.ms/LVMfvF

I'll ask Brax ... I think I posted it with the original lead to him ... for a copy.

They appear to be EXACTLY the same as those on the ICOM disc.

[Burgerman]

my two leads on windows 7 64bit do not talk to pilot or pilot plus. Your boxed up leads have not yet been tested. What next?

[malamar]

Woody...you know too well how grateful we all are to you for your efforts. We just need that piece of equipment.
Up to the point of funding the investigations between us, the need arisen...i'm sure.
And then controllers of 100 amp/h ones; and with your abilility in electronics, mounting lithium packs for the dumb of us should be great for you too...
Cheers

[woodygb]

my two leads on windows 7 64bit do not talk to pilot or pilot plus. Your boxed up leads have not yet been tested. What next?

Well ... it appears to be a Windows 7 /driver prob.....

Try mine just in case ...but I don't think you'll get any joy.

Then perhaps try Prolific
12/1/2003 version 2.0.0.24
ser2pl.sys

I think that you have a copy of

PL2303_Prolific_DriverInstaller_v130.exe

...as I recall that has an option ..when run .. to MODIFY - REMOVE - REPAIR

Choose Remove present drivers and try with one of the others..?

[woodygb]

OUT/AWAY for an hour now.

[woodygb]

Additional info that maybe relevant to some ...
I have seen one post on the web where it was reported that the uninstallation of McAfee Antivirus "cured" a Prolific driver prob.

Back to driver choice....

The other option that worked for Segreen was...updating the driver manually.

viewtopic.php?f=2&t=1965&st=0&sk=t&sd=a&start=40#p25498

[expresso]

I agree with the antivirus - disable that all the time when you do installations etc, - they cause alot of issues - and mostly false alarms --

i had to disable it even when i install normal programs - - once installed - you can enable it again -

i hope thats the solution - i am running Win 7 - 32 bit - - 64 bit users may have more issues - due to the 64 bit OS -

very good news i think -

[woodygb]

IF B.M. gets no joy..... I might post a couple to Segreen ( who has a working lead that he made ) ASSUMING he's is running Windows 7 of some description.

Segreen has just come back from a lengthy period away and has acknowledged my request for info ...but has yet to get settled back home.

[Burgerman]

Problem I have is that I have a multitude of drivers, but no idea which is which. So I uninstall (and delete) from device manager, and then am guessing which one is which...

But the only one that seems to work is always the same one. But that says comm inactive.

[woodygb]

And that driver has a version number and date?

I suspect that yours should say ....ser2pl64.sys

[woodygb]

driver ser2pl64 ...NO idea if it's the correct one or if it might fix the prob.

ser2pl64.zip

(41.82 KiB) Downloaded 302 times