I can almost see your point… but “blinking an LED” vs “Semi-autonomous failsafe on a self-powered moving object”, is not quite the same… some code will be required, and NO, no one will “write it please” for you without seeing some efforts on your part first.
Re-enables interrupts (after they’ve been disabled by noInterrupts()). Interrupts allow certain important tasks to happen in the background and are enabled by default. Some functions will not work while interrupts are disabled, and incoming communication may be ignored. Interrupts can slightly disrupt the timing of code, however, and may be disabled for particularly critical sections of code.
Parameters
None
Returns
None
Example
void setup() {}
void loop()
{
noInterrupts();
// critical, time-sensitive code here
interrupts();
// other code here
}
That was a quick nap And to some degree, YES you will need to learn enough to get by… I also have a tank drive robot that I made, and while I did find an app to simply control it with, I still needed to know enough to modify the Arduino sample sketch to match my hardware and accommodate any “extras” that I wanted, (LED control, gear change, and even a “how to not let your robot take off on its own” routine).
I haven’t Blynkified that robot yet, but when I do, I know I will need to understand how Blynk communicates and how to detect disconnects.
Search around this forum for the words connect, disconnect, etc. to see how others have handled the same types of issues.
so im strugeling
just one question .
How can my robot check the connection to my phone . would be the same as in the app
true = phone online max 500 ms
false = offline = pin x shut down
My board has destroyed because 12v have come to the big metall lanport accidentally. Have a cable not isolated
now my board is fully opened … if i power 5 v the cables starts to glow … hahahaha
Checking the Blynk link status is not sufficient for a fail-safe as this seems to check the connection between the controller and the Blynk server and not the connection between the Blynk server and the IOS/Android device.
One potential solution that I am using is to have the robot controller (in my case a Rasp Pi) “ping” the IOS/Android device every second when the robot is moving. If the ping “fails” then the movement shuts down.
The only downside is that I have to manually load the IP address of the IOS device each time as I do not use a fixed IP address.