Edit: The processor is a 16bit NEC:
D79F9211
1635EB40x
Is there any experience with this controller and the XPD software?
Regards
stancecoke
edit: here are some pictures of the circuit board:
Yay I cannot believe how much I have read to finally find the the answer to my issue been on it for about 6hrsCowardlyduck wrote:It's not exactly related to the XPD software, but I had some issues using it after upgrading to Windows 10 recently.
The issue turned out to be with my USB to Serial chip. Apparently Prolific (the makers of most of the chips used in USB to Serial converters) no longer support the 2303 chip on Windows 10.
After doing some digging I came across the blog post below that outlines how to install an older driver from 2008 that makes it work on Windows 10.
http://leftbraintinkering.blogspot.com. ... evice.html
After installing the old driver I was able to run XPD and upload new settings to my controller (18fet EB3) again.
Cheers
I didn't see an answer to the lyen programming cable compatibility question. I have a lyen 12 Fet and his cable does not seem to successfully upload to the controller. (download seems to work)jerome_speedy wrote:Hi all,
I tried to use the XPD program, which seems so much more simple to use than the Keywin software, but I have several problems....
First of all, my Xie Chang controller (supposedly on ver 6, which infineon number does it equate to ?) was delivered with a 5 pin MALE JST plug, which is unsual Also, my USB-TTL cable, bought from Lyen, doesn't have the same colour order from the picture 2 posts before,and the cable loop is not on the same pin number, which is a bit puzzling.
As for the software itself, XPD used under Linux runs well but didn't recognize my controller (not surprising given the wire problem discussed above).
On Windows XP, XPD 3.3 doesn't even start, although all the packages from Sourceforge were installed (Python 2.7 is in the programs menu and the programs launchs).
Any suggestion ? I only want to program the regen braking on my controller, nothing more ! Thanks
And your quote of his post helped me!Galvo wrote:Yay I cannot believe how much I have read to finally find the the answer to my issue been on it for about 6hrsCowardlyduck wrote:It's not exactly related to the XPD software, but I had some issues using it after upgrading to Windows 10 recently.
The issue turned out to be with my USB to Serial chip. Apparently Prolific (the makers of most of the chips used in USB to Serial converters) no longer support the 2303 chip on Windows 10.
After doing some digging I came across the blog post below that outlines how to install an older driver from 2008 that makes it work on Windows 10.
http://leftbraintinkering.blogspot.com. ... evice.html
After installing the old driver I was able to run XPD and upload new settings to my controller (18fet EB3) again.
CheersThank you Cowardly Duck so much.
The program finally recognizes the serial port im using. Ok Ive read heaps but Im a dummy so going to ask anyway as I didn't see my controller. Its a 12fet 3077 mosfets 48v Max 60v can some one please give me an idea of what the settings should be for regen? I had the bike wired for a test run and regen was like changing from 5th to 4th gear and I have been told regen is strong on this controller? I am running a 52v setup. I do have a broken wire that needs mending on the 3 speed switch could that be affecting regen?
Also a quick question. Can you see the settings that are already in your controller? when you plug in the cable does it register the settings? I would like a copy of what it is set at in case I do something undesirable. My controller is below.
How to install XPD (not finished) to Android devices and connect to controller via PL2303HxD+OTG, it's possible ?
anpaza wrote: ↑Jul 23 2017 10:48amNew version for public testing: 0.4.1 alpha.
Download here.
New features:
* Implemented KHxxx (AKA Infineon 4) controller support.
* Implemented profile downloading (EB3xx and KH6xx)
* XPD for Android (from scratch in Java) (not finished yet, so, no test builds for now)
Hi, I'm slightly confused as to whom is the main developer or owner of the project. Can someone enlighten me? As I would like to know is this project is still active or not.teslanv wrote: ↑Apr 05 2017 9:18amI'm adding this thread to the Sticky.
Also, there have been some good advancements with respect to the new version and compatibility with the new Sinusoidal "KH6" boards, (and clones).
Here is a download Link for XPD R4.8 (Most recent version as of April 5, 2017):
Code: Select all
// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
repositories {
google()
jcenter()
}
dependencies {
//Original line:
//classpath 'com.android.tools.build:gradle:2.2.3'
//My correction:
classpath 'com.android.tools.build:gradle:2.3.1'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
allprojects {
repositories {
jcenter()
}
}
task clean(type: Delete) {
delete rootProject.buildDir
}
That is as far as I was able to get as well. I was able to get the APK built last year but I haven't looked at it since then. I attempted to get my development environment fired up again and was able to get an android emulator going in hopes of fixing the crash. Here is the error thrown in the Android Development Studio:
Code: Select all
E/AndroidRuntime: FATAL EXCEPTION: main
Process: ru.cobra.zap.xpd, PID: 3463
java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.Context android.view.View.getContext()' on a null object reference
at ru.cobra.zap.xpd.GuiUtils.fillSpinnerControllerFamilies(Util.java:280)
at ru.cobra.zap.xpd.FragmentProfileEdit.onCreateView(FragmentProfileEdit.java:121)
at android.support.v4.app.Fragment.performCreateView(Fragment.java:2087)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1113)
at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1295)
at android.support.v4.app.BackStackRecord.run(BackStackRecord.java:801)
at android.support.v4.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:1682)
at android.support.v4.app.FragmentManagerImpl$1.run(FragmentManager.java:541)
at android.os.Handler.handleCallback(Handler.java:751)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6119)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)