Since '02 xBhp is different things to different people. From a close knit national community of bikers to India's only motorcycling lifestyle magazine and a place to make like-minded biker friends. Join us

Castrol Power 1

Scan – see – think – act.

Our Partner

Announcement

Collapse
No announcement yet.

Pulsar 180 RPM problem

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Pulsar 180 RPM problem

    Hello ,

    My pulsar 180 BS 4 model has completed 11 months, done 4k km so far. I found that my bike is not able to rev properly after 4.5- 5k rpm. It feels like engine rev limit is touched and not able accelerate further. Max speed able to touch around 72-75 kmph. ( In the running-in period up to 2000 km, I ride sensibly and did not cross the limit mentioned in the manual given by the company).
    Even if I put it to neutral and rev the throttle it is not able to rev beyond 5 rpm and engine sounds very harsh and stressed. I am not sure why the issue is happening. In the second service, the Bajaj service centre guys told that bike is under mileage settings and it is OK .I cannot believe as the stock performance is not meant only for mileage, it is the optimum setting for balance between performance and mileage and moreover, any new bike do not exhibit such behaviour, I do not believe Baja SCs.
    Has anyone faced similar issue? Please tell me how to check.

  • #2
    Re: Pulsar 180 RPM problem

    Topic Approved.

    I believe not crossing 4500 rpm or so, its an actual problem and no such mileage setting...

    If your air filter cleaned properly in the last service?
    Does the console show any warning light or so? Are the electric wires in place? Throtlle Position Sensor (TPS)?
    ---
    Brotherhood, Rules, Freedom. Xbhp.
    Indian riding = Alertness, Anticipation and Adjustment.

    Comment


    • #3
      Re: Pulsar 180 RPM problem

      Since it is under warranty - get it done by the Service Centre, they have to fix it - escalate to Bajaj Service Manager in your area if its not fixed soon.

      Comment

      Working...
      X