ElectricMotorcycleForum.com
Makes And Models => Zero Motorcycles Forum | 2013+ => Topic started by: evtricity on January 15, 2015, 04:39:37 PM
-
For those who want to access more information about your Zero, in particular the Main Bike Board configuration one way to do this is to make a USB to OBD II cable. This will allow you to access more diagnostic information including logs, status and error codes. With the right access, it's possible to change things such as your speedometer calibration (this is where adjustments for the front/rear sprockets and tyre circumference are made on recent models).
Here are the parts and steps to create the cable:
Parts:
- USB to TTL cable (see photo below) with 5V (red), ground (black), tx (green) and rx (white) wires
- OBD II male plug (see photo below)
Steps:
1. Cut the connectors off the end of the green, white and black wires to expose bare wires.
2. Solder the wires to the pins on the OBDII connector as follows:
- black wire to pin 5
- white wire (RX) to pin 8
- green wire (TX) to pin 9
- red wire is not connected (+5V)
3. Plug cable in to Windows laptop and device should be recognised and driver installed successfully
4. Take note of COM port used
5. Connect cable to OBD port on bike (above the motor on Zero SR/DS/S not sure where on FX)
6. Turn on bike
7. Open Putty terminal program (freeware) and use Serial connection to connect to COM port (eg COM4) and set baud rate to 38200
8. Open connection and MBB prompt should be displayed (hit enter key if not)
9. Type help and hit enter to get a list of commands that you can run (see photos)
-
Cheers for posting this info!
-
I thought the "vehicle speed calculation" / "distance calculation" was in the Sevcon settings? Is there a second one on the ODBII? Which models does this effect?
There are two fields if I recall in DVT which show revolutions per mile or something like that accept I think it might be in kilometers by default. I don't yet have my diginow ODBII connector yet -_- so I cannot check myself.
-
super many thank for this information, i will try as soon as possible
-
So where is the OBDII connector on the Zero?
-
The OBD II port is above the motor on the SR, DS and S models, next to the fast charge port.
-
Hi there,
I would like to change the speedometer calibration, because i ride 104KPH when my speedo shows 120. This is because I ride a 11cleat sprocket instead of the stock 12 cleats.... Anybody here who can give me the login to change data in the MBB?
best regards,
Christian
-
I know the log in for the 2012 is something like "1.21gigwatts" but I think they changed it for 2013 onwards, I don't know what that password is.
-
There are 3 password levels but the mentioned one will help you for the lowest level. (also for 2013...)
As much as I remember it will not allow you to change settings you need level 2 or 3 :-X
-
I have found informations about the FX speedo on my 2013 FX to calibrate the shown speed.
By pressing both buttons of the speedo for a few seconds it switches over into a kind of setup-mode.
(https://lh4.googleusercontent.com/Au1ZugfE3UIgYiO0X9xT9INFHBvM-0Hn_ai4DapQDw=s192-p-no)
Here I changed to 336-00. Now I have the correct speed displayed on the speedo. I compared it to the speed shwon on my GPS.
What I don´t know is, whats about the -00 behind the first number? (The first 3 of the number 336 was blinking, that´s the reason why it is not shown here)
And what´s about this screen here? Does anybody know this next page of the speedo?
(https://lh4.googleusercontent.com/-9SXddwJXdY8/VLp26TvEYyI/AAAAAAAAAHE/YP6wuXi3n_o/s284-p/speedo1.jpg)
The third page shows the digits "Li-5", which is the DIM function for the speedo. It can be changed to a lower number, and the blue LED light will be darker.
If anybody has more information about the set-up menue, i would be happy to learn more about it.
Best regards,
Christian
-
dgh853 do you know the pass for higth level?
-
Ok I must be doing something wrong. I connected the wires from USB cable to ODBII pins and when I plug it in no driver is recognized or installed.
Did you have to download a driver from somewhere and if so which?
Plugging it up to the bike then the computer didn't help either.
-
The driver should install when you plug the cable into the PC, before you even connect it to the bike. In fact it should recognise it before you even wire it to the OBD II plug as the chip is in the USB end of the cable. Did you cut the end off a regular USB cable or use one with the bare cables on one end? A standard USB cable doesn't have the right wire combination and chip at the PC end.
-
http://www.amazon.com/PL2303HX-RS232-Cable-Module-Converter/dp/B008AGDTA4/ref=sr_1_1?s=electronics&ie=UTF8&qid=1423452283&sr=1-1&keywords=PL2303HX+USB+To+TTL+To+UART+RS232+COM+Cable+Module+Converter (http://www.amazon.com/PL2303HX-RS232-Cable-Module-Converter/dp/B008AGDTA4/ref=sr_1_1?s=electronics&ie=UTF8&qid=1423452283&sr=1-1&keywords=PL2303HX+USB+To+TTL+To+UART+RS232+COM+Cable+Module+Converter)
This is the USB cable I ordered. I only cut off excess length from the cable, it still has about 6" of the USB cable which goes to about 15" of a OBDII cable for the colors / pins specified. I didn't try to connect it before soldering it up.
UPDATE:
Just started to read the reviews and found there were some counterfit chips recently. That lead me to the manufactures website here : http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41%E2%80%8E (http://www.prolific.com.tw/US/ShowProduct.aspx?p_id=225&pcid=41%E2%80%8E) which lead me to the driver I needed with instructions on how to check to make sure the chip is valid.
Go figure right? Going to go plug it up to the bike now ;)
UPDATE 2:
Black putty screen :/ Enter doesn't work to bring up MBB. I use putty at work daily so I don't think it is user error ;) Will have to revisit it another night, need sleep for work tomorrow :D I tried it at 9600 (since if I went to device manager it had the baud set to that stock) and modified it there as well to 38400 ... will play with it more later.
-
Baud rate needs to be 38200
-
38200 was the first thing I tried. However that isn't a default baud rate option (see attached)
If you go to device manager and open the device you can find that screen.
-
Can someone who has got their USB : ODBII to work provide a similar screenshot to the one I did on the previous post? Also which driver is your USB using.
Don't want to take apart something I am near certain I wired correctly before confirming the screen options are identical. My cable still isn't working correctly :/
Go to Device manager > find the USB in COM# being used for the ODBII > go to tab in image and check bits per second
-
here is the setting i used
-
Burton, I have the same setup in my Device Manager as per your screenshot. I only set the baud rate to 38200 when I connect using putty.
-
Lovely ... so now I have to take the cable apart :/
Let me see if I can find a way to check the pinout of the USB to the ODBII pinout to see if it is connected right. I really don't want to have to cut through three layers of heat shrink to find out it is wired right and something else is wrong lol
Thanks for the info guys.
-
Ok, for those who are wondering the best way to check your pinout on a usb ... take it apart (picture included)
Seriously. You cannot check the center pins at all less you do this. And when you test you test from where the wires come into the PCB not where the pins com in to the PCB.
My high / low are switched for some reason. >__<
So to fix it I am going to unsolder from the board and swap the wires since it is more trouble to strip down the wires at the connection to the OBDII connector.
UPDATE: was able to log in and started to dump logs then it stopped. Seemed all USB ports don't work now 0_0 restarting my laptop to hope they come back lol
UPDATE 2: restart worked to get ports functional again. Upon trying the dump all command the computer blue screened after a while and crashed >__< Tried another port on usb 2.0 and it locked up the ports just after pressing enter to get prompt. Restarting now for the fifth time ...
-
Update, the buad rate works at 38400, and since it is a stock buad rate that is what I am going to use.
Every time I do a dumpall or eventlogdump after about 30 seconds the terminal stops receiving text and the computer will blue screen. My computer never blue screens and hasn't since I have had it for the last 3 years.
I don't have another machine to test this with sadly. I might pick up a cheap laptop and install Linux on it to see if that fixes it. Wonder if I started up a VM Linux machine and tried that .... hmm.
-
I´d rather would try it with a different USB to Serial converter. Maybe the driver isnt´t very compatible to your Windows version. What´s the name of the IC on the little USB-PCB? Is it something with FT232?
If yes, you could get the drivers here: http://www.ftdichip.com/Drivers/VCP.htm (http://www.ftdichip.com/Drivers/VCP.htm)
regards, Chris.
-
It is a prolific 2303 as far as I can tell. http://www.amazon.com/gp/product/B008AGDTA4/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1 (http://www.amazon.com/gp/product/B008AGDTA4/ref=oh_aui_detailpage_o03_s00?ie=UTF8&psc=1)
The drivers installed are current. Anyone else using the prolific chipset?
System Requirement:
. USB 1.1/2.0/3.0 Host Controller
. Device using PL2303HX/X/EA/RA/SA/TA/TB version chips
. PL-2303 Windows Driver Installer v1.8.0 or above
. Supports the following Windows OS Family:
- Windows XP SP2 and above (32 & 64 bit)
- Windows Vista (32 & 64 bit)
- Windows 7 (32 & 64 bit)
- Windows 8/8.1 (32 & 64 bit)
NOTE:
- Windows 8 is NOT supported in HXA/XA chip versions (will show yellow mark Error Code 10).
- Windows 8 is supported only in following chip versions:
- PL2303HXD (HX Rev D)
- PL2303EA (ESD protection)
- PL2303RA (Built-in transceiver)
- PL2303SA (SOP8 package)
- PL2303TA (PL2303HXA/XA replacement)
- PL2303TB (12 GPIO)
Supported device ID and product strings:
. VID_067B&PID_2303 for "Prolific USB-to-Serial Comm Port"
. VID_067B&PID_2304 for "Prolific USB-to-Serial Comm Port" (PL2303TB chip)
. Other VID/PID based on PL2303 chip.
-
Check to see if you are using FDTI drivers, myself I'd be VERY hesitant about using FDTI drivers with non FDTI chips, they have already proven that they cannot be trusted after their deliberate "bricking" incident last year.
-
I have two OBDII connectors that I use for my cars. One is bluetooth that connects to the " Torque APP " on my phone.
The other has a USB end that I use with my laptop. Would the on with factory USB work on the Zeros, or, do I have
to " build " one similar to photos above? I have a 2013 FX, and, a 2012 XU that I would like to look into.
Thanks
Ed
-
Zero uses an uncommon pin layout for accessing the MBB as detailed earlier in this topic. You can try it out and you might be lucky but I suspect it won't match the Zero OBD pin configuration.
-
Thanks for the quick reply. I must have missed the mention of Zero pin difference.
Is there a particular version of PUTTY to be used, or, would the most recent work.
I thought I read in a different thread about using an older version of software. Not
sure if it was for the same purpose.
Thanks again.
Ed
-
Current version of putty works ok for accessing MBB
-
First, thank you for posting on how to assemble a cable to connect OBD-II to a computer and access the onboard management tool via serial console.
Second, please see this re: bitrates
http://www.tldp.org/HOWTO/Modem-HOWTO-23.html (http://www.tldp.org/HOWTO/Modem-HOWTO-23.html)
-
Posting a follow up on this to confirm that this pinout described by evtricity worked for me.
My USB to TTL cable looked like his did, and the color of the wires matched up (unlike Burton's experience).
I'm also providing links to the exact items I bought to make mine:
USB to TTL Cable (http://www.amazon.com/gp/product/B008AGDTA4?psc=1&redirect=true&ref_=oh_aui_detailpage_o09_s00)
OBD2 Connector (http://smile.amazon.com/gp/product/B00MWRIQV4?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00)
The OBD2 Connector might not be the ideal one (not all of the pins are connected to plated-through-holes that you can attach wires to), but, by soldering the wires directly to the backs of the pins, it worked. The strain relief is good enough that I feel OK with that approach.
I do wish the cable was longer. As it is, you're sitting on the floor by the back wheel, laptop on your lap, or you're perching it on the seat, hoping it doesn't fall.
Here are the parts and steps to create the cable:
Parts:
- USB to TTL cable (see photo below) with 5V (red), ground (black), tx (green) and rx (white) wires
- OBD II male plug (see photo below)
Steps:
1. Cut the connectors off the end of the green, white and black wires to expose bare wires.
2. Solder the wires to the pins on the OBDII connector as follows:
- black wire to pin 5
- white wire (RX) to pin 8
- green wire (TX) to pin 9
- red wire is not connected (+5V)
3. Plug cable in to Windows laptop and device should be recognised and driver installed successfully
4. Take note of COM port used
5. Connect cable to OBD port on bike (above the motor on Zero SR/DS/S not sure where on FX)
6. Turn on bike
7. Open Putty terminal program (freeware) and use Serial connection to connect to COM port (eg COM4) and set baud rate to 38200
8. Open connection and MBB prompt should be displayed (hit enter key if not)
9. Type help and hit enter to get a list of commands that you can run (see photos)
-
I broke down and purchased one of EC's diginow reaper dongles yesterday to avoid needing to use a laptop all together if desired. I will plug it in, tape it down to seal it better, and leave it there.
No more removing my "rain coat" which I tucked into the tank area (which is where my birds nest is) to access the ODBII connector :D
The funny part is I own EC's former race bike and it has this huge diginow sticker on it but I didn't own one lol Now when someone asks (which has yet to happen) I can pull out my ipad and be like "this is what it is."
-
I've wikified this now with at least the baud rate correction: http://zeromanual.com/index.php/Unofficial_Service_Manual#Diagnostics (http://zeromanual.com/index.php/Unofficial_Service_Manual#Diagnostics)
-
There are 3 password levels but the mentioned one will help you for the lowest level. (also for 2013...)
As much as I remember it will not allow you to change settings you need level 2 or 3 :-X
Hi Guys
Any progress in getting the passwords?
Thanks in advance :-)
-
I've been working on improving the python log parsing software and could use some example decoded data. A set of files with both decoded text from the serial link and .bin files from the app on the same bike would be a great help in deciphering the binary files. I'm just starting with parsing the BMS logs. What data does the BMS command produce? Can you get a BMS log dump? Has anyone even tried communicating directly with the BMS?
-
Hi Guys
Any progress in getting the passwords?
Thanks in advance :-)
Maybe this post is about the DigiNow data reaper passwords or I don't know it could be the MBB: http://electricmotorcycleforum.com/boards/index.php?topic=6587.msg52354#msg52354 (http://electricmotorcycleforum.com/boards/index.php?topic=6587.msg52354#msg52354)
-
There are 3 password levels but the mentioned one will help you for the lowest level. (also for 2013...)
As much as I remember it will not allow you to change settings you need level 2 or 3 :-X
Hi Guys
Any progress in getting the passwords?
Thanks in advance :-)
It seems that you've been living two lives ______________ One life, you're Thomas A. Anderson, program writer for a respectable software company. You have a social security number, pay your taxes, and you... help your landlady carry out her garbage. The other life is lived in computers, where you go by the hacker alias "Neo" and are guilty of virtually every computer crime we have a law for. One of these lives has a future, and one of them does not.
(Not sure if the clue above still applies to the latest bikes though)
-
Hi Guys
Any progress in getting the passwords?
Thanks in advance :-)
Maybe this post is about the DigiNow data reaper passwords or I don't know it could be the MBB: http://electricmotorcycleforum.com/boards/index.php?topic=6587.msg52354#msg52354 (http://electricmotorcycleforum.com/boards/index.php?topic=6587.msg52354#msg52354)
Those are Bluetooth pairing codes for the dongles.
Inquire privately for Zero login passwords. (I wish we had a better method.)
-
I've been working on improving the python log parsing software and could use some example decoded data. A set of files with both decoded text from the serial link and .bin files from the app on the same bike would be a great help in deciphering the binary files. I'm just starting with parsing the BMS logs. What data does the BMS command produce? Can you get a BMS log dump? Has anyone even tried communicating directly with the BMS?
Log dumps when connected via OBD-II do produce these. Not sure when my next opportunity for this is.
-
could communicate using the described USB-serial-OBD2 cable assembly.
Putty never wanted to open a communication window. Used Teraterm instead of. 38400-N-8-1-no-no very classical setting.
here is the BMS dump
-
update
by the way, I never could get the BMS data throught app, only the MBB log.
The 1st level login uses PW "1.21gigawatts" and mainly enables setting of the "custom" torque/speed/regen parameters. Luckily, since on some Zeros this setting is not possible through the app. However, the figures are strange, e.g., regen 15% means 100%, or regen 10% means 66%. and the torque setting is somehow strange as well. Finally the max speed setting works fine but only in mph, which is not a great deal calculating for the non-anglo-saxons...
I would like to know higher level logins, especially thoses enabling speed calibration (currently the speed and distance indication is 5% excessive), and very basically, adjusting the onboard real time clock, which is not related to the clock display on the dash and currently 10 min ahead.
-
I finally got my cable connected and working. I had a lot of trouble, got the laptop part working, tried every serial setting there is (!), connected RX and TX together and got echo but no MBB prompt, ever. Then I happened to look inside the USB connector and found the problem. The cable ground wire was cold soldered by the factory and had come loose, no ground to the bike means no data transfer.
Now I know more of the MBB log parser unknowns since I can compare my app logs to the MBB bike event dump. Here they are:
0x31 0x00 0xb2 0x0c 0x3a ???
BMS Isolation Fault BMS: 0
0x31 0x01 0xb2 0x22 0x2c ???
BMS Isolation Fault BMS: 1
0x02 0x20 0x03 0xb2 0x46 0xfd ???
High Throttle Disable. thr = 800 mV
There are still some mysteries there, some of the hex is not decoded fully by the MBB, but this is progress and will make the parser software better when I find the time to update it. Again, I ask for any other examples of app log and cable log pairs so that other unknowns can be identified. There are seven more MBB known-unknowns, possibly more unknown-unknowns. BMS codes are all known unless more are discovered. Search parsed log files for "???" to find unknown entries.
https://github.com/zero-motorcycle-community/zero-log-parser/blob/master/log_structure.md
-
So three consecutive question marks turn into this ??? Huh!!! Probably someway to prevent that but what I meant was "? ? ?" with no spaces.
-
I've edited your post and added 'code' '/code' bbcode tags around that block, as an example you can edit your post to see how to do this. Sorry about the forum software clobbering your data.
-
I finally got my cable connected and working. I had a lot of trouble, got the laptop part working, tried every serial setting there is (!), connected RX and TX together and got echo but no MBB prompt, ever. Then I happened to look inside the USB connector and found the problem. The cable ground wire was cold soldered by the factory and had come loose, no ground to the bike means no data transfer.
Now I know more of the MBB log parser unknowns since I can compare my app logs to the MBB bike event dump. Here they are:
0x31 0x00 0xb2 0x0c 0x3a ???
BMS Isolation Fault BMS: 0
0x31 0x01 0xb2 0x22 0x2c ???
BMS Isolation Fault BMS: 1
0x02 0x20 0x03 0xb2 0x46 0xfd ???
High Throttle Disable. thr = 800 mV
There are still some mysteries there, some of the hex is not decoded fully by the MBB, but this is progress and will make the parser software better when I find the time to update it. Again, I ask for any other examples of app log and cable log pairs so that other unknowns can be identified. There are seven more MBB known-unknowns, possibly more unknown-unknowns. BMS codes are all known unless more are discovered. Search parsed log files for "???" to find unknown entries.
https://github.com/zero-motorcycle-community/zero-log-parser/blob/master/log_structure.md
That's great! I saw the code change just yesterday. For some reason, it was not clear enough to me how decoding progress was made, but this clarifies it a bit. In the worst case, one can always send trouble logs to Zero and ask to see the decoded result for an explanation and comparison.
-
The browser parser uses three question marks to flag unparsed (hex converted) log entries in the binary file from the Zero app that are of unknown types. Since the serial cable event log dump is fully decoded text, it is possible to compare entries with matching timestamps from the parsed binary log text and the serial cable log dump. This is how I found the previously unknown entry types. I search the parsed text for unknown entries and then find matching entries from the serial log. There is a time zone correction needed, three hours in my case between local parsed timestamps and factory time zone log entries. The surrounding entries before and after the unknown one confirm the match.
From cable
06591 06/16/2017 17:34:46 Charging PackTemp: h 31C, l 30C, AmbTemp: 40C, PackSOC: 14%, Vpack: 98.951V, BattAmps: -2, Mods: 11, MbbChgEn: Yes, BmsChgEn: No
06592 06/16/2017 17:36:04 BMS Isolation Fault BMS: 0
06593 06/16/2017 17:37:33 BMS Isolation Fault BMS: 1
06594 06/16/2017 17:44:42 Low Chassis Isolation 22 KOhms to cell 1
From Browser parse
08290 06/16/2017 20:34:46 Charging PackTemp: h 31C, l 30C, AmbTemp: 40C, PackSOC: 14%, Vpack: 98.951V, BattAmps: -2, Mods: 11, MbbChgEn: Yes, BmsChgEn: No
08291 06/16/2017 20:36:04 0x31 0x00 0xb2 0x08 0x31 ???
08292 06/16/2017 20:37:33 0x31 0x01 0xb2 0x0c 0x3a ???
08293 06/16/2017 20:44:42 Low Chassis Isolation 22 KOhms to cell 1
-
I got my ODB II plug today (my ttl cable arrived last week) I plugged my ttl cabe into my mac book and found it was the same chip as Burtons cable, but I decided to solder it up and see if it worked. I had to find a serial terminal program first, I found one called Serial (for mac) not free, opted for the 7 day trial. I could only select a baud rate from a list (38400) not 38200 as on the first page. I pressed enter and it worked first go with no problems. The software requires no drivers as it has them built in and its sell point was that it would work with anything. Well they were right!
Many thanks for this post, it will be a great help now that Zero have pulled out of Australia.
-
38200 was a typo. Glad it's working!
-
> ... I had to find a serial terminal program first, I found one called Serial (for mac) not free, op ...
Did you see the Diginow Serial Terminal in the Google Chrome Browser store?
-
> ... I had to find a serial terminal program first, I found one called Serial (for mac) not free, op ...
Did you see the Diginow Serial Terminal in the Google Chrome Browser store?
Hmm obviously not.
-
> ... I had to find a serial terminal program first, I found one called Serial (for mac) not free, op ...
Did you see the Diginow Serial Terminal in the Google Chrome Browser store?
Hmm obviously not.
Just tried it, doesn't work, keeps closing the tab I run it in.
The chip in the USB cable is from Prolific (product ID 0x2303), Burton had trouble with this chip as well, and with my Arduino playing it seems the Chinese serial to USB emulation chips require their own special drivers (and there is more than one, and not much documentation on the drivers). As I said, that was this products claim to fame, that it would work with any chip set (no need to hunt for special drivers).
-
For those who want to access more information about your Zero, in particular the Main Bike Board configuration one way to do this is to make a USB to OBD II cable. This will allow you to access more diagnostic information including logs, status and error codes. With the right access, it's possible to change things such as your speedometer calibration (this is where adjustments for the front/rear sprockets and tyre circumference are made on recent models).
Here are the parts and steps to create the cable:
Parts:
- USB to TTL cable (see photo below) with 5V (red), ground (black), tx (green) and rx (white) wires
- OBD II male plug (see photo below)
Steps:
1. Cut the connectors off the end of the green, white and black wires to expose bare wires.
2. Solder the wires to the pins on the OBDII connector as follows:
- black wire to pin 5
- white wire (RX) to pin 8
- green wire (TX) to pin 9
- red wire is not connected (+5V)
3. Plug cable in to Windows laptop and device should be recognised and driver installed successfully
4. Take note of COM port used
5. Connect cable to OBD port on bike (above the motor on Zero SR/DS/S not sure where on FX)
6. Turn on bike
7. Open Putty terminal program (freeware) and use Serial connection to connect to COM port (eg COM4) and set baud rate to 38200
8. Open connection and MBB prompt should be displayed (hit enter key if not)
9. Type help and hit enter to get a list of commands that you can run (see photos)
Hello All!
I've made the cable, but I have a doubt. Is it necessary to supply 12V current at pin 16 of the ODBII plug? My cable does not work and I think that may be it.
Thank you.
-
Does a serial device appear?
On Linux I would look in /dev/ for ttyUSB0 or maybe ttyACM0 , not sure what it would be on Mac
-
No need for supply voltage, just connect ground, rx and tx. Try switching rx and tx. I had a broken ground wire in my cable.
-
You can use screen on almost all unixes. On Mac's, serial adapters have a plethora of names (ttyS0, ttyUSB0 etc) so the easiest is to make a list of devices in the /dev folder, then plug in the device, and then see what device has been added. You can do this for example like this:
ls /dev > /tmp/devices
<plug in device>
ls /dev > /tmp/plugged
diff /tmp/devices /tmp/plugged
The output should show you which device was added to the list. Then, a simple
screen /dev/<found device> 9600
should give you a serial console. You can exit screen by typing <ctrl>-a followed by \
-
Guys, about commands (prompt in putty) can I modify or change some parameter or it just read only?
-
The different levels of login grant different scopes of settings that can be seen and changed.
It’s advisable not to login at a higher level than you need, to avoid accidentally invoking unsafe changes.
-
Thanks for your answer. The login level is it the same for all bike or change with the years? If I ask for my SR 2018, where I can find all access password information? I found some thing here but not realy complet I think.
I desir to change the custom lower limit speed to lowers if is possible.
The different levels of login grant different scopes of settings that can be seen and changed.
It’s advisable not to login at a higher level than you need, to avoid accidentally invoking unsafe changes.
-
AFAIK the login levels have not changed since 2013 though I have heard murmurs about newer passwords which I have no way to verify and cannot get any clear information on.
I do know that these passwords should not be published for a host of reasons, and the whisper network is full of noise I constantly have to sift through and crosscheck.
There’s no harm in trying passwords like that. Reprogramming modes and limits may only require a level 2 password.
-
I'm sure somebody have this informations here! 8)
For now I found some good informations, mainly the eventlogdump. I saw interesting things, When my bike is born, riding etc, All is logged! ;)