I’m looking for a similar solution as Send FSR data to iPhone, but have two problems. My project has 2 different FSRs that send a tone to 2 different piezo speakers and an LED. Everything was working fine but suddenly there was no response to the FSRS. Now it won’t even compile. I tried with backup Esp32 with the same problem. I’m using the OS side of a MacBook Air (but it does have Parallels for Windows 10 installed) that’s a few years old. Could that be the problem? Is a Windows only computer better?
Thanks
Joel
You're running the Arduino IDE in a Windows VM on a Mac host? Why? The Arduino IDE runs natively on MacOS. That's faster and easier.
In that case you did something wrong in the code. As you didn't provide the code and the error message you get we have no chance to help.
Definitely not. It's the worst choice you can do, no other platform has so many driver problems reported in this forum than Windows.
Thank you very much for your help.
Much appreciated
The reason Windows has more driver problems is because it is utilized more:
Desktop operating system market share 2013-2022 | Statista
Personally, I use Debian Linux, but I am also a certified Microsoft Engineer. Windows 11 has a very solid plug&play driver auto install, but non-signed drivers may present issues: and should raise red flags.
I get a message
LED.ino.boot loader.bin:command not found
All was working well. 2 FSRs, 2 Piezzo speakers and 1 LED.
I was trying to trouble shoot the speakers not putting out the proper volume and now I can’t compile.
Any suggestions?
Is there a memory limitation? How can I measure it?
I’m using a MaxBook Air and Arduino 2.0
Thanks,
Joel
- Everything was working well
- Something changed
- Everything is not working well
What is (2)?
2 Likes
Please post the sketch that you are trying to compile and the full error message, using code tags when you do
Does the sketch compile when using IDE 1 ?
That pesky number 2.
I have merged your cross-posts @drjoell.
Cross-posting is against the Arduino forum rules. The reason is that duplicate posts can waste the time of the people trying to help. Someone might spend a lot of time investigating and writing a detailed answer on one topic, without knowing that someone else already did the same in the other topic.
Repeated cross-posting can result in a suspension from the forum.
In the future, please only create one topic for each distinct subject matter. This is basic forum etiquette, as explained in the "How to get the best out of this forum" guide. It contains a lot of other useful information. Please read it.
Thanks in advance for your cooperation.
Sorry
I didn’t realize I was doing it. I thought was was a reply and the other was listing a 127 error I asked for clarification.
I’ll be more careful
Joel
The error was a result of changing the program name and it must have had bad reserved symbols.
It compiled fine now.
Crazy
Thanks,
I’ll stick with my MacBook
The non compiling problem came because When all was working well I changed the name to make it easy to locate. The name was long and obviously corrupted something. I shortened it considerably and all works well. Now onto a few more bugs.
Hi Joel, have you straightened this one up? Can you share it here.... for the few more bugs thing.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.