Anyone here actually comfortable betting on a small two-wheeler OEM’s black-box battery and cloud stack for 5-7 years? I’m looking at Jitendra and a few peers, and I’m struggling with how casual we’ve become about “it’ll be fixed in an OTA” and “AIS-156 certified, trust us.” That’s not a plan; that’s hope. If you own a Jitendra e-bike/e-scooter (or maintain a fleet), can we cut through brochures and share raw, verifiable specifics? I’m not interested in marketing screenshots or range-at-25-km/h fairy tales. I’m after hard data and serviceability facts that determine whether these bikes survive monsoon, heat, and corporate turbulence. What I want to know, specifically: Battery and BMS Exact pack capacity in Wh (from a full-to-empty discharge log), nominal pack voltage, cell chemistry (NMC vs LFP). Cell vendor and format (e.g., 21700 from which manufacturer), BMS make/model, fuse and main contactor specs. Thermal strategy: any temperature derating curves published? Maximum pack temp you’ve seen in 40°C ambient and sustained climbs. AIS-156 Phase II: which test lab, report number, and what was the nail-penetration/thermal propagation result? Any venting/degassing path visible on the pack? Connector hardware: brand/series for charge and power connectors (TE/Amphenol or unbranded). Any melted housings or browned pins after a monsoon season? Telematics and firmware OTA cadence and changelogs. Has any update bricked or altered range/acceleration without consent? Diagnostics access: is there a documented CAN/UDS PID list? Can owners pull SOH, DCIR, fault codes without the cloud? What happens if the vendor’s servers go dark? Is there a fallback to start/ride/charge? Anyone tested offline operation for a week? Drivetrain and durability Hub vs mid-drive: unsprung mass issues, wheel bearing wear rates, water ingress in the motor after flood riding. Regen calibration: does aggressive regen cook rear bearings or glaze brake pads? Any ABS/combined braking weirdness in wet. Real-world Wh/km with a 90-110 kg system load at 35-40 km/h average, stop-go urban profile (share a GPS+voltage log if you can). After-sales and parts Availability and price of critical spares: BMS board, display, throttle, controller, brake calipers, wheel bearings, charger. Are parts tagged with generic standards (so we can cross-shop) or proprietary? Any firmware pairing that locks out third-party replacements? Warranty fine print: is SOH measured by a transparent method? Thresholds for pack replacement? Actual outcomes from claims? Weatherproofing reality check IP rating evidence: has anyone pressure-washed (not recommending, just reporting) and then opened up connectors to inspect for moisture? Drain paths in the frame/battery bay. Corrosion on busbars or frame welds after one monsoon. Safety events Any thermal events, smoke, or charger failures? Please include ambient temp, state of charge, and whether it was charging or parked. Here’s my bigger challenge to the status quo: We should stop accepting un-verifiable “compliance” statements. If an OEM won’t publish AIS-156 summary results and a service manual, that’s a red flag. Right-to-repair and right-to-data need to be baseline. Give owners: service mode access, pinouts, fault code dictionaries, and a way to extract SOH/DCIR without a subscription. Put firmware and encryption keys in escrow so the vehicle doesn’t die if the company does. Would Jitendra (or any small OEM) agree to that? If not, why are we still buying? Proposal for a community stress audit (I’ll help organize if others join): Heat soak: 20 km continuous climb or full-throttle run at 38-45°C, log pack temp, voltage sag, and derating behavior. Monsoon test: 30 minutes of heavy-rain riding, then 24-hour sit, then open select connectors/motor covers for ingress inspection. Range reality: 50 km city loop, 10 stops/km, 100 kg load, average 35-40 km/h, log Wh/km and SoC curve. Offline week: ride with backend disconnected; confirm start/charge/diagnostics still function. If you have a Jitendra, please post: Model/year and odometer Latest firmware versions (BMS, motor controller, dashboard) A 0-100% discharge log (voltage, current, temp) and any service invoices with part numbers If your experience has been flawless, that’s useful too-but let’s back it with numbers and artifacts. The market’s maturing; our standards should, too.

Quick datapoints from a small mixed fleet (2x Jitendra JMT 1000 HS MY2023 in Pune; 6 .8k km and 5 .1k km): Battery/BMS Pack label: 60 V NMC. Usable energy from full to LVC at 0 .6C: 2.45-2.6 kWh (Victron SmartShunt logs over multiple cycles). Peak pack temp seen: 48-50°C after a 15-18 km continuous climb at 37-40°C ambient; current limit/derate kicked in 50°C pack or when motor temp (internal NTC) crossed 110°C . No transparent AIS-156 Phase II report; only an ICAT sticker. Vendor refused to share summary-red flag. Charge connector on both bikes was a cheap “aviation” style; one browned pin after monsoon. Swapped to a sealed, branded connector; no repeats. Telematics/firmware OTA cadence 6 -10 weeks. One update quietly changed throttle/regen map; another bricked a dashboard, needed dealer reflash. No public PID list. CAN header present but undocumented; BMS data gated via their app. Pulled the SIM and blocked APN for 8 days: start/ride/charge worked; app dead, no immobilize. So at least basic operation survives a cloud outage. Drivetrain/durability Hub motor. Rear wheel bearings needed replacement once after deep-water days (we use 6202-2RS now + better grease). Regen is conservative; no bearing heat issues, but rear can step out on wet paint if you chop throttle mid-corner (no ABS coordination evident). Real-world consumption, 100 kg system, 35-40 km/h avg, stop-go: 29-34 Wh/km (city, mixed seasons). Heat and rain push it to the high end. After-sales/parts Controller, display, throttle: available. BMS not sold separately; pack-only swap policy. Controller appears paired-drop-in third-party controller throws faults without dealer tool. Warranty SOH judged by their tool; no DCIR number shown. A claim at 67% “app SOH” was denied. Weatherproofing IP claims not matched by reality: moisture found in two unsealed connectors post-pressure wash; dielectric grease + heat-shrink fixed it. Battery bay had poor drain; we added small weep holes to stop pooling. If we run the community audit, I’ll log with a SmartShunt + GPS and stick thermocouples on pack shell and controller. Also +1 to testing a full offline week with SIM removed and DNS blocked.

Good add. A few concrete next steps we can all run without OEM cooperation: Capacity and DCIR: Log a 0.5C-0.7C CC discharge to LVC for usable Wh. Then do a 10 s 1C pulse at 60 -70% SoC; DCIR ≈ ΔV/ΔI. Share ambient and pack temps. Sleep current: Measure key-off quiescent draw at the battery lead with a shunt; anything >2-3 mA will eat packs during storage. Offline survivability: Pull SIM and block DNS; confirm start/charge, horn/lights, and whether SoC/faults remain accessible via dash. Also test if immobilizer still works from the app when the bike later comes online. Water ingress sanity: After a heavy rain ride, megger the motor phase-to-housing at 500 V; aim >10 MΩ. If low, bake/dry and reseal grommets. Inspect connectors; upgrade to sealed families (TE Superseal 1.5 / Amphenol AT) and add a PTFE/Gore vent on battery shell if none is present. Connectors/heat: Stick temp dots on charger plug and inlet; >65-70°C at pins = resistance/oxidation. Photograph any browned terminals and note brand/series. Bearings/brakes: Note bearing codes pulled from wheels (e.g., 6202/6203 2RS). Share pad shape cross-refs so we can source generics. Check for regen-induced rear pad glazing after long descents. CAN access: Try 250/500 kbps with a CANable/SavvyCAN; look for periodic BMS frames (voltage/current/temp) and log IDs. Even a minimal DBC (V, I, T) helps replicate SOH/Wh without cloud. AIS-156 proof: Post the certification sticker photo (lab name-ARAI/ICAT/CIRT, report number). If anyone has a summary page, redact VIN and upload. Nail-penetration/thermal propagation result line is key. Charger safety: Measure earth leakage and case temperature after a 2-hour charge at 40°C ambient. Note if ELCB/RCCB trips. I can host a shared folder for raw CSVs (GPS, pack V/I/T, ambient) and photos of labels/connectors. Two comparable loops from different cities would already tell us if the stack is robust or just passing in fair weather.

Jitendra Electric Bike

ecotorque

Anyone here actually comfortable betting on a small two-wheeler OEM’s black-box battery and cloud stack for 5-7 years? I’m looking at Jitendra and a few peers, and I’m struggling with how casual we’ve become about “it’ll be fixed in an OTA” and “AIS-156 certified, trust us.” That’s not a plan; that’s hope.

If you own a Jitendra e-bike/e-scooter (or maintain a fleet), can we cut through brochures and share raw, verifiable specifics? I’m not interested in marketing screenshots or range-at-25-km/h fairy tales. I’m after hard data and serviceability facts that determine whether these bikes survive monsoon, heat, and corporate turbulence.

What I want to know, specifically:

Battery and BMS
- Exact pack capacity in Wh (from a full-to-empty discharge log), nominal pack voltage, cell chemistry (NMC vs LFP).
- Cell vendor and format (e.g., 21700 from which manufacturer), BMS make/model, fuse and main contactor specs.
- Thermal strategy: any temperature derating curves published? Maximum pack temp you’ve seen in 40°C ambient and sustained climbs.
- AIS-156 Phase II: which test lab, report number, and what was the nail-penetration/thermal propagation result? Any venting/degassing path visible on the pack?
- Connector hardware: brand/series for charge and power connectors (TE/Amphenol or unbranded). Any melted housings or browned pins after a monsoon season?
Telematics and firmware
- OTA cadence and changelogs. Has any update bricked or altered range/acceleration without consent?
- Diagnostics access: is there a documented CAN/UDS PID list? Can owners pull SOH, DCIR, fault codes without the cloud?
- What happens if the vendor’s servers go dark? Is there a fallback to start/ride/charge? Anyone tested offline operation for a week?
Drivetrain and durability
- Hub vs mid-drive: unsprung mass issues, wheel bearing wear rates, water ingress in the motor after flood riding.
- Regen calibration: does aggressive regen cook rear bearings or glaze brake pads? Any ABS/combined braking weirdness in wet.
- Real-world Wh/km with a 90-110 kg system load at 35-40 km/h average, stop-go urban profile (share a GPS+voltage log if you can).
After-sales and parts
- Availability and price of critical spares: BMS board, display, throttle, controller, brake calipers, wheel bearings, charger.
- Are parts tagged with generic standards (so we can cross-shop) or proprietary? Any firmware pairing that locks out third-party replacements?
- Warranty fine print: is SOH measured by a transparent method? Thresholds for pack replacement? Actual outcomes from claims?
Weatherproofing reality check
- IP rating evidence: has anyone pressure-washed (not recommending, just reporting) and then opened up connectors to inspect for moisture?
- Drain paths in the frame/battery bay. Corrosion on busbars or frame welds after one monsoon.
Safety events
- Any thermal events, smoke, or charger failures? Please include ambient temp, state of charge, and whether it was charging or parked.

Here’s my bigger challenge to the status quo:

We should stop accepting un-verifiable “compliance” statements. If an OEM won’t publish AIS-156 summary results and a service manual, that’s a red flag.
Right-to-repair and right-to-data need to be baseline. Give owners: service mode access, pinouts, fault code dictionaries, and a way to extract SOH/DCIR without a subscription.
Put firmware and encryption keys in escrow so the vehicle doesn’t die if the company does. Would Jitendra (or any small OEM) agree to that? If not, why are we still buying?

Proposal for a community stress audit (I’ll help organize if others join):

Heat soak: 20 km continuous climb or full-throttle run at 38-45°C, log pack temp, voltage sag, and derating behavior.
Monsoon test: 30 minutes of heavy-rain riding, then 24-hour sit, then open select connectors/motor covers for ingress inspection.
Range reality: 50 km city loop, 10 stops/km, 100 kg load, average 35-40 km/h, log Wh/km and SoC curve.
Offline week: ride with backend disconnected; confirm start/charge/diagnostics still function.

If you have a Jitendra, please post:

Model/year and odometer
Latest firmware versions (BMS, motor controller, dashboard)
A 0-100% discharge log (voltage, current, temp) and any service invoices with part numbers

If your experience has been flawless, that’s useful too-but let’s back it with numbers and artifacts. The market’s maturing; our standards should, too.

chargemastermind

Quick datapoints from a small mixed fleet (2x Jitendra JMT 1000 HS MY2023 in Pune; ₆.8k km and ₅.1k km):

Battery/BMS
- Pack label: 60 V NMC. Usable energy from full to LVC at ₀.6C: 2.45-2.6 kWh (Victron SmartShunt logs over multiple cycles).
- Peak pack temp seen: 48-50°C after a 15-18 km continuous climb at 37-40°C ambient; current limit/derate kicked in _50°C pack or when motor temp (internal NTC) crossed _110°C.
- No transparent AIS-156 Phase II report; only an ICAT sticker. Vendor refused to share summary-red flag.
- Charge connector on both bikes was a cheap “aviation” style; one browned pin after monsoon. Swapped to a sealed, branded connector; no repeats.
Telematics/firmware
- OTA cadence ₆-10 weeks. One update quietly changed throttle/regen map; another bricked a dashboard, needed dealer reflash.
- No public PID list. CAN header present but undocumented; BMS data gated via their app.
- Pulled the SIM and blocked APN for 8 days: start/ride/charge worked; app dead, no immobilize. So at least basic operation survives a cloud outage.
Drivetrain/durability
- Hub motor. Rear wheel bearings needed replacement once after deep-water days (we use 6202-2RS now + better grease).
- Regen is conservative; no bearing heat issues, but rear can step out on wet paint if you chop throttle mid-corner (no ABS coordination evident).
- Real-world consumption, 100 kg system, 35-40 km/h avg, stop-go: 29-34 Wh/km (city, mixed seasons). Heat and rain push it to the high end.
After-sales/parts
- Controller, display, throttle: available. BMS not sold separately; pack-only swap policy.
- Controller appears paired-drop-in third-party controller throws faults without dealer tool.
- Warranty SOH judged by their tool; no DCIR number shown. A claim at 67% “app SOH” was denied.
Weatherproofing
- IP claims not matched by reality: moisture found in two unsealed connectors post-pressure wash; dielectric grease + heat-shrink fixed it.
- Battery bay had poor drain; we added small weep holes to stop pooling.

If we run the community audit, I’ll log with a SmartShunt + GPS and stick thermocouples on pack shell and controller. Also +1 to testing a full offline week with SIM removed and DNS blocked.

VoltPro

Good add. A few concrete next steps we can all run without OEM cooperation:

Capacity and DCIR: Log a 0.5C-0.7C CC discharge to LVC for usable Wh. Then do a 10 s 1C pulse at ₆₀-70% SoC; DCIR ≈ ΔV/ΔI. Share ambient and pack temps.
Sleep current: Measure key-off quiescent draw at the battery lead with a shunt; anything >2-3 mA will eat packs during storage.
Offline survivability: Pull SIM and block DNS; confirm start/charge, horn/lights, and whether SoC/faults remain accessible via dash. Also test if immobilizer still works from the app when the bike later comes online.
Water ingress sanity: After a heavy rain ride, megger the motor phase-to-housing at 500 V; aim >10 MΩ. If low, bake/dry and reseal grommets. Inspect connectors; upgrade to sealed families (TE Superseal 1.5 / Amphenol AT) and add a PTFE/Gore vent on battery shell if none is present.
Connectors/heat: Stick temp dots on charger plug and inlet; >65-70°C at pins = resistance/oxidation. Photograph any browned terminals and note brand/series.
Bearings/brakes: Note bearing codes pulled from wheels (e.g., 6202/6203 2RS). Share pad shape cross-refs so we can source generics. Check for regen-induced rear pad glazing after long descents.
CAN access: Try 250/500 kbps with a CANable/SavvyCAN; look for periodic BMS frames (voltage/current/temp) and log IDs. Even a minimal DBC (V, I, T) helps replicate SOH/Wh without cloud.
AIS-156 proof: Post the certification sticker photo (lab name-ARAI/ICAT/CIRT, report number). If anyone has a summary page, redact VIN and upload. Nail-penetration/thermal propagation result line is key.
Charger safety: Measure earth leakage and case temperature after a 2-hour charge at 40°C ambient. Note if ELCB/RCCB trips.

I can host a shared folder for raw CSVs (GPS, pack V/I/T, ambient) and photos of labels/connectors. Two comparable loops from different cities would already tell us if the stack is robust or just passing in fair weather.