Jump to content
Search In
  • More options...
Find results that contain...
Find results in...


  • Content Count

  • Joined

  • Last visited


This user doesn't have any awards

1 Follower

About Unimportant

Recent Profile Visitors

2,580 profile views
  1. Unimportant

    C Sound

    SDL can decode mp3 and handle the output side of things. On top of that it's available on many platforms thus portable. https://gist.github.com/cdave1/10563386&ved=2ahUKEwjSt_7r4IbsAhVLsaQKHfswAYkQFjAAegQIAhAB&usg=AOvVaw230gaWNAWOsUFs_5EYw9xd&cshid=1601121105707
  2. I assume you mean flowcharts? We use them mainly for interface design of large applications. Any non trivial application will end up with a complex interface (you can click this, but not when that is enabled, and you shouldn't be able to do that when this condition is not met, etc...). So we plan these things beforehand with flowcharts.
  3. Have you even tried compiling it? (it should't, you've got code outside a function body.)
  4. With RAM sizes increasing constantly, the statistical error chance rises with it. If you double your RAM there's now twice as many bits to possibly go faulty. Now, of course the manufacturing technology improves as well and increases the reliability of the produced parts. However, do you think it realistic to improve reliability at the same rate as size increases ? It isn't. So yes, statistically, RAM is becoming more unreliable with size increases outpacing manufacturing improvements.
  5. The C program is broken. Both i and j can reach a value of 99999. Multiplying them would overflow int. signed int overflow is undefined behavior.
  6. I'd say the low level stuff. There's an abundance of ever more abstract languages, further and further removed from the hardware, and the accompanying programmers who know less and less about how things work under the hood. That's nice and all but what I see regularly: Their abstract machine fails in some way or the other -> they're clueless about what to do next. Less and less people in the fields that actually design and build the underlying systems these languages run on. And as a result, those who do have this knowledge can eat all the other's lunch.
  7. Just pointing out the futility of people standing at the back of the car pointing and discussing why it won't run while the engine is in the front.
  8. I can't imagine 4 SOT23-5 voltage regulators doing much talking over USB, so the party pieces of this camera are on the unseen backside of the PCB.
  9. Doesn't matter, it's still linear, it'll dissipate +100W worst case - that's way too much to be reasonable. (and the chip can nowhere near handle that kind of power/current).
  10. Unusable, 12V/9A would dissipate +100W worst case.
  11. The options are (from simplest to most complex): A simple fuse that pops when you go above the allowed current and needs to be replaced. An electronic fuse: A circuit that disconnects the load when it goes above the allowed current and then needs to be manually reset (or resets itself when the fault condition goes away). Linear current limiter: A circuit that does not allow more then the allowed current to flow to the load and lowers the load voltage as required. Probably not usable in this case as it would dissipate around 100W worst case here. Switching current limiter: A circuit that does not allow more then the allowed current to flow to the load but does so by switching current trough an inductor on and off quickly - dissipates little power.
  12. Looks like a 2 layer board? Make the complete underside one large ground plane. Put all other traces on the top side. Use way thicker traces and/or polygons (especially the traces that actually carry current, such as power traces and the outputs to the motor). Don't place traces so close together for no reason, leave some room (it's a simple board, no need for acrobatics). Place C2 and C3 physically close to IC1. C1 is bulk capacitance - place it physically close to the POWERIN connector. Put a 100nF decoupling capacitor close to U$1's power pins. Edit: Also, this looks autorouted. Don't do that. Route manually, otherwise you get a mess like this. The autorouter is only meant to autoroute things like data or addressbusses.
  13. @artuc He also mentioned a DC-DC converter can rely on the capacitor ESR for loop stability. (The ESR introduces a zero which provides phase boost at higher frequencies). Polymers have much lower ESR then plain electrolytics. The result might not be stable or have such low phase margin that it rings and overshoots. Edit: nvm, I tought you meant replacing plain electrolytics with polymers.
  14. In the power supply or the motherboard? Because from what I can see in online pictures the PS3 motherboard does not contain any electrolytics. The other types of capacitors typically don't show visual signs of failure (except for tantalum, which can be overly visual on failure).
  15. I think you've got your terminology mixed up. A FET can be controlled in it's linear region, just as a BJT. And that IS analog. The linear region simply means it's neither fully on or fully off but somewhere in between, just allowing the required amount of current to flow. It's PWM that isn't linear (the switching device is either fully on or fully off) and can be seen as more digital rather then analog. However, using a FET in it's linear region is rare(*) because the key feature of a FET is that it has (can have) a very low on resistance, making it an excellent switch that dissipates little power when fully on. By using it in it's linear region it would dissipate power anyway and a much cheaper BJT can be used instead. (*) It can have it's uses tough if the application demands a voltage controlled transistor rather then current controlled.