Kingfish
100 MW
Greetings.
I am in the midst of working on a variation of the Parameter Designer for Infineon-clone type ebike controllers. The version I am working on (if successful) will be able to flash the controller using our smartphones and tablets as platforms, and Bluetooth (wireless) in addition to USB connectivity.
It is a bit like XPD on steroids, advancing upon the very good work Anpaza has provided, and leveraging the brilliant configuration model. One distinction between XPD as a first generation open-source and this new second-gen effort is in the stock precompiled controller configurations:
The architectural design I am employing extracts controller profiles and other custom features so that they are exposed for customization, for augmentation, and for adding new model profiles. There’s more involved, and I don’t wish to talk more about vaporware beyond a working prototype. The main point is that each controller profile will exist in an external XML-based (or possibly JSON-based) data store, and that we can modify or clone stock parameters without the need to recompile the application.
The other aspect is that (I hope) we will be able to run on multiple platforms, not just Windows – but iPhone, Android, and Desktop.
Now that you know my story, the survey asks quite specifically which Controller Model Number you own so that I can get a sense of which configurations we need in addition to the following below (and please give thanks to Anpaza for providing them):
EDIT: Removed XPD from the application list because it is already understood.
More information on this development effort here.
Thank you kindly. KF
I am in the midst of working on a variation of the Parameter Designer for Infineon-clone type ebike controllers. The version I am working on (if successful) will be able to flash the controller using our smartphones and tablets as platforms, and Bluetooth (wireless) in addition to USB connectivity.
It is a bit like XPD on steroids, advancing upon the very good work Anpaza has provided, and leveraging the brilliant configuration model. One distinction between XPD as a first generation open-source and this new second-gen effort is in the stock precompiled controller configurations:
The architectural design I am employing extracts controller profiles and other custom features so that they are exposed for customization, for augmentation, and for adding new model profiles. There’s more involved, and I don’t wish to talk more about vaporware beyond a working prototype. The main point is that each controller profile will exist in an external XML-based (or possibly JSON-based) data store, and that we can modify or clone stock parameters without the need to recompile the application.
The other aspect is that (I hope) we will be able to run on multiple platforms, not just Windows – but iPhone, Android, and Desktop.
Now that you know my story, the survey asks quite specifically which Controller Model Number you own so that I can get a sense of which configurations we need in addition to the following below (and please give thanks to Anpaza for providing them):
- EB206, EB209, EB212, EB215, EB218
EB206/Lyen, EB209/Lyen, EB212/Lyen, EB215/Lyen, EB218/Lyen, EB224/Lyen, EB236/Lyen
EB218/Crystalyte
EB306, EB309, EB312, EB315, EB318
EB306/CellMan, EB309/CellMan, EB312/CellMan
EDIT: Removed XPD from the application list because it is already understood.
More information on this development effort here.
Thank you kindly. KF