Curtis connects to terminal, but not to the 1314 programmer

[zamahuikano]

Hello; I have been reading the forum up and down looking for any clue about my connection problem. As I didn't find anything I am opening this thread (well, I found lots of hints about connection problems and tried many of them, but it seems my problem is somewhat different).

I got a Curtis 1236, used. I don't know much about it's previous settings or use conditions.
I tried connecting to it without motor, throttle...Terminal software (putty & dacio) showed error codes (scode x) signaling the parts that were missing, like the motor. Curtis software 1314, however, refused connection:

"Error 0023 Initialization of communication interface failed. Communication error with controller"

After assembling all the parts requested by the controller, the controller stopped printing error codes and printed run info like RPM, Amps, etc...I can change that info with the "menu mode" switch. Again, I can see all that using putty, dacio, etc.
The controller seems to work, it will accelerate the motor (the encoder settings are probably wrong, but it works anyway).

But the programmer software still refuses to connect.
I have tried 4 differente USB/Serial adapters, some will show the terminal output correctly, others will not. I even tried with an old win98 PC, but the programming software still refuses to connect (terminal work though).

Using an oscilloscope I have checked some bits are sent in the TX wire, but still conection is not established.

I did also read about entering commands in the terminal, using ":". But it does not seem to work; sometimes the output of "RPM x" info will stop for a moment but will resume activity soon.

Some questions for the experts:

- I have a 840 display installed, it shares the bus with the programmer cable. Is that ok with the programming process, or should I remove it? (I tried with & without).
- Can be the Curtis controller set up as non-programmable? Is it possible or controller is programmed (using VCL) to avoid programming?
- I have seen captures of users sending commands in the terminal. My terminals are full of controller output text (RPM - RPM - RPM...). Maybe there is a "program mode" or something similar I have overlooked?

Hope somebody can offer a clue

[DonBenigno]

See in red below

Originally Posted by zamahuikano

Hello; I have been reading the forum up and down looking for any clue about my connection problem. As I didn't find anything I am opening this thread (well, I found lots of hints about connection problems and tried many of them, but it seems my problem is somewhat different).

I got a Curtis 1236, used. I don't know much about it's previous settings or use conditions.
I tried connecting to it without motor, throttle...Terminal software (putty & dacio) showed error codes (scode x) signaling the parts that were missing, like the motor. Curtis software 1314, however, refused connection:

"Error 0023 Initialization of communication interface failed. Communication error with controller"

After assembling all the parts requested by the controller, the controller stopped printing error codes and printed run info like RPM, Amps, etc...I can change that info with the "menu mode" switch. Again, I can see all that using putty, dacio, etc.
The controller seems to work, it will accelerate the motor (the encoder settings are probably wrong, but it works anyway).

But the programmer software still refuses to connect.
I have tried 4 differente USB/Serial adapters, some will show the terminal output correctly, others will not. I even tried with an old win98 PC, but the programming software still refuses to connect (terminal work though).

Using an oscilloscope I have checked some bits are sent in the TX wire, but still conection is not established.

I did also read about entering commands in the terminal, using ":". But it does not seem to work; sometimes the output of "RPM x" info will stop for a moment but will resume activity soon.

Some questions for the experts:

- I have a 840 display installed, it shares the bus with the programmer cable. Is that ok with the programming process, or should I remove it? (I tried with & without).
I know for a fact you can have a 840, I have one running with a 840 and a 1314 programmer as well as a 1311
- Can be the Curtis controller set up as non-programmable? Is it possible or controller is programmed (using VCL) to avoid programming?Yes, in VCL you can actually assign access levels.
- I have seen captures of users sending commands in the terminal. My terminals are full of controller output text (RPM - RPM - RPM...). Maybe there is a "program mode" or something similar I have overlooked?


Hope somebody can offer a clue

[Stevegrmich]

. . . which version of the 1314 software are you using? It comes in 4 versions, each with different levels of access . . .

1314-1101 - User Access (very limited)
1314-2201 - Service Access
1314-3301 - Dealer Access
1314-4401 - OEM (Greatest Access)

[zamahuikano]

thanks for replying, I am using 1314-4401 "downloadable version".
I think I remember v3.12 build 35 patch 6.

[Stevegrmich]

Originally Posted by zamahuikano

thanks for replying, I am using 1314-4401 "downloadable version".
I think I remember v3.12 build 35 patch 6.

. . . that is same version I use successfully . . . however, it took me awhile to resolve the connection/communication error . . . the blue CH340 USB/serial cable is the easiest way to go, but it took me trying different CH340 cables until I found one that worked . . . actually had to have a verified working cable shipped to me from London by WoodyGB . . . I sent him my non-working cable which he disassembled and found a bad solder joint . . . it may be as simple as buying a few cheap blue CH340 cables off ebay to get one that will work . . they sell for about $3 US . . .

[zamahuikano]

After many hours and errors I managed to communicate with the controller.
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".

[zamahuikano]

screenshots

[Stevegrmich]

Originally Posted by zamahuikano

After many hours and errors I managed to communicate with the controller.
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".

. . . great . . have fun . . .

[ericshufro]

Originally Posted by zamahuikano

screenshots

Think you can help me? I have tried everything and cannot get a connection. I put a scope on it as well and I see some back and forth, as well as bit errors. I tried lowering the fifo sizes which helped a little when using an FTDI adapter. My CH didnt work in the past and its loaned out at the moment.

Any idea what the signal levels should be?

RS232:
- Idle LOW
- 9600bps ?

I assume RS232 compatible, no inverters or level shifters needed. Straight from PC to cart?

Thanks

-e

[KRAZYMATT]

You probably need the 1309usb cable. Not all the controllers use rs232 only a few of the older ones. Most are enhanced serial and need the 1309usb cable.