Q LOGIC PROGRAMMING INTERFACE

[woodygb]

Check your P.M.

[gologen]

Looks new Ebay supplier shows up with cheaper USB-CAN converter.

http://www.ebay.com/itm/USB-CAN-USB-to- ... 257a67d71e

[woodygb]

The Q-Logic Technical Manual.

http://www.icare-jmb.com/Documents%20pa ... QLOGIC.PDF

[D1vad]

The Q-Logic Technical Manual.

http://www.icare-jmb.com/Documents%20pa ... QLOGIC.PDF

That is a starting point, but it is old and outdated for say a Q-Logic in a Pride Q6 Edge, in my opinion. It would be nice to be able to get a hold of a manual for the CTLDC1609 the handheld programer for the Q-Logic controller with color display CTLDC1467

[Burgerman]

Its all you need. In fact you dont need that really. Its all pretty self explanitory.

And if you fiond any setting that are not obvious then 2 things:

Make a note where its set now.

Then set it at lowest, and highest.
Drive and feel what it does. But most are obvious.

DONT CHANGE MOTOR COMPENSATION! Thats the only one that you can really hurt yourself with. Unless you understand its purpose, and usage, and only in small steps.

[D1vad]

What parameters do/should we set the serial port to? And do we wish to connect as a Master or slave device?

Thanks

[woodygb]

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

[zamahuikano]

Hi everyone, this is not the place to discuss the problem that I have with the communication controller curtis 1314-4401 to 1236-6301. I have made or used various usb/serial inverter or without the "7404" and no way to communicate Error 0023 communication and not detected in automatic. I have read that some people connected with USB/CAN it?. I have no wires in my wiring harness, this does not lead. Maybe my copy "3.12 bulid 35, patch 6" 1314 this bad, I've downloaded two, I could update it to a newer version. I have WinXP SP3, I tried in various ports the computer if he sees and installs but does not communicate. On the other hand I have a 840 spyglas which continually sends me error code 39, I have not installed the main contactor connected, motor and encoder, all wiring necessary to communicate and programming?. I need to remove the error to communicate? Any help will be much appreciated, greetings.

[woodygb]

Have you read thru the Buggies forum?

http://www.buggiesgonewild.com/electric ... er-37.html

I very much doubt that the 1314 software is the problem...and the USB-CAN isn't the way for you to go with your controller.

Is your COM Port assigned a number under 9 and does your COM Port show up in the 1314 software?

[woodygb]

NOTE THIS ONLY APPLIES TO CURTIS SCOOTER OR BUGGIE CONTROLLERS.

Rather than the 7404 chip use a SN74HC14N

gridBSM.jpg (78.76 KiB) Viewed 23008 times

SERIAL ADAPTOR INTERFACE curtis.jpg (138.04 KiB) Viewed 23008 times

[zamahuikano]

Hi and thanks, I've tried assigning ports COM1, 2 or 3 and none of them I can communicate. I can see the port assigned in the device manager and when I open is also 1314. As I have tried several USB/Serial as Belkin, PL2303 chip and one with CH340, I always get "code39" I see with the Putty or spyglass 840, but not communicate with the 1314 "Error 0023". One of my questions is whether it is necessary to have everything connected to program and/or communicate. I say this because I have the controller working in the bank provisionally and truth circuits seeing so many different ways and many people talking about their problems, I'm lost.

[D1vad]

Hi and thanks, I've tried assigning ports COM1, 2 or 3 and none of them I can communicate. I can see the port assigned in the device manager and when I open is also 1314. As I have tried several USB/Serial as Belkin, PL2303 chip and one with CH340, I always get "code39" I see with the Putty or spyglass 840, but not communicate with the 1314 "Error 0023". One of my questions is whether it is necessary to have everything connected to program and/or communicate. I say this because I have the controller working in the bank provisionally and truth circuits seeing so many different ways and many people talking about their problems, I'm lost.

If I understand you correctly you are getting a code 39 error in device manager. If that is correct you are going to need to fix that error before you will get a working interface....

Have you uninstalled ALL SERIAL PORT DRIVERS? There are a number of possible causes of a device manager code 39 error, I suggest that you google device manager code 39 error and follow the instructions for un-installing all serial port drivers... I posted on another thread how to show devices that are not present on your system in order to uninstall them.

[woodygb]

I always check my leads communication with a loopback test via a utility called Dacio .. the RX and TX is simply joined together and a signal sent from TX to RX.
http://www.buggiesgonewild.com/electric ... er-54.html

[zamahuikano]

Hi, I have not explained well. The COM device manager driver are correct, the error "code39" gives curtis 1236 controller to applying power to program "This error sends him back to back which I can see with Putty or spayglass 840. As I say the Com drivers is installed without any errors.'ve tried on several COM "1.2, y3".

[woodygb]

If you wish I can provide you with a lead that works for me.

[Burgerman]

As I say the Com drivers is installed without any errors.'ve tried on several COM "1.2, y3".

Inevitably this always turns out to be the problem. Wrong setup, old or wrong drivers, port settings, or port sharing, or USB port conflict errors.

Never found one that I couldn't get working yet. Regardless of people telling me it wasn't possible. At least with the correct lead, wired correctly.

[zamahuikano]

woodygb thank you very much, I really appreciate it. I'm waiting for a USB/Serial IOGEAR GUCXXXX not remember the exact number, but some people say it has worked. If you can help me with a USB/Serial would solve many doubts and problems. Tell me more to realize, if you'd send me an PM as you want.
CODE39 will clarify that the error is due to its current configuration, is a second hand controller and configured, but I want to configure it for my project and I can not communicate with. The USB/Serial I install I previously did not have errors in device manager and when it started the 1314 could see the correct COM but without communicating. See the screenshot and you will see that is installed on COM2 and the message that gives automatic 1314. If I try to connect to manual ERROR 0023.
thanks and regards.

[zamahuikano]

The cheap blue USB/Serial CH340 works perfectly. The protocol used in the 1314 is the Enhanced Serial COM2 and lower the minimum buffers on the properties of the serial port "device manager".
screenshots:

USB/Serial CH340

1-340.jpg (133.78 KiB) Viewed 22031 times

connections TX, RX and GND

2-SERIAL ADAPTOR INTERFACE.jpg (109.76 KiB) Viewed 22031 times

Enhanced Serial COM2

3-serial.jpg (91.18 KiB) Viewed 22031 times

Thank you and greetings

[jptrx]

Hi Guys
The first thing I would like to say is thanks to Woody and Gologen for the effort put forth here to help us all.
This thread is layed out in a very easy to follow manner with the steps in the first post. I have tried everything I can think of, but still having a problem getting the 1314 to communicate with my Q-logic controller.

I am using PC PS #1314-4401, version 3.12, update patch 4.
I have the A1+ Chinese USB CAN that Gologen has
I have installed Gologens LXN4py2s.dll (NetPorty driver).
I have installed the QM-USB file.
I have windows Vista 32 bit.

I am only able to get the 1314 connected as “MC-2 Master” and never SLAVE. I have tried com1 com2 and com3, with the same results. I have never had the 1314 find a “connected device”.

This is what the quick reference help manual says (page 29):


"The PC-PS acts as network slave. If there is a network master (Controller) present on the bus, it is now bound to the system as an additional node (Device).

If the network master is either not present or not functioning, the PC-PS automatically tries to overtake the role of the network master. In this case, be aware of connecting a Controller Device to the bus, as in this case two network masters in the system would lead to an unstable situation. For this reason, anytime the PC-PS connects as network master, a corresponding warning message is issued:

In either of the 2 modes, SLAVE or MASTER, after the network binding is finished, the PC-PS scans the bus for all connected devices. "


If anyone has any suggestions, I would be very thankful.

.

[D1vad]

What com port is your A1+ device using? If it is not com1 try switching it to com1

[woodygb]

As D1vad says ...it's probably a COM Port miss match

BOTH the COM Port assigned by Windows and the COM Port selected in the 1314 prog must be the same.

Your A1+ Chinese USB should be assigned COM1 in Windows Device manager.

You should pick SLAVE and COM1 in the 1314 prog.

[jptrx]

I wish it was a simple com port miss match, but its not. I have tried, very carefully ports 1,2 and 3 , and always been sure to match the 1314 MC-2 protocol setting to the setting shown in windows device manager.

If I intentionally create a com port miss patch there is a error window that instantly pops up when you try to connect. This is not what is happening.

Whats happening in my system, is the 1314 does connect, but it does so as the "Master" and not the "slave". See my first post for a quote from the manual, thats exactly whats happening. When the 1314 does connect as "Master" I get a warning that is mentioned in my first post.

So the 1314 is not detecting the USB-Can device, and so it by default connects as "master". I just cant understand why it does not detect, because if i deliberately assign com port #1 to the usb-can device in device manager, and use port #3 in 1314 protocol, it detects the error instantly.

Woody: That program you use to check your cables with, will it work with Windows Vista?

Also, when 1314 is connected as "Master" along the bottom of the 1314 window it shows "Interface:CAN" , "Mode:MASTER", "User Group:OEM"

[LROBBINS]

This is probably a stupid question. Was your WC controller turned on when you tried to connect? Ciao, Lenny

[woodygb]

Woody: That program you use to check your cables with, will it work with Windows Vista?

Yes ..BUT .. ( to the best of my knowledge ) it will not work to test the CANBUS transmit and receive.

[jptrx]

This is probably a stupid question. Was your WC controller turned on when you tried to connect? Ciao, Lenny

Not a stupid question, the simple stuff needs to be looked at. Yes, controller turned on.I have tried a number of different start-up sequences, all with the same results. The sequence I try most often is the one Gologen posted.

Here is a simple test anyone with a properly working setup could try, and please report back:

Try to connect to your Q-Logic controller the way that normally works for you, but deliberately do not connect the cable from your USB-Can device to your Q-Logic programming port, leave it unplugged. Please report back on what happens when you try to connect with 1314 as "Slave".

Does the 1314 connect as "slave" or "Master" ? (If a connection is made you will see it referred to as Slave or Master at the bottom of the 1314 window).

If the 1314 does not connect at all, what error message do you get?

Thanks for the help!

[gologen]

1. Check CAN-H and CAN-L connected correctly and jumper 120 Ohm in the place.

port.JPG (12.75 KiB) Viewed 20555 times

2. Be shure port you chose at 1314PCPS assigned to your device A1+ at Device Manager and working properly (no yellow mark). Manual 1314PCPS says Com1 or Com2.
3. Be shure WC controller power ON.
If no luck:
Try to test your A1+ device with "CAN bus Debugging tools". Connect your A1+ to WC controller. Power ON. Set CAN speed 250 KBPS. Port - assigned to your A1+ at device manager. Push "Connected device".

debugg.JPG (79.77 KiB) Viewed 20555 times

What you see? If nothing happens - you choose wrong port, CAN-H CAN-L connected oposite or your device A1+ doesn't work.(or your WC controller doesn't work???).

[jptrx]

Hi Gologen , thanks for your help.

#1. The 120 ohm jumper is the one next to the blue terminal block on the A1+ device? If thats the jumper you mean, I have it.

I have tested with the debbuging tool. The only thing that happens when I push "connected device" is the green font that says "PORT CLOSED" changes to "NORMAL". If I then push "release device" again the green font changes to "PORT CLOSED". This is done with the wheelchair power on, and connected to the A1+

[jptrx]

I should also mention that I programmed this chair with a Pride/Curtis handheld programmer on the weekend and it worked perfectly.

I suspect my A1+ is faulty.

[gologen]

I did screenshot debugging program. You should get something like this.
Status "Normal" and running data at the bottom part.

debugg1.jpg (114.65 KiB) Viewed 20541 times

If no reading data - possible your device is faulty or wrong connection CAN-H and CAN-L.

[gologen]

Try to do hard reset your device - disconnect from USB and connect again. After run debugging program.