PSoC™ 4 Forum Discussions

I watched the video on adding a battery service and I completed the exercise and code.

Now I've added a custom service and want to write data to it.

If the battery service is accessed like this:              locHandleValuePair.attrHandle = cyBle_bass[0].batteryLevelHandle;

I see the syntax for accessing my custom service is cyBle_custom. But that variable does not contain the handle for the service i added. Why?

Is there an example simple custom BLE with code I can look at?

PSoC creator 4.1, cyc8ki-042-BLE pioneer board, 222014 plugged in. USB connected to PC. teraterm running connected to the provided com port.

Create new project for the above.

in main, add printf("hello world\n");

build, debug, run. program hangs up (printf never returns). no output on teraterm.

Whiskey Tango Foxtrot?

Hi all,

I am having some problems with using the ADC and outputting the result over I2C using CY8CKIT-042-BLE and would very much appreciate your help please!

I am trying to send 12-bit ADC output over I2C and have set up a 6-resistor potential divider to help me understand the different generated output compared to the actual voltage levels.

I am using:

Vref = VDDA/2

Unsigned differential mode

Vneg is externally set to VDDA/2

When I use the alternative resolution in the ADC and set this to 8-bit I get the output that I would expect as Vpos is changed from 0 to VDDA (3.3V), that is 0x00-0xFF.

However, when I change it back to 12-bit I get the following output:

3.3V     0x00FF

2.75V     0x006C

2.2V     0x00C0

1.65V     0x0016

1.1V     0x0069

0.55V     0x00C3

0V    0x0011

To me, it looks like the most significant 4-bits are missing.

In my code I am using the bit-shifting code to access the two bytes:

i2cbuf[1] = (adcVal >> 😎 & 0xFF; // First byte

i2cbuf[2] = adcVal & 0xFF; // Second byte

As a test, if I only bit-shift 4 bits then I output a copy of bits 4-7 which makes sense.

I am most likely making a simple mistake so I would be very grateful if someone could suggest reasons for this error and/or things for me to clarify/check to get to the bottom of this.

Many thanks,

Rich

i don't know how to set up, It's warning after i program it. Thanks

Have one PSoC 4 BLE Pioneer kit as Central/Client receiving notifications from a second PSoC 4 BLE as Peripheral/Server in close proximity (~1 meter) .  When the latter is mounted in a second Pioneer Kit operation is robust and stable however when the Peripheral/Server module is stand alone powered by a battery (2- AA batteries with about 6 inches of wire) the operation is not stable or robust.  The link will disconnect frequently and the re-connect sequence can be quite lengthy.

The modules are identical CY8CKIT-143A PSoC 4 BLE 256KB and the Pioneer Kit is a CY8CKIT-042-A.  A CySmart/CY5677 dongle about half a meter away reads -85 dBm RSSI from both versions, the the Pioneer Kit module as well as the stand alone module.  The modules have inner layer ground and power planes and appear to have adequate decoupling capacitors.  Adding an additional 47 uf ceramic cap to the stand alone module's VDDD/GND made no discernible difference.

Can these modules be used stand alone?  If so how can the hardware and software be optimized for robust stand alone operation?

(A pic of the Central and each version of the Peripheral is attached)

I'm having issues with reading the slider over BLE on the CY8CKIT-042-BLE (with the CY8C4247LQI-BL483 module). I've tried the PSoC_4_BLE_CapSense_Slider_LED project and the PSoC 4 BLE 101:4 lesson project and they both seem to have the same issue. In the CySmart app, the slider seems to jump between values as you move your finger, rather than scrolling smoothly. If I look at the characteristic value directly in the GATT DB section, it jumps from 00 -> 0c ->25 -> 3e -> 57 -> 64.  I've tried CySmart on both Android and iOS and they both show the same thing, so it seems like there is an issue with the PSoC examples. Any ideas?