Is it possible to use a cellphone with Bluetooth to both input instructions to a Nano and also to display feedback from the Nano? If yes, can the screen have labels or must the feedback simply display in a line or column?
I have already built my project and everything works. I am trying to eliminate a display and keypad so I can use a smaller enclosure and make everything more portable.
Yes, you can do all that if you have programmed the Nano to accept and correctly process that input. If you have already completed your project, then the answer is "NO", since you have not included that capability.
if a Nano 33 BLE you could add functionality to communicate with a smartphone
if a basic nano and you have free pins, sufficient memory, etc you could add a HC-06 or HM-10
you would then need to implement a app for the smartphone to communicate with the nano and display information etc
or using your existing system as a base draw up an updated requirements specification for a new prototype, e.g. using a ESP32, RP2040, etc to give more options
a simpler approach maybe to use a microcontroller with WiFi capability running an Access point and webserver - you then display information on web pages and enter control parameters
I know I have re-write my program. This is not a problem. I am retired and have plenty of time on my hands. I am looking for some sort of app or guidance to doing so.
"microcontroller with WiFi capability running an Access point and webserver" Is this something available on Arduino? Or do I need to move to some other micro-controller or perhaps a Raspberry Pie.
My reason for trying to do this is to make the camera mount more portable by using a smaller enclosure. I can do this by eliminating the keypad and display — hence the desire to control using a cellphone.
Begin by writing down exactly what you want to do and then begin expanding the details of each. Otherwise you will never know when you are finished with the project.
I am sorry if I wasn't clear at my first post. I was trying to be brief.
I am a photographer and I have built a camera mount for panoramic pictures. This fits on a tripod and holds my camera. It uses servo motors to move the camera both horizontally and vertically.
A panorama photo is really a series of photos that are "stitched" together on the computer to form one very wide photo. By automating the camera mount I am assured that all the frames have the same overlap.
I input the camera and lens I am using along with width of the desired panorama (in degrees). The Arduino then calculates the how many frames are required to complete the panorama.
This project was completed about 24 months ago. It works quite well. All I want to do is change the interface from a keypad and display to a cellphone. The reason is to allow for a much smaller enclosure and hence a more portable package.
A simple way to go that does not require you to write a cell phone app is to use a Bluetooth Serial module, like the HC-06.
You can download and use a Bluetooth Terminal App on the phone to send commands in the form of text messages to the Arduino. All you have to do is write your own command protocol and interpreter for the text messages.
Likewise, the terminal app can display text message responses from the Nano, just as you might use the Arduino serial monitor.
From that, it seems that all you need is to install an HC-06 onto pins 0,1 + power, and you're done. Any Android Bluetooth terminal will suffice, the most popular these days is that by Morisch. No re-writing the Nano's code, no need to fartarse about with AppInventor, no need to re-invent the wheel.
I tend to do the same thing. I'm by no means an Android app expert, but I have written a couple for production use and it tends to be extremely time-consuming.
I can get simple web application running on an ESP32 that does everything I need with far less effort than writing BLE code on the device and then app code on another device. Web browsers simplify a lot of the work needed.
As far as I'm concerned, the only advantage BLE has is low power. And yeah, it can be a huge advantage in the right project, but I've moved away from building wearables, so it doesn't matter.
I don't think there's much to think about. The hardest part of this exercise is proper handling of the serial input, which you have already got sorted.
"
I have already built my project and everything works"