Blue, high beam indicator light not on!

Ash700

Ash700

Active member
UKGSer Subscriber
Joined
Aug 30, 2013
Messages
356
Reaction score
72
Location
Epping Forest
I’m hoping that someone will be able to help me with this, and will be extremely grateful if they can.

I fitted a pair of Lone Rider Moto lights to my 2024 1250GSA and everything works perfectly, except for one thing! The blue, high beam indicator light. It works if I’m stationary but not when I’m on the move.

Whilst out riding, it became apparent that I’d accidentally hit the high beam switch with my right forefinger (probably whilst rotating the whizz wheel) and, as a result, inadvertently selected main beam. It wasn’t immediately obvious because it was a bright sunny day.. it was when I noticed the rear of the vehicle I’d caught up seemed very brightly lit. I looked to see if I was on main beam, but only the GREEN headlight on light was illuminated - no BLUE light. To check, I pulled the main beam switch back (it’s not visible from the riding position) and it clicked back to dipped beam, to which the driver of vehicle in front must have been thankful of.

Since discovering this, I’ve deliberately selected high beam a few times to see if the blue light comes on. Sometimes it does, sometimes it doesn’t? The problem is… I’ve accidentally hit the high beam switch a few times now (I’m training myself to keep my right index finger under control) but on bright, sunny days, the only way I’ve known that I’m on main beam is because of oncoming traffic flashing me. Each time this has happened I’ve glanced to see if the blue, main beam indicator light is on, but it never is? Obviously, night time isn’t an issue.. you can instantly see that the main beam is on - everything, literally, lights up!

I’m now thinking, is it something to do with the speed blending function of the centre spot, or is it some other anomaly? It’d be very useful to see the blue indicator light working properly.
 
Blue light shows on mine every time I use high beam.
Check your settings on Ezcan.
 
siddo said:
Blue light shows on mine every time I use high beam.
Check your settings on Ezcan.
Click to expand...
I’ve looked at this a few times but can’t see anywhere on the set-up that looks incorrect. It’s all set as I’ve watched the guidance vids I’ve seen. Absolutely no mention of the blue, high beam warning light. 🤔
 
It doesn’t sound like Hex EzCan has anything to do with this.

The blue high beam indicator light in your dash should light up if you’ve got high beam enabled.

If you think the Ezcan is impacting this, disconnect it from the CanBus and see if that makes any difference. .
 
DJ123 said:
Does it work if you flash high beam?
Click to expand...
Yes, it appears to work normally when I do a high beam flash. It also works (illuminates) when I push the switch forward to select the high beam, but it’s obviously catching me out when I’m on the moved and I’ve accidentally knocked it onto high beam with my LEFT index finger, which is why I’m wondering if it has anything to do with the speed blending function.

The problem I’ve had is finding an unoccupied road to test it all out. They’re that bright when activated it makes me feel guilty that I might have inadvertently burned someone’s retinas out.
 
If it works in flash, but not constant - i would suggest checking the microswitch in the switchgear. It's in a crap location which allows road grime and water to get into the switch. It's fairly easy to take it apart, and give it a clean out with some GT85, or other electrical cleaner.
 
I doubt it’s the switch, as the function works, but the indicator doesn’t. If the switch was bolloxed, neither would work. Smells like either a dodgy connection to the tft, or a software glitch.

If the OP has been programming stuff, like new lights, I guess I’d start there.
 
Drop lone rider an email. They may have been asked about this.
 
Ash700 said:
I’m hoping that someone will be able to help me with this, and will be extremely grateful if they can.

I fitted a pair of Lone Rider Moto lights to my 2024 1250GSA and everything works perfectly, except for one thing! The blue, high beam indicator light. It works if I’m stationary but not when I’m on the move.

Whilst out riding, it became apparent that I’d accidentally hit the high beam switch with my right forefinger (probably whilst rotating the whizz wheel) and, as a result, inadvertently selected main beam. It wasn’t immediately obvious because it was a bright sunny day.. it was when I noticed the rear of the vehicle I’d caught up seemed very brightly lit. I looked to see if I was on main beam, but only the GREEN headlight on light was illuminated - no BLUE light. To check, I pulled the main beam switch back (it’s not visible from the riding position) and it clicked back to dipped beam, to which the driver of vehicle in front must have been thankful of.

Since discovering this, I’ve deliberately selected high beam a few times to see if the blue light comes on. Sometimes it does, sometimes it doesn’t? The problem is… I’ve accidentally hit the high beam switch a few times now (I’m training myself to keep my right index finger under control) but on bright, sunny days, the only way I’ve known that I’m on main beam is because of oncoming traffic flashing me. Each time this has happened I’ve glanced to see if the blue, main beam indicator light is on, but it never is? Obviously, night time isn’t an issue.. you can instantly see that the main beam is on - everything, literally, lights up!

I’m now thinking, is it something to do with the speed blending function of the centre spot, or is it some other anomaly? It’d be very useful to see the blue indicator light working properly.
Click to expand...
Hi Ash700

Just to clarify, and elaborate on AndrewA's response. The easiest way would be to disconnect your ezCAN to test whether the high beam LED on the dash is giving you feedback as expected. The problem with this however, with the ezCAN disconnected, most drivers won't know you're on high beam as the stock one is horrifically bad.

Furthermore, with the lights reacting as expected to the high beam, that means the CAN bus signal is coming through, i.e. the high beam switch is working as expected. This then only leaves the actual LED on the dash as a possible failure point.

Although others have mentioned the switchgear as a possible problem, I would argue that the switches themselves are working, as the ezCAN is detecting high beam and activating the "see 3 days into the future mode". A good clean is always welcome, but I highly doubt this will resolve the issue.

For some understanding on the ezCAN itself, allow me to explain the influence of the ezCAN. The ezCAN is a listening device, that joins into the CAN bus network using a connection points where access to the entire CAN bus can be obtained on the bike itself. The only exception would be the older KTMs where we can emulate the KTM dongle feature. Other than that, we only listen to what is going on, meaning there is no way for the ezCAN to a) work as expected and b) influence a dash to not show a specific LED when the CAN bus signal is being detected (i.e. lights going on high beam when high beam switch is on). What we've found in the past, on first install, if there is a wiring issue on, for example, one of the CAN wires, the bike will throw a fault code that there is an interruption on the CAN comms of the bike. This however, is a hardware issue on the ezCAN side, which throws a constant fault on the bike.

The behaviour you're describing does not fit that consistent fault state, which points towards a hardware issue on the bike's dash.

I hope this helps, feel free to let me know if anything is unclear.

Kind regards and safe travels
 
Last edited:
HEX Support said:
Hi Ash700

Just to clarify, and elaborate on AndrewA's response. The easiest way would be to disconnect your ezCAN to test whether the high beam LED on the dash is giving you feedback as expected. The problem with this however, with the ezCAN disconnected, most drivers won't know you're on high beam as the stock one is horrifically bad.

Furthermore, with the lights reacting as expected to the high beam, that means the CAN bus signal is coming through, i.e. the high beam switch is working as expected. This then only leaves the actual LED on the dash as a possible failure point.

Although others have mentioned the switchgear as a possible problem, I would argue that the switches themselves are working, as the ezCAN is detecting high beam and activating the "see 3 days into the future mode". A good clean is always welcome, but I highly doubt this will resolve the issue.

For some understanding on the ezCAN itself, allow me to explain the influence of the ezCAN. The ezCAN is a listening device, that joins into the CAN bus network using a connection points where access to the entire CAN bus can be obtained on the bike itself. The only exception would be the older KTMs where we can emulate the KTM dongle feature. Other than that, we only listen to what is going on, meaning there is no way for the ezCAN to a) work as expected and b) influence a dash to not show a specific LED when the CAN bus signal is being detected (i.e. lights going on high beam when high beam switch is on). What we've found in the past, on first install, if there is a wiring issue on, for example, one of the CAN wires, the bike will through a fault code that there is an interruption on the CAN comms of the bike. This however, is a hardware issue on the ezCAN side, which throws a constant fault on the bike.

The behaviour you're describing does not fit that consistent fault state, which points towards a hardware issue on the bike's dash.

I hope this helps, feel free to let me know if anything is unclear.

Kind regards and safe travels
Click to expand...
Good of you to chime in.
 
HEX Support said:
Hi Ash700

Just to clarify, and elaborate on AndrewA's response. The easiest way would be to disconnect your ezCAN to test whether the high beam LED on the dash is giving you feedback as expected. The problem with this however, with the ezCAN disconnected, most drivers won't know you're on high beam as the stock one is horrifically bad.

Furthermore, with the lights reacting as expected to the high beam, that means the CAN bus signal is coming through, i.e. the high beam switch is working as expected. This then only leaves the actual LED on the dash as a possible failure point.

Although others have mentioned the switchgear as a possible problem, I would argue that the switches themselves are working, as the ezCAN is detecting high beam and activating the "see 3 days into the future mode". A good clean is always welcome, but I highly doubt this will resolve the issue.

For some understanding on the ezCAN itself, allow me to explain the influence of the ezCAN. The ezCAN is a listening device, that joins into the CAN bus network using a connection points where access to the entire CAN bus can be obtained on the bike itself. The only exception would be the older KTMs where we can emulate the KTM dongle feature. Other than that, we only listen to what is going on, meaning there is no way for the ezCAN to a) work as expected and b) influence a dash to not show a specific LED when the CAN bus signal is being detected (i.e. lights going on high beam when high beam switch is on). What we've found in the past, on first install, if there is a wiring issue on, for example, one of the CAN wires, the bike will throw a fault code that there is an interruption on the CAN comms of the bike. This however, is a hardware issue on the ezCAN side, which throws a constant fault on the bike.

The behaviour you're describing does not fit that consistent fault state, which points towards a hardware issue on the bike's dash.

I hope this helps, feel free to let me know if anything is unclear.

Kind regards and safe travels
Click to expand...
Thank you for your response to this. I have, in the meantime, been engaged in an email conversation with Lone Rider.. albeit an AI.

For anyone else who has the same issue as me, this is the exchange, so far…..

Hi Anna

My Moto Lights on my 1250 GSA on the undernose mount work great, but I have one problem that I hope you can help with.

The main beam, blue indicator light, on the TFT only seems to light when I’m stationary or moving slowly?

I’ve accidentally knocked my main beam switch whilst riding and, on bright sunny days, have not been aware that I was riding around with main beam on until oncoming traffic were flashing me. I’m thinking that there must be an anomaly which might be related to the speed blending function, as to why the blue main beam indicator light doesn’t stay on?
I’d be very grateful if you could please could you advise me on this? Is there a setting I’m missing??

Many thanks

Ash
———————

Hello Ash

Thank you so much for your detailed message! I appreciate you highlighting the issue with the blue main beam indicator light on your TFT. 😊

The behavior you’re experiencing is actually a known feature related to the Speed Blending Technology™ integrated into your Motorcycle Lights system and the MotoCAN interface. This technology automatically adjusts the light output based on your speed for enhanced safety and efficient energy management, which is why the blue main beam indicator may not stay on at higher speeds. This is not a defect but a designed feature.

If you’d like to customize this behavior, you can do so by reviewing your MotoCAN software settings. The MotoCAN application allows you to adjust features like the speed blending function and main beam indicator behavior. Make sure your MotoCAN software is up to date for the best experience. Helpful guides and downloads are available on our website.

Best regards,

Anita – Always Here to Help, Powered by AI

——————

Hi Anita

Thank you for your reply.

It’s good to know that the issue is not a defect, and is actually a design feature.

During the hours of darkness the blue indicator light isn’t needed, as the lights are super bright and make it obvious when the high beam is on - the darkness becomes highly illuminated!

My concern is during daylight hours.. I want to know if my high beam is on. The high beam/dip switch on the BMW 1250GS is very easily knocked when operating the wonder wheel. When this happens, and the main beam inadvertently selected, the physical switch position doesn’t show whether dip or high beam is selected, besides the switch is not really visible from the riding position.

I’m familiar with the set-up process when plugging the MotoCan into my laptop but there is no mention of the TFT high beam indicator light being affected by certain settings made by the user.

As you mention that the blue light not staying on is a design feature, and not a defect, please could you therefore tell me which settings I need to select for my Moto Lights in order that my TFT, blue, high beam indicator light stays illuminated when high beam is selected.

Many thanks & regards

Ash
——————

Hello Ash,

Thank you for your thoughtful follow-up and for clarifying your needs regarding the blue main beam indicator during daylight riding!

Based on the available resources and official guidance, the blue main beam indicator light on the TFT is indeed managed by the Speed Blending Technology™. Unfortunately, there is no documented user-adjustable setting in the MotoCAN software that will allow the blue indicator to remain illuminated at all times when the high beam is on, including during daylight. This automatic behavior is a built-in safety and efficiency feature.

If you are looking for advanced customization or want to further explore technical solutions beyond the publicly available MotoCAN software options, we recommend a consultation with a technical expert who can assist with in-depth configuration.

If you’d like to further optimize your setup, you might be interested in these popular accessories and upgrades:

Thank you again for your attention and feedback. If you have more questions or would like technical escalation, please let us know and we’ll be happy to transfer your request to a specialist.

Best regards,

Anita – Always Here to Help, Powered by AI
——————
Hi Anita

Thank you for your quick reply.

At this stage, please could you tell me, how the main beam indicator light, not being lit when main beam is on, is a safety feature, and an efficiency feature? It’s definitely not good for oncoming motorists, of whom I have no intention to annoy or put in a position of danger. Knowing that I am definitely on high beam would certainly alleviate this issue.

Many thanks

Ash
——————
Hello Ash,

Thank you for your thoughtful follow-up and your concern for the safety of all road users. I completely understand how important clear indication of high beam status is, especially during daylight hours!

The blue main beam indicator light's behavior is intentionally linked to the Speed Blending Technology™ within the Motorcycle Lights system and MotoCAN interface. At higher speeds, the system continuously provides optimal headlight brightness and projection to ensure your visibility to others, including oncoming traffic. The blue indicator light on the TFT does not remain on because the actual headlights themselves are designed to be highly visible, and keeping the indicator constantly illuminated could introduce unnecessary distraction or glare for other motorists, rather than being helpful. This helps to optimize both safety and energy efficiency for various conditions.

While this can feel uncertain during bright daylight, the system prioritizes effective real-world illumination over constant dashboard indication. There currently isn't a user setting in MotoCAN to allow the indicator to be on continuously at all speeds—this is by design. If you’re interested in exploring advanced technical adjustments beyond the standard MotoCAN software, a consultation with a specialist may help identify custom solutions.

If you have any other questions or are interested in product enhancements, mounting options, or accessories to further customize your experience, please let me know—I’m here to help! 👍

Best regards,

Anita – Always Here to Help, Powered by AI
——————
(From me, having dropped the "Hi/Dear")

In your second paragraph, third sentence, you state that "keeping the indicator constantly illuminated could introduce unnecessary distraction or glare for other motorists". How? As the rider, I am the only one to see the blue indicator light.. it cannot be seen by other motorists! Vehicles that are ‘type approved’ are required to have indication to the driver/rider that the ‘high beam’ is on.

Regards
——————
I’ve not yet had a reply to this one! But it seems that escalation will be the next step.

Isn’t the BLUE indicator light there for a reason? All road vehicle have them!
 
And the latest…. It’s good at pointing out the point I was pointing out?!

Hello Ash,

Thank you for your thoughtful follow-up and for raising this important point!

To clarify: the blue main beam indicator light on your TFT is a rider-facing signal only—it is not visible to other motorists. The design choice for the indicator not to remain continuously illuminated is primarily for your benefit as the rider. Based on the integrated Speed Blending Technology™, your Motorcycle Lights system and MotoCAN interface optimize headlight power and beam pattern at various speeds to ensure maximum visibility and efficiency. The indicator’s behavior is not about preventing glare or distraction for other road users; rather, it reduces unnecessary distraction or redundant signals on your dashboard and helps manage energy use, focusing your attention on real-time riding conditions.

There is currently no user-accessible setting in MotoCAN that allows the indicator to stay illuminated at all times—this is a standard feature and not an oversight.

If you’re interested in further enhancing your riding experience, you might like to explore these popular accessories:

If you wish to pursue more advanced or custom solutions, a technical expert consultation may be helpful.

If you have any more questions or concerns, feel free to reach out any time! 😊

Best regards,

Anita – Always Here to Help, Powered by AI
 
SBD said:
“Her” replies strike me as complete works of fiction
Click to expand...

I don’t think it makes sense either.

The Motolights are connected to the EzCan, and Hex have already said it should have no impact.

The “speed blending” on the motolights relates to when the central high power LED switches on - you can opt for it to only be on at a certain speed or higher. That shouldn’t be related to the high beam indicator light in your dashboard.

The quickest thing is still to unplug the EzCan and test - it’d take barely 10mins to do.

Edit: The motolights use the upper 4 LEDs for high beam - the central spot affected by “speed blending” is in addition to these.

IMG_4421.jpeg
 
Last edited:
HEX Support said:
Hi Ash700

Just to clarify, and elaborate on AndrewA's response. The easiest way would be to disconnect your ezCAN to test whether the high beam LED on the dash is giving you feedback as expected. The problem with this however, with the ezCAN disconnected, most drivers won't know you're on high beam as the stock one is horrifically bad.

Furthermore, with the lights reacting as expected to the high beam, that means the CAN bus signal is coming through, i.e. the high beam switch is working as expected. This then only leaves the actual LED on the dash as a possible failure point.

Although others have mentioned the switchgear as a possible problem, I would argue that the switches themselves are working, as the ezCAN is detecting high beam and activating the "see 3 days into the future mode". A good clean is always welcome, but I highly doubt this will resolve the issue.

For some understanding on the ezCAN itself, allow me to explain the influence of the ezCAN. The ezCAN is a listening device, that joins into the CAN bus network using a connection points where access to the entire CAN bus can be obtained on the bike itself. The only exception would be the older KTMs where we can emulate the KTM dongle feature. Other than that, we only listen to what is going on, meaning there is no way for the ezCAN to a) work as expected and b) influence a dash to not show a specific LED when the CAN bus signal is being detected (i.e. lights going on high beam when high beam switch is on). What we've found in the past, on first install, if there is a wiring issue on, for example, one of the CAN wires, the bike will throw a fault code that there is an interruption on the CAN comms of the bike. This however, is a hardware issue on the ezCAN side, which throws a constant fault on the bike.

The behaviour you're describing does not fit that consistent fault state, which points towards a hardware issue on the bike's dash.

I hope this helps, feel free to let me know if anything is unclear.

Kind regards and safe travels
Click to expand...
Hi Ash

Right, so this is a good example of why AI causes more frustration than relief...

It is required by law to have an indicator on your dash when your lights are a) on, b) in high beam, and c) when your fog/aux lights are on. That's why we never released a fog light feature until we could link it with something like the ezSwitch to give you a visual indicator that it is on. We rely on the motorcycle being roadworthy and able to show you when the high beam is on.

Please disregard the statement that the high beam indicator being defective is a feature/designed for the motolights' speed blending feature. That is just not true at all. Please refer to my original response here for clarification.

Kind regards and safe travels
 
Update!

Well… I did as a few of you suggested (including HEX Support) by disconnecting the MotoCan at the canbus plug and also removing the 30A fuse, and then went out on the bike to see how things functioned when riding.

It’s not easy finding roads without traffic ahead, or oncoming! Anyway, I managed to find enough road(s) to conduct a test with sufficient distance and duration. Everything worked perfectly - I suspected it would. The headlight came on dipped beam when not on Auto; main beam came on when switched on, as did the blue Indicator lamp on the TFT; it when off when main beam was turned off. I carried this repeatedly for a good few miles, but all worked as it should have done.

At the roadside, I reconnected the MotoCan, plugged the fuse back in and then proceeded to conduct the same test again. I didn’t expect it, but everything now works fine. The blue indicator lamp on the TFT now stays on for as long as the main beam is on (as it should do), and goes off when main beam switched off (as it should do).

The information I was given by the Lone Rider AI email responder was total, utter nonsense! They are in charge of it, so it’s their responsibility to ensure what it spouts is not BS. Clearly it was BS, and I have a copy of each of the responses to verify it.

Thank you to everyone who responded to my original with your advice, it was all gratefully received and it also turned out to have solved the problem. I keep forgetting how small computers are these days and often overlook the simple task of rebooting, which, in this case, seems to have done the trick. On the surface my problem seemed to be a minor issue, but these light are so incredibly bright it was a relief to see the blue, main beam, TFT lamp working as it should. And… I will be training my left index finger 😁

🍻
 
The headlight beam switch - Dipped beam selectedIMG_5904.jpeg

The headlight beam switch - main beam selected.
IMG_5905.jpeg

Not much difference, and it’s out of sight!
 
Glad it’s sorted, even if it still doesn’t quite explain how the EzCan can affect the high beam indication light in your dash!
 
Nippy Normans supply Touratech, Wunderlich, Desert Fox and many other makes of accessories.
You must log in or register to reply here.

Similar threads

High beam indicator failed.
Replies
8
Views
1,632
Antti
Antti
(RIP) Boxertools
Why won't my full beam indicator light work?
Replies
2
Views
932
(RIP) Boxertools
(RIP) Boxertools


Back
Top Bottom