ElectricMotorcycleForum.com

when you charge at home with 220v you use only one phase and one charger, with 3 phase charge station you use 2 phases and 2 x 3kw chargers.
now to understand where is the problem ... is not easy, maybe the charge station have problems on the second phase and charger disconnect until voltage is stable.. but if you find the same problem on all charge stations i think the problem is on the bike. 
my suggestion is to remove cables from second chargers, check connectors humidity and apply dielectric sillicon grease if is required... maybe is only oxidation problem.
regards
Artur

After the previous posts i made some tests to verify max speed, since is the easiest parameter to verify without a dynometer..
i lifted rear wheel and adjusted riding modes, in this way wind and road do not affect results, and i made a video to see rpm and max speed on dash

results:
TWlua2lvbmUAALx46AOo/eD8AQCCHAUUUAAAAAAA - custom mode 124mph (speed limiter slider at max)
rpm limiter set to 7298
max rpm on dash 7794
max speed on dash 198 km/h

TWlua2lvbmUAALx46AOo/eD8AQBIHAUUUAAAAAAA - custom mode 123mph
set rpm 7240 
measured rpm 7730
max speed 196 km/h

TWlua2lvbmUAALx46AOo/eD8AQAMHAUUUAAAAAAA - custom mode 122mph
set rpm 7180
measured rpm 7681
max speed 195 km/h

U1BPUlQAAAAAAAHI6APo/uj+AQBMHQMBMgAAAAAA - sport mode
set rpm 7500
measured rpm 8034 
max speed 207km/h

so, bike add +500 to the rpm limiter set in driving modes and that's it... sport mode definitively have higher rpm.

about max power...
no idea about 200 vs 120 values.. and no idea if MBB reduce power or not..
for this test a dynometer is required.

yes, zero console is not standard,
you can use this small program i made to interface it
https://drive.google.com/file/d/1xFppbBsfCtPkoJzsk0wwxbPf_gVOVHPW/view?usp=sharing

 "open" the FTDI com port connected to the bike and type the comand or select the tab with pre-coded commands to show data.

I have the same problem, SR/F MY2020 MBB27 MBS21 latest android app, but i think it's not relevant since you can check online data with zengo apps or browser

disconnect 12v battery, my ccm will work until you ride the bike, than it will die until the next 12v power disconnection.
there is a service recall
https://dot.report/bulletins/10216888
but dealer report is only for usa bikes....
anyway my ccm  is fw_ver,  2020.4.16, you can read with diagnostic serial cable.

I just spent several months getting a new CCM fitted (under warranty).  It had to be coded to the bike which unfortunately the first that Zero sent out was not.  But after successful replacement it updates the Cloud status fine, but after the bike is keyed off for a couple of hours (next CCM update basically) then the SOC goes to 0%.  Key the bike on and leave for an update to occur and it is correct again.
It feels as though this is an issue with the new CCM sending back the wrong status when the bike is off.  But the dealer is stating this is a known issue with the App (Zero NextGen app that is). 
Anyone else with any further info on this issue?  I can't help but feel it's a simple config problem.   

my ccm is faulty from the beginning ( february ) and i have open a ticket to my dealer, and i call it every week for status... but at today nothing.
my current ccm have 2 problems, it never report soc % and charge status to the server,
but the worst problem is that after a server position update ( with bike in motion) it hang, simply ccm go to low power mode and never wakeup, to fix this you need to disconnect 12v battery.
if bike is stationary it update server position without issues every time you turn on key.

running a canbus trace on the communication lines, the bike send soc % and fw ver to the ccm every sec, and ccm send back the info you see in the diagnostic.
as soon it hang it disconnect from bus and all the data transmitted from mbb is not captured.

i have also found canbus messages (id253) with soc 0% sent to the ccm  at key on, this is likely the cause of the bad soc% reported to the server (if ccm update the server with this value)...and i think it will be addressed by a new MBB firmware soon or later... (i'm running MBB v24)

p.s you can check the real data sent from ccm to the server with the following info https://www.electricmotorcycleforum.com/boards/index.php?topic=9520.0
cause app can be bugged too

Hello!
i own a sr/f 2020 premium,
application update on android worked ok but app crashed, so i had to delete the app and reinstall it from playstore because of cache bugs.
firmware update to MBB v24 and BMS v20 worked properly, only takes a lot of time at 100% waiting the complete message...don't panic!
i didn't test yet the max speed problem on riding modes, but i noticed a strong reduction of regenerative brake,
my custom mode have regen at 100% and usually i don't need to use brakes... after the update i have to brake... any one noticed the same?