PSoC™ 4 Forum Discussions
text.format{('custom.tabs.no.results')}
I have a CY5677 CYSMART BLE 4.2 USB Dongle and a CYBLE-214009-00 evaluation board.
I am trying to use the USB dongle as a uart-ble bridge to communicate with the CYBLE-214009 through a serial terminal. When I type a character in the serial terminal, the usb dongle should transmit that character to the cyble-214009 and the cyble-214009 should in turn send continuous sensor data for about two minutes.
Would it be possible to use the 'UART to BLE bridge peripheral' project to program the usb dongle, and edit the 'UART to BLE bridge central' project to program the CYBLE-214009 to send sensor data over BLE through UART? What changes would I need to make?
Show LessI'm starting to doubt whether this is even possible. I'd be grateful if someone could tell me if I'm wasting my time:
i have created a custom PCB using a PSoC4 BLE module. I plan to have some number of these same units within the BLE operating distance of a similar number of iPads. I want to be able to pair/bond/connect a given iPad to one and only one of these peripheral units and each unit be able to connect to only the one iPad.
The ipad will be running an app specifically designed for this and will include a provision to specify which peripheral unit to connect to.
I've tried using different local names in each peripheral which works fine when only one peripheral is advertising but when two or more are advertising the iPad seems to not care what the local names are and will sometimes connect to the one with a different local name.
Is this a place to be using PSoC's public address or what should I do (if it really is possible to do this)?
Thanks,
Dennis
Show LessI remember reading that setting up a PSoC 4 BLE as a peripheral for an iPad (iOS device) needs certain parameter values as required by Apple, but I can't find this information. Can someone please direct me to it?
Thanks,
Dennis
Show LessHello,
Can anyone explain why if we place a PSoC 4 BLE (CYBLE-224110-00), without respecting dimensions of the host PCB-keep out area, can lead us to an unacceptable BLE connection distance (RF-BLE connected at maximum 5cm RF from Tx)?
Based on Cypress datasheet "002-11264_CYBLE-224110-00_EZ-BLE_TM_CREATOR_XT_XR_MODULE.pdf" we have
Based on our board design we placed the antenna part of PSoC at the edge of host- PCB
What is the purpose of host PCB-keep out area concerning BLE RF propagation?
Keep in mind that we have an efficient VDD and VDDA in PSoC and also TX Power ,TXP, 0dBm!
Can this issue (the violation of respecting dimensions of the host PCB-keep out area for best RF perfomance) justify this unacceptable BLE RF connection or could be something wrong with other thing (bug)?
Thank you in advance
Show LessHello,
what is the best approach to manage a PSoC Creator projects with source control software like git. What files can be omitted to keep things neat and clean?
Thanks!
Nikolay
Show LessHello,
Is it possible to have a multiple of pin-out configurations under a single PSoC Creator project?
I want to be able to build same project, but with different pin assignment configurations. Changing pin assignments manually every time is very tedious and having a multiple copies of the same project with different pin assignments sounds like big redundancy. So I wonder if it is possible to save different ping assignment configuration in separate files and load the desired file before a particular build. Does PSoC Creator have anything like this?
Thanks!
Nikolay
Show LessHi there,
I spent the last 2 weeks trying to figure out why sometimes my solution seems crashing.
I have followed as much as possible all the recommendation from Cypress...
My main loop looks like:
for(;;){
// process the BLE events in the stack
CyBle_ProcessEvents();
/***********************************************************************
* Put BLE sub system in DeepSleep mode when it is idle
***********************************************************************/
ManageBlePower();
/***********************************************************************
* Run your application specific code here
***********************************************************************/
// if(applicationPower == ACTIVE)
{
RunApplication();
}
/***********************************************************************
* Process application power modes
***********************************************************************/
ManageApplicationPower();
/***********************************************************************
* Manage system power mode based on application and BLE power modes
***********************************************************************/
ManageSystemPower();
}
the systems has 2 interrupts :
interrupts # 1 => WDT (every 250 msec)
Interrupt #2 => external pin (Pin 1.1)
What I notice is that sometimes after I have pressed the button the system seems to crash.
Most of the time I see an LED going off (e.g. Green LED is gets on) and then the systems don't respond anymore.
with the oscilloscope I have noticed (in my last test this evening) that when it crashes the 24 MHz is ON for ever, draining all the battery.
Can someone have a look at the code please and tell me what I'm doing wrong please?
Thank you,
Francesco
Show LessHello,
I have seen several threads about MTU in android. Some claiming that the max MTU for android is 23 or so, others claiming it goes up to 512.
I have had some difficulty myself getting to the bottom of this. In fact, I am able to increase MTU considerably close to 512, however the reason for it is unclear.
In my android studio project, I have tried to negotiate the MTU in several locations throughout, with no success in changing MTU and increasing overall data transmision.
However, I find when insert negotiateMTU function into the OnConnectionStateChanged function, as soon as the device connects, I am able to change the MTU and get higher MTU and data transmission.
However, When I try to reduce the MTU, for example if I do not want so much data, I am not able to lower or change.
I should say, negotiateMTU funciton is not doing anything more than mBluetoothGatt.requestMtu(mtuVal); in java.
I would appreciate anyone's insight into this for changing MTU rate of the device. Not sure even if the problem is Psoc Creator Firmware or if this is Android.
Attached are PSOC Creator Firmware and Android Java Class which handles BLE services (search (OnConnectionStateChanged for example)
Show LessHi,
I am looking at using the CYALKIT for a project, standard firmware has demo mode and timer mode. Within my application I want the user to be able to use a switch to change between demo mode and timer mode. Can I change the firmware to use the charge from the 0.1F cap when in demo mode and charge that cap during timer mode?
Thanks
Luke
Show LessI am thinking of using the CYBLE-012012-10 as a simple serial interface between a 5v micro based controller and Android / iOS phones. Is this part suitable for new designs? Is there a more suitable part?
Show Less