Review: Wurkkos TS10 w 5500K LEDs and Red Aux

LED Flashlights – General Info Other Battery Type Flashlights
1

I received a Review Sample of the
Wurkkos TS10 w 5500K LEDs and Red Aux lights

Wow this thing is tiny! I love the waistline and the tailcap design reminds me of bamboo… very nice.
Tailstands perfectly.

The TS10 beam is more throwy than the FWAA… YAAAAY!!!

and the Tint is not green, and the CCT is not Blue. This is a very nice LED.
Fwaa 219c 4000Km TS10 5500K

The light feels great in hand, the button has a solid clic, not as easy to turn on as a stock FWAA.

Did I mention that the form factor feels really nice in hand, the aux LEDs are really fun, and the tint and CRI and CCT are awesome?! Plus it throws more than the FWAA… yes I know Im repeating myself. Its worth repeating… This is a really nice little light!

weights 48 grams w battery

Outputs in Advanced mode
0.09 low (FWAA is 0.12)
1000 lumens turbo (2c from on)
525 ceiling (2c from off)

outputs in simple mode
0.7 low
ceiling is turbo (2C from off and 2C from on also)

7 clics from off to change aux light brightness.
This is Anduril 2… with NO midramp nor topramp flashes… YAY! Loving It!

2

Thanks for the side-by-side comparison with FWAA.

I’m looking forward to 2700K :smiley:

3

that could be nice, I think they have 4000K atm

btw, I recommend raising the thermal limit to 55C… this allows the light to sustain about 280 lumens… By default the light throttles down to 85 lumens within 30 seconds of higher output, such as the 100/150 ceiling in Advanced. (ceiling in simple is 150/150)…

4

sure… why do you want to see the tail?

added some glow paint to the mcpcb:
.

5

This Post is a Cry for HELP with learning how to reflash Anduril on a TS10. Maybe someone here will take pity on me, and walk me through the process.

Bear in mind Ive been struggling at every step of the way, for quite a long time.

At this point I have my iMac set up with all the software that gchart coached me on installing in Terminal. And I have the gchart SP10 Pro programmer that he built. The TS10 has the same flashing pads

So, Im trying to follow these instructions from Adair21:

===
Here’s the gist of it:

  1. wire up the programmer to the light: pin2 => GND pin6 => VCC pin1 => TX/RX (depending on the programmer, you might need a 1kOhm resistor between TX and pin1)

2. figure out what your programmer is called on your system
• mine was /dev/tty.usbserial-1420 but yours might be different

3. try to ping the light
• pymcuprog ping -t uart -u /dev/tty.usbserial-1420 -d attiny1616

4. make a backup of the existing hex
• pymcuprog read -m flash -f ~/Desktop/sc21.hex -t uart -u /dev/tty.usbserial-1420 -d attiny1616

5. erase the mcu
• pymcuprog erase -m flash -t uart -u /dev/tty.usbserial-1420 -d attiny1616

6. write the new firmware
• pymcuprog write -f ~/Downloads/anduril.2021-12-13.sofirn-sp36-t1616.hex -t uart -u /dev/tty.usbserial-1420 -d attiny1616

7. Do a factory reset on the light just because lol

And Im stuck on Step 2… how do I figure out what the programmer is called?

6

What is the output for this command? (It should be one of the devices listed)

ls /dev/{tty,cu}.*

7

thank you!

this is the result: (with the programmer plugged into a USB port on the back of my iMac)

input: ls /dev/{tty,cu}.*

output: /dev/cu.Bluetooth-Incoming-Port /dev/tty.Bluetooth-Incoming-Port

(I do not know why it lists the /dev/cu.Bluetooth-Incoming-Port twice, there are actually 4 usb ports on the back of the iMac, I have nothing plugged in to the other three)
.

8

Can you try this to see if the device is connected?

ioreg -p IOUSB -l

ioreg -r -c IOUSBHostDevice -l


Unfortunately I don’t have an adapter to test the output here.

9

either of those two command lines produce several pages of output…

here is a sample from the first command, at the end of the output:

±o USB2.0-Serial@14200000 <class AppleUSBDevice, id 0x100001140, register$
{
“sessionID” = 44282508400420
“iManufacturer” = 0
“bNumConfigurations” = 1
“idProduct” = 29987
“bcdDevice” = 611
“Bus Power Available” = 250
“USB Address” = 23
“bMaxPacketSize0” = 8
“iProduct” = 2
“iSerialNumber” = 0
“bDeviceClass” = 255
“Built-In” = No
“locationID” = 337641472
“bDeviceSubClass” = 0
“bcdUSB” = 272
“USB Product Name” = “USB2.0-Serial”
“PortNum” = 2
“non-removable” = “no”
“IOCFPlugInTypes” = {”9dc7b780-9ec0-11d4-a54f-000a27052861”=“IOUSBFam$
”bDeviceProtocol” = 0
“IOUserClientClass” = “IOUSBDeviceUserClientV2”
“IOPowerManagement” = {”DevicePowerState”=0,“CurrentPowerState”=3,“Ca$
”Device Speed” = 1
“idVendor” = 6790
“IOGeneralInterest” = “IOCommand is not serializable”
“IOClassNameOverride” = “IOUSBDevice”
}

10

TS10 surpasses FWAA from any point of view, the most beautiful and performing light, a must have!

11

I dug this up: https://forums.macrumors.com/threads/any-usb-to-serial-cable-driver-for-macos-montery.2320221/post-30542447 which says that only certain USB serial adapters that contain an FTDI chipset work on MacOS Monterey and higher.

That combined with the lack of output from this command likely means a driver issue, but I don't have a adapter here to confirm on my end

Command:

ls /dev/tty.usb*

Example output:

/dev/tty.usbserial-ftDI

12

thanks for trying… to help

my mac is on Sierra 10.12.6

is this supposed to be two separate commands:

ls /dev/tty.usb*

/dev/tty.usbserial-ftDI

it shows up as 2 separate lines in your post

13

Updated my post to clarify, the second line is the output you should get it the usb serial has been recognised.

“ftDI” is a placeholder for the serial number of the device.

14

understood, thanks

so yes, youre right, my mac is not able to see the TTL

it just responds with

ls: /dev/tty.usb*: No such file or directory

thanks again for trying to help… Im going to stop bashing my head against the wall for now… enjoy your Sunday, and

Happy Fathers day to all

15

Do you have access to any other computers? (A raspberry pi for example?)

16

> Do you have access to any other computers?

no, just this 2015 iMac…
Do I need to buy a new computer to be able to flash Anduril?

> only certain USB serial adapters that contain an FTDI chipset work on MacOS Monterey and higher.

or maybe just a different TTL Programmer?

17

I just noticed that you said your mac is on Sierra 10.12

Can you try these instructions? They apply to the CH340 chip you have on Mac versions earlier than Mojave 10.14

18

> Can you try these instructions?

thanks for the suggestion… might give it a try later… much appreciated

19

Jon, what CRI does your Opple measure?

20

99.5 Ra at 5509 CCT… but Im waiting for someone w a spectrometer to measure R9, and confirm the other values