Mobile Phone to Remote Control Connecting.
Installing the app into mobile phone is a simple matter accomplished by the Android Package Installer which is part of the Android operating system pre-loaded into the device.at manufacture. There is a button at the top and bottom of each product page to facilitate the downloading and installation of each product's app, using the built-in Package Installer. If you have not already installed the app into your Android mobile phone go back to the relevant product page and install it from the Download button.
All Bluetooth devices are identified through a unique 6-byte number, the MAC address. At start the app will look for a specific file containing the target device's MAC address. If this file does not exist, or if the contents of the file are not hexadecimal characters it will exit because there is no possibility of a successful connect to the remote controller. The MAC Editor will can generate and edit and save a MAC address for all of our products and should be downloaded first. Its operation is fairly self-explanatory but the menu item Installation Step-bystep will take you through a detailed procedure.
The MAC address of the control unit can be read on a label attached to the underside of the device's housing, but if that cannot be found it can be easily discovered by using the Android Bluetooth utility resident in all mobile phones equipped with Bluetooth. Simply power up the controller and let the Bluetooth utility list all Unpaired Devices. The controller will be identified by HC-06 as the device name. There are also a wide variety of Bluetooth analysers and testers on the Play Store, all of which will scan for local devices and show their identities.
Setting the MAC Address
On starting the MAC Editor utility you will see what is depicted at left. No device is selected and the 6 MAC field contain no valid data.
On selecting a device the curent value of the MAC address will be displayed at screen top and the SAVE buttom will become visible.
Tapping any of the 6 data fields will blank that field and prepare it for data entry from the keyboard. As shown at far right.
Enter the data from the MAC label on the product exactly. There must be 2 hexadecimal characters in each field. The hexadecimal character range is 0 - 9 and A - F. Do not use the character 'O' when a numeric zero is required.
When all 6 fields are correctly set tap SAVE to store the new values in the mobile phone.
With the MAC address created and edited it is time to download and run the app. The actual Bluetooth connection process is handled by the Android operating system and Android's first requirement will be to Pair with the targetted Bluetooth device.
Please enable Bluetooth in the System Shortcuts before starting the app. If you omit this step Android will prompt you to enable the Bluetooth sub-system, and will exit once you have done so. You will then need to restart the app.
Before two Bluetooth units can connect to each other they have to be paired - like being introduced to a lady before you can ask her to dance. The pairing process is handled by Android the first time the app tries to connect to the controller, a dialogue will appear asking you for a PIN code to complete the pairing. The PIN code is always '1234', entered without the quotes.
When the Remote Control is switched on the Bluetooth module always enters receiver mode, evidenced by the flashing red LED, wherein it awaits a connection request. At this time the controller broadcasts its MAC address which can be detected and displayed by the various Bluetooth utilities available on the Google Play Store. Later versions of Android will ask the user whether access the the Bluetooth subsystem is permitted, and then whether Bluetooth should be enabled.
When the mobile phone app is started it immediately attempts to connect with the MAC address mobile phone. If potential for a successful connect exists but the two units have not yet been paired then Android and the module enter the pairing sequence and a dialogue is opened to allow the user to input the pairing PIN, which is always 1234. Often the app will need to be restarted at this point.
Any time the app is started while the mobile's Bluetooth sub-system is switched off you will be asked by Android for permission to switch it on. Depending of the version of Android in your mobile the app may exit at this point and need to be restarted. When you put the app to sleep in the background the Bluetooth sub-system will remain switched on, but eliminating the app from memory will switch Bluetooth off, thereby removing a considerable load on the mobile's battery.
If the Bluetooth connection was unsuccessful the red exclamation point is displayed on the upper left corner of the mobile's screen and a 'toast' message is flashed on the screen. The message includes the MAC address that connection was attempted with. This should be the same as indicated on the controller's label and also the MAC address stored in the mobile phone for that product.
The smoothest connect is therefore achieved by switching the Remote Control on before starting the mobile phone app.
When the red LED on the Bluetooth module in the controller stops flashing and stays on continuously. this indicates that it is connected to a host, and the host must be the mobile phone since the controller is not paired to anything else. When the mobile phone app detects data coming from the controller it changes the red alert in the top left corner to the blue Bluetooth rune, and this will remain until the app detects a persistent loss of communication with the controller.
Whenever the app is put to sleep (made to run in the background) it will disconnect from the controller and the red LED will start to flash, as will also happen if the two units are taken out of range of each other. However, when possible, connection will be automatically re-established.
In cases where controllers switch currents that are common to their own power source, such as happens with the Winch Control, Caravan Mover and Tyre Pressure Control, it is possible that this switching disturbs that power source to the extent that the operation of the controller is compromised. Typically this might happen if the supply battery is weak, the load is too heavy, or power connections are resistance-prone enough to cause large volt-drops or spiking.
Generally this problem will manifest itself in Bluetooth communications failure. Immediately such failure occurs the output relays will release, thereby disconnecting any motor being driven at the time, and 4 seconds later a message will appear on the mobile phone informing that there are no BT communications.
See the specific device's page for further information.