PSoC™ 4 Forum Discussions

The data sheet for this part ( http://www.cypress.com/documentation/datasheets/cyble-022001-00-ez-ble-creator-module ) indicates that it offers a "BLE stack compatible with Bluetooth 4.1". I'm using PSoC Creator 4.2 (4.2.0.641), which documentation for the BLE component indicates that it "implements the core BLE functionality as defined in the Bluetooth Core Specification 4.2".

We are encountering a situation in which our abnormally large MTU is not being properly conveyed to the client. I'm wondering whether we are hitting the 32-byte MTU limit in BLE 4.1.

I find it interesting that at no point in the connect/notify/read/disconnect cycle does the client request the MTU size. It might well be the client program (Microchip's SmartDiscovery on Android) that simply does not ask for this information.

If all of my assumptions are incorrect, can someone show me how to notify on large packets?

(we would use shorter packets and just keep the channel open if it weren't for battery power constraints)

Hi,

I'm checking the datasheet, BLE_v3_30.pdf . And I can't find anywhere where the bonding data is stored after calling the CyBle_StoreBondingData function.

Is there anyone who can help me?

Tks

Jordi

I have been trying to use the Kit 037 to control a BLDC motor using FOC. The kit is working fine with the included motor, but when I try to make it work with my own motor (RoboDrive ILM 25x 04) it fails at high speed.

As far as I know, only these parameters should be modified:

int32_t   Motor_i32PolePairs      = 4;    // the pole pairs of rotor

float32_t Motor_f32Ld             = 0.006;  // the d axis inductance  

float32_t Motor_f32Lq             = 0.006; // the q axis inductance 

float32_t Motor_f32Res            = 1.1;    // the resistance between two phases

float32_t Motor_f32Ke             = 2.83;   // inductive voltage constant between two phases,RMS value

I have observed that information in the datasheet does not match the values in the example project "Sensorless FOC Motor Control". The datasheet states that the line to line resistance is 0.8 ohm, while the value in the firmware is 1.1. Why is this?

How is the "inductive voltage constant between two phases,RMS value" calculated?

Also, how to obtain the other values (Ld, Lq and voltage constant)?

I know that my motor has 7 pole pairs, 0.5ohm of terminal resistance, 170uH terminal inductance, 24V rated voltage and 24kRPM rated speed.

Is there a document or something I can read to better understand the other parameters and the firmware algorithm? I would like to change the closed loop parameters too, but can't find what does everyone of them do in the algorithm.

          The cy8c4025lqi-s412 chip I used does not have Capsence CSD module, only Capsence module, how to design sliding touch with Capsence module, existing routines are implemented by Capsence CSD module.If you can, please provide a code routine for me to study, thank you very much！！！

Hello, I'm approaching to PSoC4 - BLE. I need to implement an Automation I/O Profile (server and Client) but I did not find examples. Can anyone send me a sample code?

I will use CYBLE 022-001-00  as target device.

Thanks

So how do I get rid of this error on a CY8C4013SXI-400 device?

I don't see anywhere in the documentation that says you cannot use that pin for GPIO.

Thanks

Dave

HI,Community!

     In my project,there are six touch buttons. when the code does not add CySysPmDeepsleep() function,everything works normally;

but  when  wake up from deepsleep,no matter press any of the six,The state of the first Capsense touch is always Active(use the Capsense_IsSensorActive() function read key value)

   the attachment is my code.

CY8C4025AZI-S413 is used for the project. I configured 12 capsense buttons with smart-sensening mode. C-sheild and C-tank was left floating. It worked normally during normal environment but could not be waked up after 24hrs testing with 70℃ and 90% RH.

Hello,

We have implemented the Fixed Stack OTA Bootloader example and also made several changes to meet our requirements and it runs successfully.

We see that the PSOC Creator IDE generates two hex files - one for each project (bootloader and bootloadable).

We are able to load the bootloader hex via the serial programmer and then using the BLE dongle, load the bootloadable cyacd file using OTA. It all works fine.

The "problem" is that we see that if we erase the flash of the device, and then just load the bootloadble hex via the serial programmer then both the bootloader AND the bootloadable applications run on the device! So we don't understand what's going on and how is this working? We thought that the hex generated when compiling the bootloadable project holds ONLY the bootloadable project and not both the bootloader and the bootloadable. Also, if the hex holds both the projects then how were we able to successfully load the bootloadable project via FOTA?

Thanks a lot.

Regards,

David