| case 'commute' : console.log('setting commute mode'); app.mbb.send('set'); setTimeout( function(){ app.mbb.send('peak'); app.mbb.send('400'); app.mbb.send('lowsp'); app.mbb.send('50'); app.mbb.send('lowtq'); app.mbb.send('50'); app.mbb.send('medsp'); app.mbb.send('50'); app.mbb.send('medtq'); app.mbb.send('50'); app.mbb.send('econsp'); app.mbb.send('50'); app.mbb.send('econtq'); app.mbb.send('50'); }, 5000 ); setTimeout( function(){ app.mbb.send('map'); app.mbb.send('5'); app.mbb.send('stage1'); app.mbb.send('135'); app.mbb.send('stage2'); app.mbb.send('155'); app.mbb.send('stage3'); app.mbb.send('175'); app.mbb.send('tempfan'); app.mbb.send('75'); app.mbb.send('contopen'); app.mbb.send('75'); app.mbb.send('scale'); app.mbb.send('65'); }, 10000 ); break; case 'race' : console.log('setting race mode') app.mbb.send('set'); setTimeout( function(){ app.mbb.send('peak'); app.mbb.send('490'); app.mbb.send('lowsp'); app.mbb.send('100'); app.mbb.send('lowtq'); app.mbb.send('100'); app.mbb.send('medsp'); app.mbb.send('100'); app.mbb.send('medtq'); app.mbb.send('100'); app.mbb.send('econsp'); app.mbb.send('100'); app.mbb.send('econtq'); app.mbb.send('100'); }, 5000 ); setTimeout( function(){ app.mbb.send('map'); app.mbb.send('0'); app.mbb.send('stage1'); app.mbb.send('175'); app.mbb.send('stage2'); app.mbb.send('180'); app.mbb.send('stage3'); app.mbb.send('185'); app.mbb.send('tempfan'); app.mbb.send('30'); app.mbb.send('contopen'); app.mbb.send('98'); app.mbb.send('scale'); app.mbb.send('85'); }, 10000 ); break; |
EC,
I'm new to the Zero framework and would like to better understand where the set up values reside and how you reconfigure them (provided you are willing to share).
A few simple questions to start-
Were do the set up values you describe in your table deffinitions reside? Is MBB the main battery board? I ask because I thought the overall ECU interfaced and controlled the Main Battery Board and the Motor Controller.
How do you talk to this device (both manual button pressing and automated configuration download)?
Has Zero expressed an opinion on how changes of any kind might affect the warranty?
I've got an electrical design background and have written a good bit of microcontroller code so technical answers work for me.
Thanks,
Bill
Were do the set up values you describe in your table deffinitions reside? Is MBB the main battery board? I ask because I thought the overall ECU interfaced and controlled the Main Battery Board and the Motor Controller.
How do you talk to this device (both manual button pressing and automated configuration download)?
Were do the set up values you describe in your table deffinitions reside? Is MBB the main battery board? I ask because I thought the overall ECU interfaced and controlled the Main Battery Board and the Motor Controller.
How do you talk to this device (both manual button pressing and automated configuration download)?
The key value pairs reside in the MBB(main bike board) and are sent over RS232 to the MBB settings.
On the 2011 the controller really does not have any adjustable settings that make a difference, everything is best done through the MBB.
I am always willing to share as much as possible.
If you want I can build you an interface for under $200 that would expose your 2011 Zero to a smartphone or web app. Not sure if people are interested in paying for an interface for the 2011's.
I could also do a remote desktop session and program your bike directly for you at a lesser expense, even so you would probably have to spend about $50 on the necessary cable.
Were do the set up values you describe in your table deffinitions reside? Is MBB the main battery board? I ask because I thought the overall ECU interfaced and controlled the Main Battery Board and the Motor Controller.
How do you talk to this device (both manual button pressing and automated configuration download)?
The key value pairs reside in the MBB(main bike board) and are sent over RS232 to the MBB settings.
On the 2011 the controller really does not have any adjustable settings that make a difference, everything is best done through the MBB.
I am always willing to share as much as possible.
If you want I can build you an interface for under $200 that would expose your 2011 Zero to a smartphone or web app. Not sure if people are interested in paying for an interface for the 2011's.
I could also do a remote desktop session and program your bike directly for you at a lesser expense, even so you would probably have to spend about $50 on the necessary cable.
Were do the set up values you describe in your table deffinitions reside? Is MBB the main battery board? I ask because I thought the overall ECU interfaced and controlled the Main Battery Board and the Motor Controller.
How do you talk to this device (both manual button pressing and automated configuration download)?
The key value pairs reside in the MBB(main bike board) and are sent over RS232 to the MBB settings.
On the 2011 the controller really does not have any adjustable settings that make a difference, everything is best done through the MBB.
I am always willing to share as much as possible.
If you want I can build you an interface for under $200 that would expose your 2011 Zero to a smartphone or web app. Not sure if people are interested in paying for an interface for the 2011's.
I could also do a remote desktop session and program your bike directly for you at a lesser expense, even so you would probably have to spend about $50 on the necessary cable.
i've done a fair amount of hobbiest specialty device building based primarily on arduino and arduino-like controllers, all for my own use (home irrigation controller, entertainment system controller, thermostats, etc). i'd really be interested in building such a bike interface myself. however, of course i lack enough knowledge of the bike's design, and the communication system/protocols. not sure where to look to learn.
Hey guys,
Just thought I would share a snippit of the code I wrote for my first Foxy project. These were my commute & race settings, as set by the framework I built to interface with the Zero MBB.
You can still input them manually if you have access to the mbb, just use the key and values you see in the code below.-Electric Cowboy
case 'commute' :
console.log('setting commute mode');
app.mbb.send('set');
setTimeout(
function(){
app.mbb.send('peak');
app.mbb.send('400');
app.mbb.send('lowsp');
app.mbb.send('50');
app.mbb.send('lowtq');
app.mbb.send('50');
app.mbb.send('medsp');
app.mbb.send('50');
app.mbb.send('medtq');
app.mbb.send('50');
app.mbb.send('econsp');
app.mbb.send('50');
app.mbb.send('econtq');
app.mbb.send('50');
},
5000
);
setTimeout(
function(){
app.mbb.send('map');
app.mbb.send('5');
app.mbb.send('stage1');
app.mbb.send('135');
app.mbb.send('stage2');
app.mbb.send('155');
app.mbb.send('stage3');
app.mbb.send('175');
app.mbb.send('tempfan');
app.mbb.send('75');
app.mbb.send('contopen');
app.mbb.send('75');
app.mbb.send('scale');
app.mbb.send('65');
},
10000
);
break;
case 'race' :
console.log('setting race mode')
app.mbb.send('set');
setTimeout(
function(){
app.mbb.send('peak');
app.mbb.send('490');
app.mbb.send('lowsp');
app.mbb.send('100');
app.mbb.send('lowtq');
app.mbb.send('100');
app.mbb.send('medsp');
app.mbb.send('100');
app.mbb.send('medtq');
app.mbb.send('100');
app.mbb.send('econsp');
app.mbb.send('100');
app.mbb.send('econtq');
app.mbb.send('100');
},
5000
);
setTimeout(
function(){
app.mbb.send('map');
app.mbb.send('0');
app.mbb.send('stage1');
app.mbb.send('175');
app.mbb.send('stage2');
app.mbb.send('180');
app.mbb.send('stage3');
app.mbb.send('185');
app.mbb.send('tempfan');
app.mbb.send('30');
app.mbb.send('contopen');
app.mbb.send('98');
app.mbb.send('scale');
app.mbb.send('85');
},
10000
);
break;
totally unfamiliar with CAN bus or anything similar. trying to decipher practical implications of your post. is it the case, for example, that if i knew which physical port to connect to (2012), and it's pinout, and, for example, it's baud rate, that i could simply send those command pairs over in sequence, i.e.
set
peak
490
lowsp
100
...etc
to configure the race mode you created?
any additional info would be appreciated, and likely productive with respect to my previously stated goal.
i've done a fair amount of hobbiest specialty device building based primarily on arduino and arduino-like controllers, all for my own use (home irrigation controller, entertainment system controller, thermostats, etc). i'd really be interested in building such a bike interface myself. however, of course i lack enough knowledge of the bike's design, and the communication system/protocols. not sure where to look to learn.
Electric Cowboy
Thank you for the information. I've done many a CAN and 232 (actually K-Line but the handler is the same for 232) preprogramming interfaces. My interest was in the bike's control structure; that is, what elements reside on which boards and such. Apparently Zero is supporting access to some of these values via smartphone applications and blue tooth for the MY13s so I will probably wait a few months for the new bike to show up and not muck with my MY12.
Mine was more a curiosity about how Zero is managing the motor and pack. I thought I read on another thread that current inrush for acceleration was managed by the "ECU" which I assumed was the CAN reflashable normal ICE motorcycle looking bit under the seat. I got the impression that the speed controller CAN based flashing was either passed through the "ECU" or was simply another node on the CAN bus (along with the "ECU"). Do you have any description on the command set for 232 based altering of the MBB?
I love to read about your exploits (along with those of Doctorbass) and am willing to chip in on the design side if it would be of any help. The benifit of being retired is that I have a lot of spare time.
This is for 2011 models only. and yes that would be the case for a 2011 model
Where do you live?