I've been doing C# on Linux and NeoVim for months now. I must be masochistic because I haven't been able to setup a debugger yet, but man, NeoVim is too much fun.
That’s why I can emphasize enough why people should read datasheets and fully understand the equipment they are dealing with before messing around with stuff. It’s one of the biggest differences between an engineer and a tinkerer.
Let em break stuff, an RPi is $35. Better to screw around a get a proof of concept super fast and then get details when you face a problem. Otherwise you end up reading a 500 page data sheet, in which you won’t retain 90% of the information
@@dylpickle8147 page 8 of the rpi datasheet - took me more time to type “raspberry pi datasheet” than to find the pin voltage tolerance table. If one of my junior engineers made this mistake they would have been put on BOM management projects for the next year.
Chill. Stuff like this even happens to seasoned electrical engineers once in a while. Not too long ago, I worked on a project with an electrical engineer with 20+ years of experience and the exact same thing happened, 5V was connected to 3.3V. It still worked, but we did catch it in a review before series production started. A lot of 3.3V pins can tolerate 5V for exactly this reason, you don't want to have your CPU destroyed just because someone mixed up two super common voltages.
I definitely am a tinkerer. I have no background in electrical engineering and this project is entirely for fun. In fact, the main motivation is that I have no experience so each step has been a fun challenge. This particular mistake was caught because I was reading more about the equipment. But yes, going forward, I will probably read the specs in more detail before using new equipment.
Are you going to multiplex the fsr reading and use a level shifter? Your code can just sweep through the mux and you’ll only use one input pin. Also you could use something other than force to detect cup. For example a light sensitive resistor and a cutout through the table. This way the cup doesn’t have to perfectly sit on a large pad.
I initially was using a load cell but switched over to using FSRs. I'm not familiar with multiplexing. I will definitely do research into this before completing the next step. Thanks for the suggestions.
@@scottmacchia in my experience FSR aren’t great unless you have perfect contact. Plus you don’t really care about for you care if a cup is there. I would set up limit switches or photo resistors and then multiplex through them to see what’s occupied.
I started using vim motions inside vscode and in parallel used kickstart.nvim to get me started with nvim, I still mostly use vscode in my job related stuff cause I don't want to slow down while learning, but I take every chance I get to use nvim for personal stuff and I am aiming to hopefully fully transition in a couple of weeks
Can you go over how you made this extension? I scrapped data from the English Premier League website and saved it into MongoDB. I did this to try to learn JS. I honestly haven’t gotten further than just scraping the data and saving it to the DB. I was thinking of just replicating the EPL website with the table and turning it into a FullStack app, but doing a chrome extension makes more sense and is probably cooler! Any suggestions on what I should do?
The API that I use for the hockey data also has EPL data: rapidapi.com/apidojo/api/livescore6 The free tier allows you to make 500 requests per month. I pay for the 50,000 request version just because my app is updating the live scores every 50 seconds. However, it sounds like the 500 requests would be enough for you right now. Currently, my Chrome extension relies on a NodeJS server I built which pulls data from the external API I linked above and stores it in MongoDB. Then, my Chrome extension JS will call the Node server's endpoints to get data. The logic in these endpoints pulls the data from the database. Chrome extensions are actually really easy to build. There are just collections of HTML, CSS, and JS files. This tutorial is a good place to start: developer.chrome.com/docs/extensions/get-started/tutorial/hello-world Additionally, I've actually just started streaming my Chrome extension development here and on Twitch. I can't share the repo since it has some private API keys but in the VODs, you can see most of the code.
To summarize, doing your project as a Chrome extension makes a lot of sense since it's really just a mini website. You can even build the project in such a way that it serves as both a "full" website and a Chrome extension. Adding CSS that is dependent on page width makes this very possible.
Yea, while it might take a thousand years to crack an algorithm today, 5 years from a security hole could appear that takes that number way down, combined with advances in computing power, it’s just not worth the risk.
bruh your productivity will be less initially just because you will be sinking time into configuring everything when you have vscode that can do all you need with one click. Not saying vscode is better than having your own dotfiles setup with all tmux, zsh, nvim fully setup like a chad, but if you want to be productive sit on ur ass and write code does not matter where
That’s definitely true. In fact, I don’t plan to use most of the tools mentioned in the course (ex: Ansible, Dvorak keyboard, dotfiles management). However, for the tools I have adopted, the hope is that time is saved in long run even though it will cost me some time now.
only you can tell, are you in a state where you are bored of your current job and current project and have free time to invest into this time sink. There is profit in the long-run and make it personalized to motivate you to work if its draining@@RT-.
@@scottmacchia iirc he doesn't recommend dvorak and says he wouldn't have switched to it if he was deciding right now, he only did it for medical reasons but then discovered it was not necessary
@DMSBrian24 Ah interesting. You are correct that he does not explicitly recommend it in the course. I’ve not heard him talk about why he uses it. I’ll have to check that out
I followed up prime for so long. I dual booted my system to take full controll over system. Once i get into i3 and tmux i got addicted to that .now I barely use windows.
@@scottmacchia I'm half way through "The Last Algorithms Course You'll Need" and I really enjoy it. I'm currently in the process of switching to QWERTY from my german layout and while I'm at it I'm also properly learning touch-typing instead of my freestyle technique. As I'm not yet at my regular typing speed this makes coding a lot less enjoyable but it helps me in my path of learning vim later this year with proper muscle memory.
The circuit was inspired by this article: core-electronics.com.au/guides/force-sensitive-pads-raspberry-pi/. But there are some mistakes in their circuit which can damage your raspberry pi. My most recent video explains how to fix (need to use the 3.3V instead of 5V pin)
@@saeedjalali7339 Another user/fan of NixOS and Ansible here. They're two different projects with two different goals. NixOS's is making a truly declarative, repeatable operating system. Ansible's is declarative, automated configuration of infrastruture. NixOS isn't going to build my Cisco switch, nor is it going to manage my company's red hat systems. Ansible isn't going to ensure, beyond a shadow of a doubt, that my system is exactly what is described in its scripts; just that what is declared there has been done. Both are extremely useful tools and will continue to be
Hi, thats neat i also started the same project about last year. And went at first the same route as you with the loadcell but the more i experiment the more issues i see with this approach :) If you want exchange experiences, we can get in contact :)
Just had to explain this to someone who was going to buy tracks for his 4 wheeler so he could drive better on ice. It wasn’t easy convincing him that good winter treaded tires are better than tracks every day.
That’s definitely an option. I appreciate the feedback. I’ll spend some time looking for a switch that could satisfy the requirements. The hardest part might be the size considering I don’t have the materials to construct one myself
Easy solution Engineer style: Just add more mass to the sensor without the cup, so when some small mass is placed on it, the total mass exceeds the activation mass XD
Pressure = Force/Area. If I'm not wrong, @jamesskymobilivion is suggesting reducing the area at the base of the cup to increase the pressure. I'm not exactly certain what your measure is (it looks like just the voltage of the circuit) but there could be a couple of fixes. One suggestion could be adding more resistance to increase the voltage of the sensor. I'd assume that because it's a binary input, if you raise the "resting" voltage closer to 3.3V, the system would theoretically take less force to trigger (I'd assume).
Switch to a 16-bit ADC (SPI/I2C). I would also amplify the signal being modulated by the FSR to raise the signal floor, making it easier to read changes at the lower force ranges. Just be sure to clamp the voltage ceiling so you don't fry the ADC if too much force is applied to the FSR. You can probably just use a zener diode for this. But a 16-bit ADC may have enough resolution on its own to differentiate a small change in resistance. I would also apply a moving/running average to the readings to stabilize any transient noise.
That’s a great point. Since I am looking for binary input I concluded that there wasn’t any more need for the ADC. However you’re 100% correct. I would definitely get more detailed input and can calculate the binary result myself. I will definitely retry the experiment with an ADC
