• Crank position error

    From sticks@21:1/5 to All on Mon Oct 21 16:40:13 2024
    Backed the bike out of the garage to do something, and went to fire it
    up and drive it back in and it would not fire. Pushed it in and started looking. I could see no spark. Thought maybe I fried the coil running
    the plugs so long a while back. Replaced coil and wires. Still no luck.

    Figured out how to get any code faults I could. It had two. P0374 and
    U1301.
    U codes supposedly indicate a "communication problem with the modules".
    1301 is Serial High Data or possibly ECM Serial High Data. It didn't
    say 1301 ECM, just 1301.
    The P codes indicate issues "monitored by the ECM". The 1301 looks like
    it is a crank position sensor. If the sensor took a crap I would think
    the ECM would not know when to fire and therefore wouldn't. I think I'm
    gonna get a new one tomorrow and see if that gets it running. I was
    initially afraid the ECM took a crap, but they say that is rare. Winter
    hours on parts now around here, so they weren't open today, unfortunately.

    Missing some good riding weather

    --
    I Stand With Israel!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From sticks@21:1/5 to sticks on Mon Oct 21 16:48:55 2024
    On 10/21/2024 4:40 PM, sticks wrote:
    Backed the bike out of the garage to do something, and went to fire it
    up and drive it back in and it would not fire.  Pushed it in and started looking.  I could see no spark.  Thought maybe I fried the coil running
    the plugs so long a while back.  Replaced coil and wires.  Still no luck.

    Figured out how to get any code faults I could.  It had two.  P0374 and U1301.
    U codes supposedly indicate a "communication problem with the modules".
    1301 is Serial High Data or possibly ECM Serial High Data.  It didn't
    say 1301 ECM, just 1301.
    The P codes indicate issues "monitored by the ECM".  The 1301 looks like
    it is a crank position sensor.  If the sensor took a crap I would think
    the ECM would not know when to fire and therefore wouldn't. I think I'm
    gonna get a new one tomorrow and see if that gets it running.  I was initially afraid the ECM took a crap, but they say that is rare.  Winter hours on parts now around here, so they weren't open today, unfortunately.

    Forgot to mention I did test it with an ohm meter and got nothing so I
    assume it has shorted out and has no resistance. Hopefully, I"m on the
    right path.

    --
    I Stand With Israel!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From sticks@21:1/5 to sticks on Tue Oct 22 14:10:12 2024
    On 10/21/2024 4:48 PM, sticks wrote:
    On 10/21/2024 4:40 PM, sticks wrote:
    Backed the bike out of the garage to do something, and went to fire it
    up and drive it back in and it would not fire.  Pushed it in and
    started looking.  I could see no spark.  Thought maybe I fried the
    coil running the plugs so long a while back.  Replaced coil and
    wires.  Still no luck.

    Figured out how to get any code faults I could.  It had two.  P0374
    and U1301.
    U codes supposedly indicate a "communication problem with the
    modules". 1301 is Serial High Data or possibly ECM Serial High Data.
    It didn't say 1301 ECM, just 1301.
    The P codes indicate issues "monitored by the ECM".  The 1301 looks
    like it is a crank position sensor.  If the sensor took a crap I would
    think the ECM would not know when to fire and therefore wouldn't. I
    think I'm gonna get a new one tomorrow and see if that gets it
    running.  I was initially afraid the ECM took a crap, but they say
    that is rare.  Winter hours on parts now around here, so they weren't
    open today, unfortunately.

    Forgot to mention I did test it with an ohm meter and got nothing so I
    assume it has shorted out and has no resistance.  Hopefully, I"m on the right path.

    Got the new part and ohm tested it before install and it had good
    resistance. They changed the part number and the fit wasn't exactly the
    same at the frame. Wires a little too tight for my liking where the
    mounting skid puts it. Got it all in and it fired right up!

    I finally got one right.


    --
    I Stand With Israel!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From sticks@21:1/5 to sticks on Wed Oct 23 13:16:12 2024
    On 10/22/2024 2:10 PM, sticks wrote:
    On 10/21/2024 4:48 PM, sticks wrote:
    On 10/21/2024 4:40 PM, sticks wrote:
    Backed the bike out of the garage to do something, and went to fire
    it up and drive it back in and it would not fire.  Pushed it in and
    started looking.  I could see no spark.  Thought maybe I fried the
    coil running the plugs so long a while back.  Replaced coil and
    wires.  Still no luck.

    Figured out how to get any code faults I could.  It had two.  P0374
    and U1301.
    U codes supposedly indicate a "communication problem with the
    modules". 1301 is Serial High Data or possibly ECM Serial High Data.
    It didn't say 1301 ECM, just 1301.
    The P codes indicate issues "monitored by the ECM".  The 1301 looks
    like it is a crank position sensor.  If the sensor took a crap I
    would think the ECM would not know when to fire and therefore
    wouldn't. I think I'm gonna get a new one tomorrow and see if that
    gets it running.  I was initially afraid the ECM took a crap, but
    they say that is rare.  Winter hours on parts now around here, so
    they weren't open today, unfortunately.

    Forgot to mention I did test it with an ohm meter and got nothing so I
    assume it has shorted out and has no resistance.  Hopefully, I"m on
    the right path.

    Got the new part and ohm tested it before install and it had good resistance.  They changed the part number and the fit wasn't exactly the same at the frame.  Wires a little too tight for my liking where the mounting skid puts it.  Got it all in and it fired right up!

    I finally got one right.


    Additionally, I was going to clear the U 1301 fault code to see if it
    would reappear, but it was already show as "none" for codes in that
    position. So it looks like that was connected to the ECM not getting
    all the signals it needed to proceed. Case closed I guess.


    --
    I Stand With Israel!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)