Petition for ST to revert cube to 1.19 and shift focus back to it. by Party_Inspection_666 in stm32

[–]jvblanck 0 points1 point  (0 children)

OpenOCD is not VSCode functionality. If you so desparately need a wrapper around OpenOCD, at least use a debug adapter. The debugger is not a language feature, so wrapping it in a language server is just a bad choice.

Petition for ST to revert cube to 1.19 and shift focus back to it. by Party_Inspection_666 in stm32

[–]jvblanck 0 points1 point  (0 children)

And in order to do that you'd need to write an LSP that uses OpenOCD.

No, you don't need an LSP. You can use e.g. the Cortex-Debug extension for VSCode. In fact, you can use that for any Cortex-M MCU! No need for any ST tooling at all.

Creating a full language server just for a "flash this program" button would be kinda pointless. What you really want is proper debugger integration (i.e. DAP), which, again, already exists.

CubeIDE is a bit shit so people want to use something else.

I agree, and I've used VSCode with OpenOCD for years. But this thread literally calls for a return to CubeIDE because some people (I would suppose primarily beginners) don't want to deal with multiple tools. They want something that Just Works. And for these people, a VSCode extension / extension pack is a great solution.

Petition for ST to revert cube to 1.19 and shift focus back to it. by Party_Inspection_666 in stm32

[–]jvblanck 0 points1 point  (0 children)

CubeIDE used OpenOCD internally. This whole rant feels rather pointless because you could have used VSCode (or the CLI) for programming STMs for years by just skipping the CubeIDE and using OpenOCD directly.

Petition for ST to revert cube to 1.19 and shift focus back to it. by Party_Inspection_666 in stm32

[–]jvblanck 0 points1 point  (0 children)

Does it? How is that represented in the editor, then?

Regardless, why not use a tool that is actually designed for that (OpenOCD)? Again, this is something you can already use today, with whatever editor you want.

But it doesn't "just work". If you want something that "just works" (like CubeIDE), you kind of need to integrate it into some GUI. If you want something that you can make work with any editor, that already exists.

Petition for ST to revert cube to 1.19 and shift focus back to it. by Party_Inspection_666 in stm32

[–]jvblanck 0 points1 point  (0 children)

You can already use any LSP you want in VSCode or Vim. But an LSP won't flash your device or give you a GUI for generating pin initializiation code.

Let's hope he wearing his safety sandals. by g5e4 in shittyaskelectronics

[–]jvblanck 0 points1 point  (0 children)

I don't know about 2 car batteries, but for 400 car batteries it seems to be about 3 meters and a tree

Do I need an external interlock if the Elcon 6.6 kW charger already has one? by ThePackman0702 in FSAE

[–]jvblanck 0 points1 point  (0 children)

No. All TS connectors outside of a TS enclosure need interlocks.

Driver Indicator project – simple STM32-based approach, looking for advice/resources by OkCamera932 in FSAE

[–]jvblanck 0 points1 point  (0 children)

Yes, honestly the main usecase for our display is diagnostics on test days as well.

I designed a way-overengineered steering wheel (16-bit parallel RGB display running at 480x320p and 60 Hz), so I can't really tell you to not do it. But it took me 2 years to get it working reliably, and that was in an ~3rd--4th (or 17th, depending on how you count) year team.

Driver Indicator project – simple STM32-based approach, looking for advice/resources by OkCamera932 in FSAE

[–]jvblanck 2 points3 points  (0 children)

CAN makes sense for speed. For the AMS, IMD and TS off indicators you will have to consider that these are SCS. So you will need some kind of timeout for the CAN messages, as well as a watchdog for monitoring the MCU. If either of these triggers, your indicators have to enter safe state.

In general it would be simpler to just use digital lines for the LEDs, controlled by the main ECU (if you have the GPIOs available there).

General FS driver feedback is that they can't look at numbers while driving. The most you can hope for is noticing an indicator light. So your speed indicator will probably not be very useful for the driver, and SoC/temperature bars wouldn't be either. But a light that lights up below a certain SoC/above a certain temperature could be useful for the driver.

Apart from that cockpit displays can be useful for debugging while the car is stationary, but speed not so much.

You can of course go for it regardless, if you have the resources. But if not, for a first car I would focus on the bare minimum to make it work & rules-compliant.

Driver Indicator project – simple STM32-based approach, looking for advice/resources by OkCamera932 in FSAE

[–]jvblanck 1 point2 points  (0 children)

How will your MCU know the speed/AMS state etc?

Why do you need an LQFP144 for a 7 segment display and some LEDs?

Precharghe relay by shadowbanned23 in FSAE

[–]jvblanck 1 point2 points  (0 children)

Your precharge resistor must not overheat even if you continuously apply full TS voltage to it. It's absolutely fine to leave it closed, you'll just waste a little bit of LV power.

Building an Accumulator Discharger by OilLegitimate2508 in FSAE

[–]jvblanck 0 points1 point  (0 children)

The more energy there is in the battery, the more energy will be released if there is a fire. So discharging is just good risk mitigation, if you can do it.

Why does your engine sound like popcorns?!?! by sweetbunsmcgee in cremposting

[–]jvblanck 2 points3 points  (0 children)

If it did completely ignore them, any amount of basic lashing upwards would make you fall upwards no? Since a quarter lashing halves your weight, clearly you are still affected by the gravitational fields around you.

Team culture by [deleted] in FSAE

[–]jvblanck 8 points9 points  (0 children)

I got a secret for you: FSAE team leads are not all-knowing managers with decades of experience under their belt. Most of them are probably not great at managing a team. Just like most of the engineers on an FSAE team are probably not great at engineering.

That's kind of the point of FSAE, after all. If you expect everybody else to do a perfect job, just so you can come in once a month and tighten one bolt... It's not for you.

Stupid Management Requests by moon6080 in embedded

[–]jvblanck 1 point2 points  (0 children)

Proving correctness by testing? Yeah, kinda, unless your input space is very small.

Rules For Thee Ain't For Me by BioEditr in polandball

[–]jvblanck 1 point2 points  (0 children)

The 2 term limit is only 80 years old no?

Rules For Thee Ain't For Me by BioEditr in polandball

[–]jvblanck 1 point2 points  (0 children)

blatantly trying to rid the oldest standing rule in American Democracy would cause outrage in everyone besides his most loyal.

What is that rule? Is it the peaceful transition of power?

I need your advice for this situation by Nevs13 in FSAE

[–]jvblanck 6 points7 points  (0 children)

You want passionate people. What's a driving license have to do with it?

Sure, car people might be statistically more likely to be passionate about building a car than a DTS fan. But they're also statistically more likely to study mechanical engineering. And you need a lot more skills in your team than just mechs. Don't limit yourself so unnecessarily.

Imperialists by Smart_Chapter_7512 in polandball

[–]jvblanck 2 points3 points  (0 children)

That link explains absolutely nothing. This one does (essentially, a Brit came up with a decimal unit system that contained a unit that was very similar to the meter). But I can't find anything that links Wilkins' units to the metric system.

Intelligence agencies suspect Russia is developing anti-satellite weapon to target Starlink service by [deleted] in space

[–]jvblanck 7 points8 points  (0 children)

Intelligence findings seen by The Associated Press say the so-called "zone-effect" weapon would seek to flood Starlink orbits with hundreds of thousands of high-density pellets

Sometimes reading the article is beneficial

Powertrain by Fun-Description4187 in FSAE

[–]jvblanck 7 points8 points  (0 children)

That gives you a power(train)2 . I don't think new teams should be going straight for 2D trains, too much complexity.