Q8, PMS SEND TO THOSE WITH ISSUES BLF soda can light

These work on both ends of the tube - I have ordered and used them

O-rings

Search is my friend I had been using it but I was typing “O-ring” not “o ring” so I wasn’t getting any returns of the provided link

Thank you tho

Thank you big time!

Hello,

I reflowed new leds on MCPCB, connected to driver (no reflector), turned on Moon as usual and one led didn´t work, so reflowed again, assembled, but leds didnt turn on at all (no reflector). I tried to double click and got direct turbo, strobe etc, disconnected tube and from this moment everytime I connect the tube with the head I get direct turbo. The switch does not react to any click.

Could someone advice what went wrong? I cleaned everything, I checked all the wires, resolder the led wires on the driver and MCPCB, checked the wires of e-switch. When I soldered wires to the driver I accidentaly put an solder on other “connection places” for led + (there are four spots), but there is no solder bridge in to the wire, so I guess there should be a problem and I cleaned most of the solder with the wick.

I will try, but no guarantees.

What type of leds did you add? It’s not too uncommon for the moon level to be too low to light up an led. Moon level has 7 adjustments. If you mean the bottom of the ramp (moon level 3), then it might not be any big deal. As long as all 4 work as soon as you give it a bit of ramp up.

After reflowing the leds a 2nd time, they didn’t work at all, or just at the very lowest level?

When a light goes to max when you connect the battery, it’s usually because of a short circuit. The positive of the battery goes straight to the mcpcb, then the mcpcb negative wire goes to the driver which controls the output. Any type of short on this negative wire will cause the leds to go full power. You might check if the reflector is shorting it.

The 4 positive led pads are all connected, you can use any of the 4. Same for the 4 negative pads.

Make sure no driver components are being shorted against the body.

Other than that, IDK.

JasonWW, thanks for your support and help ;).

I reflowed Samsung LH351D 4000K on a new MCPCB I bought on Ali (Sofirn original spare parts for Q8).

All four leds work on Turbo. I will check everything you advice in the evening.

First time (before 2th reflow) the 3 leds lighted up on Moon as expected. After 2th reflow, none of them, just a straight turbo after double click, there was no response on single click at all (only led switch turned on/off).

The e-switch is lit and react to on/off flashlight as expected.

Sounds like the 7135 is fried on the driver… have no idea how it could have happened unless there was a short initially….

Stupid question probably, what would happen if someone put in 4 xhp35 emitters for more throw would that work in this kind of light vs the xpl emitters?

In this case, it would just be better to swap the XPLs for XPL HIs for more throw.

You will get more lumens and more throw with XHP35HIs, but you will need a different battery configuration and a buck driver, which will cost quite a bit.

yea ok, makes sense. i feel the xpl are more then enough anyways.

I’ve not posted here in a while, but I think this is the right thread. I’ve been playing around programming my Q8 (Narsil v1.0 I think) and now have a couple of weird bugs… It’d be great if someone could help me out with a fix.

If I am in ramping mode, and I press and hold then I get a flash of turbo (about 0.5 seconds), before it goes to moonlight. It’s as if the light forgets it’s in ramping for half a second and goes to what it would in the mode groups setting before it remembers what it should do. I should also say this only happens if the light hasn’t been on in the last 10-20 seconds or so, if it was recently switched off then a long press will go straight to moonlight.

There is also a probably related issue when using mode groups. This happens in similar circumstances as described above (switching on after 10-20 seconds of not being used). Here, the light comes on in the correct mode, but the indicator (under switch) LED blinks three times and the light turns itself off again. If I click a second time during the three flashes then it will usually stay on instead. This one will also sometimes happen twice, i.e. another time after turning the light back on again. I haven’t seen it three times before though.

I had thought I’d caused this by changing a setting, but I have tried switching most back to factory resets and the problems are still there.

Does anyone have any idea what is going on?

Right, I’ve actually just fixed it.

I feel a bit silly now, I’d been trying what felt like everything for the last hour or so before posting, but I hadn’t reset the step-down setting to timer instead of temperature. Doing this fixed both issues. I’m not sure why exactly, I’m guessing for the mode groups at least there was some fault with the sensor that caused it to shut the light down. I have no idea why this would also cause turbo from press and hold in the ramping setting.

I’ll leave it on timer now!

Hi, good to see you’re still around.
I’m not sure how to exactly explain what happened to your Q8, but if you set the stepdown to temperature instead of time, the default stepdown temperature can be anywhere, including room temperature. That is because the temperature is recorded in the MCU and that is extremely inaccurate. So you will have to tell the MCU the correct stepdown temperature by going through the stepdown temperature setting procedure (see manual).

But going back to timed stepdown is a good choice too, the 3 minute default is about spot-on IMO when batteries are full.

Hello,
Who can conduct a temperature study?
To what temperature does Q8 head warm up at room temperature (22-26C) without forced cooling after 20 minutes of operation ?:

  1. 1500LM (Group4)
  2. 2500LM (Group6)
  3. 750LM (Group8)
    Is there a 20-minute decrease in brightness for thermal control in these modes?
    Thank you!

1) No thermal stepfown from what I tested.

2) Still nothing.

3) Still nothing.

The only decrease in lux comes the battery voltage going down as time passes

Thanks, you too. I somehow finally managed to get away from buying new lights and more into using the ones I already have! I still get drawn in by the odd-BLF special (I really like the look of the Sofirn AAA light with the Yuji LED and I’m sure will pick a few up after the first feedback on them), but the BLF A6 and Emisar range pretty much killed off my feel for needing anything more.

I did set the temperature using the procedure on the instructions, and I waited until the body was really too hot to touch, so I thought that wouldn’t be the problem. I would have to guess that my thermal sensor was particularly inaccurate, or faulty, leading to the odd behaviour. I think timed stepdown will be fine. It’s not like I regularly need 4-5k lumens for more than 3 minutes at a time anyway!

I’m not sure if it’s the same issue, but I fixed something like that in RampingIOS between V1 and V2. If the user ran the light on a high mode for a while, then shut it off, it didn’t reset any of the thermal info it had collected. So when the user next turned it on, even at a low level, it would think it was hot and then “step down” to whatever it was going to do in the previous session, and this usually meant it would go from a low mode to a high mode.

Since RampingIOS V1 was a fork of Narsil, Narsil could be doing something similar. It wouldn’t be the first bug the two firmwares have shared.

I completely rewrote all that for FSM / Anduril / RampingIOS V3, and those also allow the thermal sensor to be calibrated. So, that’s available if you’d like the issue fixed instead of just working around it.

I resolved the issue. I guess I used too much solder paste or I moved wrongly with some led and there was a problem - straight anode-catode short. I reflowed leds again and all works fine now. Thanks for ideas anyway ;).

After these “troubles” I have really nice 4000K HI CRI beam of LH351D leds and I got a lot of new modding experiences :).

The BLF Q8 is not available on BG,when back?

Processing time:Expected on October 31, 2018

just in time for halloween.