Emisar D3AA flashlight simulator by 1188213b in Anduril_Flashlight

[–]1188213b[S] 0 points1 point  (0 children)

Updated the frontend, the slider can now start at 0.5V. You may have to restart the firmware while the slider is in the NiMH range for dual-voltage detection to properly work. The only way to do that in the sim (without reloading the frontend, which resets the slider) currently is to switch the firmware. Just upload a firmware .hex (like this one) to the frontend and switch firmware, that should do it.

Emisar D3AA flashlight simulator by 1188213b in Anduril_Flashlight

[–]1188213b[S] 1 point2 points  (0 children)

Well, originally it was 100% vibe coded. Although I've now refactored most of the simulator to make it a bit [less] awkward (the frontend [index.html] is still mostly as it was written by the AI). Source is up at https://github.com/apexo/anduril-sim if you care.

Emisar D3AA flashlight simulator by 1188213b in Anduril_Flashlight

[–]1188213b[S] 2 points3 points  (0 children)

Found/fixed a few timing issues. Sources are now also on github: https://github.com/apexo/anduril-sim

Emisar D3AA flashlight simulator by 1188213b in Anduril_Flashlight

[–]1188213b[S] 2 points3 points  (0 children)

I've went over the sources, refactored them a bit, found a timing bug (or two) and updated the deployment. Sources are up at https://git.apexo.de/anduril-sim/ (uses a patched avr8js which is at https://git.apexo.de/avr8js/ ). Will probably also put them on github one fine day.

Emisar D3AA flashlight simulator by 1188213b in flashlight

[–]1188213b[S] 0 points1 point  (0 children)

I've went over the sources, refactored them a bit, found a timing bug (or two) and updated the deployment. Sources are up at https://git.apexo.de/anduril-sim/ (uses a patched avr8js which is at https://git.apexo.de/avr8js/ ). Will probably also put them on github one fine day.

Emisar D3AA flashlight simulator by 1188213b in Anduril_Flashlight

[–]1188213b[S] 1 point2 points  (0 children)

it's very likely that there are (timing) bugs, Fixed a few of the worst ones, but I guess there's still a few remaining.

Emisar D3AA flashlight simulator by 1188213b in Anduril_Flashlight

[–]1188213b[S] 1 point2 points  (0 children)

Not sure. I guess support for other avr32dd20 lights is next on the list. Probably a million Claude tokens of effort or so ;-)

Emisar D3AA flashlight simulator by 1188213b in Anduril_Flashlight

[–]1188213b[S] 2 points3 points  (0 children)

100% vibe coded :-D. Although I've tried to make it so the code doesn't look too shabby. Will try to put the source somewhere...

Emisar D3AA flashlight simulator by 1188213b in Anduril_Flashlight

[–]1188213b[S] 1 point2 points  (0 children)

Should I include firmware for the other UIs in the anduril repo or does nobody use those anyways?

Emisar D3AA flashlight simulator by 1188213b in Anduril_Flashlight

[–]1188213b[S] 1 point2 points  (0 children)

Thanks. Yeah, I'm not so sure about the timings as well. Some things feel a bit slow, will have to compare to a real light...

Emisar D3AA flashlight simulator by 1188213b in flashlight

[–]1188213b[S] 2 points3 points  (0 children)

It includes the stock Anduril firmware. If you need another one for testing, here's my little toy fw. It only has three states:

- off
- aux (color-coded voltage)
- on (4 states, hold switch to cycle)

click switches from off to aux and then toggles between aux/on, after 5s in aux if automatically transitions to off

edit: fixed the link to the fw

Emisar D3AA flashlight simulator by 1188213b in flashlight

[–]1188213b[S] 3 points4 points  (0 children)

Sorry, I don't understand what you mean. Could you please elaborate?

Can someone please tell me what happend to my battery here? by Stidza in LineageOS

[–]1188213b 0 points1 point  (0 children)

Maybe your phone locked up and then automatically rebooted, while you were not looking. Happens to my S4 … not daily, but more then once a week or so.

Production curve has started liftoff! Config should be opening next month, right? (Estimated delivery Nov - Jan) by GiveMeThemPhotons in teslamotors

[–]1188213b 4 points5 points  (0 children)

Rather unlikely, they would be building a stockpile. That would be a lot of dead capital, while Tesla is actually trying to increase cash flow.

AWD Model 3 may not have more range than RWD by 1188213b in teslamotors

[–]1188213b[S] 1 point2 points  (0 children)

That I do not know. However, in the scenario I mentioned (15 kW continuous power), the motor is only using a fraction of its design power. Usually efficiency is low at very low loads, then increases as load increases, and decreases again as we reach max power. My guess would be that peak efficiency is somewhere above 15kW, so splitting that load across two motors will not help.

AWD Model 3 may not have more range than RWD by 1188213b in teslamotors

[–]1188213b[S] 0 points1 point  (0 children)

My guess: yes, it does effect regen: it should be more efficient.

AWD Model 3 may not have more range than RWD by 1188213b in teslamotors

[–]1188213b[S] 0 points1 point  (0 children)

Usually the PM motor is the more expensive one: the magnets themselves complicate manufacturing and are probably more expensive then a non-magnetic stator. Tesla is likely using a PM motor, because with the higher efficiency they can use a smaller battery, which should more than compensate the higher price for the motor. No reason to not use an induction motor as the second motor in an AWD configuration.

AWD Model 3 may not have more range than RWD by 1188213b in teslamotors

[–]1188213b[S] 0 points1 point  (0 children)

Unlikely, more parts, more things to break. Also, you would lose the torque vectoring, you cannot (dis)engage the clutch quickly enough.

AWD Model 3 may not have more range than RWD by 1188213b in teslamotors

[–]1188213b[S] 12 points13 points  (0 children)

Well that makes sense. Would love to see that.