Tryker

I was just pointing out a discrepancy. I have no idea if there is a standard to wiring Julet/HIGO plugs as they don't seem to be that common especially on the Chinese controllers. Different controllers provide all sorts of different connections depending on their available functions. The LCD panels also provide different functions dependent on the capability of the controller. For example the LCD1 provides walk assist when the motor is running at or less than 6kph, but a cruise control for speeds of 7kph or greater using the same button press: the controller would have to support this though. The TX/RX data connection was suggested by D8veh in another thread, and logically this makes sense: the controller contains a computer system on a chip which has program memory and data memory in flash ROM. There is working RAM too. I would think the controller should be regarded as a computer that has to boot into its normal operating mode after switch-on and one thing it does is check for the presence of an LCD (which, I believe, also contains a computer on a chip). I suspect it may wait indefinitely if it gets no response during initialization or it may be designed to revert to a default condition after a wait period. Looping back its data connection makes sense if this is the case, to avoid any startup delay or even failure to start. The pin 5 connection is intended for a key-switch input to lock the system, obviously easy to over-ride for those in the know who might be able to hot-wire it.

Hear, hear to Alan's problem as I too am interested in this, but further information for yours: my motor is on a 26" wheel and Labelled XF40 30H which is a MXUS 1000W motor. This number is followed by 250W but nowhere does it say restricted. The motor number you give I'm unable to find any reference to on the internet, I suspect it's the same motor though. Also the shorting plug info given by Harrys is different to yours: he suggests pins 1-5 and 2-3 are linked (not 3-4 as in your diagram). Maybe, as I suggested, there is a wiring difference between the controllers and your shorting plug isn't connecting TXdata to RXdata. I suggest the only accurate way to find out is by opening the controller and belling out the multi-way plug back to the circuit board to find out which pins to connect together: your shorting plug may not be shorting the correct pins.

I don't think it's possible to change the program stored on the controller microchip just by re-plugging things. The parameters which control things may have changed though. I think you should check P4 parameter it should be 0 (for throttle to work without pedalling: zero startup) and this parameter is common to both the LCD1 and LCD3 panels for all controllers.

I've researched this as extensively as seems possible and it boils down to Cyclotricity being cagey about their kit. I can only assume that they have made some mods but are unwilling to release what they are. The P6 parameter is completely undocumented by anyone other than Cyclotricity and there doesn't appear to be a solution. I'm only just learning this stuff so class myself as a novice although I am an electronics engineer. From all that I've discovered Cyclotricity say that their LCD is needed to unlock the high power mode. This is confirmed by your initial wrong one supplied to you. I don't know how the controller is crippled to 250W until their P6 code is entered and only their KT-LCD1 has the P6 parameter available. It is possible that the C codes of the KT-LCD3 may be possible to unlock the controller but knowing what code is a mystery: Cyclotricity seem unwilling to provide this information, if it is available, from what you say. The upshot is that it looks like the controller is restricted and locked to the Cyclotricity KT-LCD1. I can only assume that they have a custom program on the controller and there is no obvious way around this. The only possible workaround that I can see is to use something like their LCD1 and mod the controller to take a direct plug Cycle Analyst to control the power delivered to the motor used in tandem OR replace the controller for one that's compatible with the KT-LCD3. This would leave you with a potentially illegal system (although it may be argued that the Cyclotricity system is dubious in its legality anyway), but I think you can set the LCD3 to run the system at the reduced power level, but switching between power levels may not be as straightforward as the P6 parameter switch. All in all it looks like an awkward and unacceptable position from Cyclotricity. I am becoming not so impressed. It also means, if this is correct, that the controller won't work with anything else as the rating on its label is incorrect.

I was replying to Alan but I found your comment interesting. Unfortunately I can't see a simple solution to your problem either, doh! I suspect that the Yose wiring may be different so looking inside and tracing its connections may be the only way to work out a solution: if the linking of data TX and RX is possible and a link for the key ('on') signal to make a throttle work. The terminology of speed set hall is a little confusing because a throttle is a hall sensor powered from the controller. I'm guessing it's possible to make this work but is probably just a wiring issue. I could be wrong.

I'm assuming that diagram refers to the green connector which normally goes to the LCD panel. I've just belled out my cable to the controller and the links appear to be +ve volts (pin1) to the 'on' line (pin5). The others link TXdata(pin3) to RXdata(pin4) in the controller. The throttle would be connected through the yellow connector. Is this link plug supplied by Cyclotricity for a display less system? If so this confirms (with the fact that a replacement LCD was needed to enable the 1000W setting) that the P6 parameter only appears in a Cyclotricity modded KT-LCD1.

I'm in a similar position as I have the Cyclotricity 250/1000W kit, however I would check your controller as, according to the programming hack link you posted, the ZWS type controllers can not be hacked (correction: it looks like there is a programming interface marked SOFT on my controller. The problem with this hack seems to be something to do with Sinewave control/Field Oriented Control, which I'm not sure how this applies, or not, to the Cyclotricity system.) using that software and hardware mod. It looks like the only option is to replace the controller with one that works with a KT-LCD3 unit but you would lose the power level control. I have been looking at a Cycle Analyst to do the control, but from my understanding this would still be unable to override the controller's programming and the KT-LCD1 provided by Cyclotricity seems the only way to do the switch. The CA would be able to control the power settings of a suitable controller though, as it can store 3 power settings which would allow duplication of the Cyclotricity setting. This effectively means replacing all the control electronics provided by Cyclotricity and looks like quite an expensive option although does have a power meter included. I've also looked at adding a CA connector to the ZWS controller so this can do all the power control, but even this would need the KT-LDC1 to set the controller to output its full power via the P6 parameter. I'm not sure if I've fully understood the problems yet as I've only just started researching this.