Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Doctorbass]

The communication between diverse parts of the zero electrical system is done with CanBus protocol.

I just wonder if someone ever tried to communicate  and get some data from the zero system like the battery or dashboard or other with these CAN to USB adaptor... or even the OBDII adaptor ?

 

[BSDThw]

I did some reading at the 2012.

The CAN is on the OBDII plug.

And I can see what the SevCon send over "OpenCAN". I belive that the SevCon don't receive data.

The communication to the SevCon is done with the I/Os.

I have no idea if other components talk over the CAN.


 

[Electric Cowboy]

The sevcon can receive commands via the ODB port.

[BSDThw]

The sevcon can receive commands via the ODB port.

What do you mean?

For sure the SevCon can receive commands via OBD II if not you couldn't program it

just a joke:

I can see all the (T)PDOs => regularly send from SevCon to the bus, but in my SevCon setting all (R)PDOs are unused, so it will not receive data through the RPDO mechanism.
I even see to COB-IDs [104 and 204] not coming from the SevCon.

Do you let us know how / what you communicate to the SevCon, so we don't die stupid.

[BSDThw]

Hi Cowboy,

did I offend you? sorry!

I am really interested if there is more data transfer between sevcon and MBB...
Do we talk of 2012 bikes? I do have no experience with 2011s.

What I can see: the MBB  only has the "forward" bit to manipulate, it looks really little because there are so much different ways to control the Sevcon. 
I would really like to know if someone has more information if the MBB can manipulate the Sevcon on the fly.
2013 models can change setting with the help of a smart phone so MBB has to reprogram (scary) the Sevcon or even manipulate it online. It illustrates there are much more possibilities as I can see.

[Electric Cowboy]

Lol! No, I just get very busy and don't check the forums some time.

[Electric Cowboy]

The 2012 mbb does not have the ability to do much to the sevcon.

The 2013 does not allow any scary reprogramming on the fly. You have to be stopped and the settings you can effect are limited in selection and range.

[BSDThw]

The 2012 mbb does not have the ability to do much to the sevcon.

is what I thought, but I am not unhappy so it will not interfere if you mod your controller

Today I accidentally run over this pic. I don't have a smart phone so if I would buy a 2013 my first upgrade would be a new phone

[BSDThw]

The 2012 mbb does not have the ability to do much to the sevcon.

We have been wrong, I trace the CAN data at the moment and the MBB would be able to do a lot! but it do only little; as much as I know.

If you trace the data you will see that the MBB use the SDO-Protocol to speak direct to the Sevcon. It's funny they first log in with password level 4 it's the highest you can reach only Secon-Techs have level 5. Additionally you will know the password now if you write own software it will be helpful!
Now they change Neutral Torque, Regen-brake torque and the Ramp up rate for both on the fly. I guess this is the most reason why we are not allow to change from SPORT to ECO vs during drive. (I/We never realized a problem but as a SW-engineer I would do the same)

The data flow!

ASCII Trace IXXAT MiniMon V3  Version: 1.1.1.3080                      Date: 13.02.2013                      Start time: 18:20:48                      Stop time: 18:21:20                      Overruns: 0                      Baudrate: 125 kbit/s                      Time   Identifier (hex)   Format   Flags   Data (hex)          00:16:23.47   601   Std      40 00 50 01 00 00 00 00          00:16:23.48   581   Std      4F 00 50 01 00 00 00 00          00:16:23.48   601   Std      2B 00 50 03 00 00 02 01         Set PWD-ID 00:16:23.49   581   Std      60 00 50 03 00 00 00 00          00:16:23.50   601   Std      2B 00 50 02 ** ** 02 01         Set Password (PWD) 00:16:23.51   581   Std      60 00 50 02 00 00 00 00         (I think PDW shouldn't be in the NET) 00:16:23.51   601   Std      40 00 50 01 00 00 00 00          00:16:23.52   581   Std      4F 00 50 01 04 00 00 00         We now have Level 4 ;=)                       00:16:23.52   601   Std      40 20 29 03 00 00 00 00         Maximum Torque applied when neutral braking 00:16:23.53   581   Std      4B 20 29 03 96 00 00 00         Actual value 150=15% 00:16:23.54   601   Std      2B 20 29 03 46 00 00 00         Set value 70 00:16:23.54   581   Std      60 20 29 03 00 00 00 00         respond 00:16:23.54   601   Std      40 20 29 03 00 00 00 00         read 00:16:23.55   581   Std      4B 20 29 03 46 00 00 00         Actual value 70 = 7%                       00:16:23.55   601   Std      40 00 50 01 00 00 00 00          00:16:23.56   581   Std      4F 00 50 01 04 00 00 00         we still have PWD level 4 00:16:23.56   601   Std      40 20 29 09 00 00 00 00         Ramp up rate during direction change braking 00:16:23.57   581   Std      4B 20 29 09 DC 05 00 00         Actual value 1500 00:16:23.57   601   Std      2B 20 29 09 F4 01 00 00         Set value 500 00:16:23.58   581   Std      60 20 29 09 00 00 00 00         respond 00:16:23.58   601   Std      40 20 29 09 00 00 00 00         read 00:16:23.59   581   Std      4B 20 29 09 F4 01 00 00         Actual value 500                       00:16:23.59   601   Std      40 00 50 01 00 00 00 00          00:16:23.60   581   Std      4F 00 50 01 04 00 00 00         we still have PWD level 4 00:16:23.60   601   Std      40 20 29 04 00 00 00 00         Maximum Torque applied when footbraking 00:16:23.61   581   Std      4B 20 29 04 FA 00 00 00         Actual value 250=25% 00:16:23.61   601   Std      2B 20 29 04 96 00 00 00         Set value 150 00:16:23.62   581   Std      60 20 29 04 00 00 00 00         respond 00:16:23.62   601   Std      40 20 29 04 00 00 00 00         read 00:16:23.63   581   Std      4B 20 29 04 96 00 00 00         Actual value 150=15%

Why is it done?

The Sevcon has a so called "Traction baseline profile" for the default and highest set of values (2920 h).
and two "Drivability select 1 and 2 profiles [2921h and 2922h].

I don't know why but Zero use the baseline for SPORT and drivability 1 for ECO.

The problem is ECO will use higher neutral and brake torque so they couldn't set it in drivability 1 because baseline will limit this.
A smart but tough way was this on the fly reprogramming.

Actually they could write the highest values in the baseline and use  drivability 1 for SPORT and drivability 2 for ECO. Maybe I overlooked some thing but if not, they could have saved lot of developing time. (but what they did is cool stuff )

Why does I play with this?

I intend to use all three modes because since your "glitch up date" there is a parameter that allows the drivabilities to override the basline  but now the MBB will interfere 
I will use ECO and  SPORT wit normal neutral braking 7% and a second SPORT with neutral braking 0%!

 

[trikester]

Well at least we don't have a problem with 2013 models, according to Zero engineering. We can switch back and forth, on the fly, as much as we desire now. My handlebar mounted momentary switch gets a a lot of use.

They did really tell me that they worked with Sevcon to eliminate this problem, so I have no idea how the 1013 Sevcons and Zero's MMBs may differ from 2012's

Trikester

[eyeinsky]

will this work on my 2011 Canbus to connect to the MBB protocol?



 http://www.ebay.com/itm/USB-VW-Audi-Interface-Scan-Tool-Code-Reader-Cable-VCDS-409-1-FT232BL-OBD2-OBDII-/360696314165?pt=Motors_Automotive_Tools&hash=item53fb2cf935

[mentalvmaxrider]

Hi. I can switch modes on my 2012 xu on the fly...any idea why?