It will create an exact copy of my project's widgets. When you are at this screen and are ready to proceed, press the QR code icon in the center and it will open your smartphone's camera to scan a QR code. Once done, I would recommend those who are new to Blynk to check out the "Getting Started" section here and also the sample LED project to get familiar with it. So head over to on your smartphone, download the Blynk app for your platform (Android or iOS) and also, make an account or log in to your existing one. This is my first project with Blynk, and from what I've seen, it's extremely easy to build IoT apps with it. Widgets are present in the Blynk app and they can be dragged and dropped, and then configured to connect with your hardware in a variety of ways. The pertinent bundle is attached.I will be using Blynk for this project with which users will have the benefit of connecting their Android as well as iOS devices.īlynk allows you to connect your hardware to the cloud very quickly and easily. I'd sure be grateful for any advice anyone could give me on this. This despite the fact that nothing relating to BLE functions, such as bonding, has been done, except whatever the code itself does, no action on my part has been taken. However, all subsequent presses cause immediate toggling of the LEDs without the required hold time. In the situation when it's not operating properly, the first press of a button whether held or not does nothing to the LEDs and the ISR is not called. Pressing and releasing the button before the timeout period is over simply stops the timer and nothing else happens. The interrupt's ISR, based on a flag which indicates which button has been pressed, then toggles the pin driving the appropriate LED. If the button is held for more than the timeout period the timer initiates an interrupt at terminal count. Operation should be: when a PB is pressed and held a timer is started (set for a timeout of 3 seconds). If I install code to allow BLE bonding when an iPhone or iPad is very close to the EZ-BLE module the switches still work properly when in Debug mode but not when "programmed" (non-debug mode). If I program this code to the PSoC 4 without code for BLE operation installed, it works fine both when doing Debug and non-debug (program) operation. The response (for test purposes) should be that SW1 will toggle an output driving an LED and SW2 will do the same to another LED. Using EZ-BLE module (CYBLE-214009-00), PSoC 4 with the pioneer board I have two pushbutton switches which I want my program to respond to when either has been pressed and held for 3-4 seconds. I don't know how I can see what the BLE saw for the entered passkey to check what went wrong. When my app is prompted and I enter '1234' into the passkey entry, the connection fails for the following reason:ĬYBLE_GAP_AUTH_ERROR_CONFIRM_VALUE_NOT_MATCH I have confirmed that this is indeed the pin here:Ĭase CYBLE_EVT_GAP_PASSKEY_DISPLAY_REQUEST: When stack comes on, set correct ECO capacitance trim valueĬY_SET_XTND_REG32((void CYFAR *)(CYREG_BLE_BLERD_BB_XO_CAPTRIM), 0x9898) ĬyBle_GapFixAuthPassKey(TRUE,dataLocal.pinCode) ĬyBle_GappStartAdvertisement(CYBLE_ADVERTISING_FAST) I have set the password to '1234' using the following code: I am trying to have my BLE device connect to my app with a simple password setup.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |