Code Examples Forum Discussions

最近、私の同僚が CapSense のデモ用に設計してエレファンテック社にオーダーしたフレキのセンサー電極を少し分けてもらうことができました。

https://www.elephantech.co.jp/

Recently one of my colleague gave me a few sensor electrode of flex PCB he designed and ordered to Elephantech.

https://www.elephantech.co.jp/en/

フレキと標準の変換は下記基板を入手して使いました。

I used an adapter from the URL below

https://www.aitendo.com/product/19419

最初、CY8CKIT-043 でも試してみたのですが、EZI2C を使用した CapSense Tuner と
KitProg 経由 UART の相性があまり良くない気がしたので、いつもの CY8CKIT-044 に乗り換えて
以前買ってあった Adafruit の TFT を使用しました。
※ ILI9341/SPI/QVGA タイプの TFT であれば他のものでも使えると思います。

https://learn.adafruit.com/adafruit-2-8-tft-touch-shield-v2

At first I tried with CY8CKIT-043, but I found that EZI2C used for the CapSense Tuner and UART via KitProg do not go well, so I changed the hourse to my trusty CY8CKIT-044 and used the Adafruit TFT, which I purchased before.
Note: Probably any TFT with ILI9341/SPI/QVGA can work, too.

https://learn.adafruit.com/adafruit-2-8-tft-touch-shield-v2

Launching the CapSense Tuner / キャップセンス　チューナーを起動します

CapSense Tuner started / キャップセンス　チューナーが立ち上がりました

Click "Connect" icon in the top left / 左上にある "Connect" ボタンを押します

接続されるとボタンは "Disconnect" という表示に変わります。

The button changes to "Disconnect" when connection is established.

次に "Start" アイコンを押します。(私はいつもこれを忘れてしまいます。orz)

チューナーの動作が開始されると表示が "Stop" に変わります。

Then click "Start" icon. (Note: I always forget this >_< )

The button changes to "Stop" when the tuner started working.

ボタン1にタッチした状態

When button1 is touched

ボタン2にタッチした状態

When button2 is touched

ボタン3にタッチした状態

When button3 is touched

表示を GraphView タブに変えた時

Switching to the GraphView Tab

評価基板上のキャップセンス電極が機能するのは当然と言えるかも知れませんが、

他の電極を接続しても、殆ど手間いらずでボタンを検知できる SmartSense の機能は

ありがたいものだと思いました。

Although it is natural that EVB's on board electrodes work OK, when connecting other electrode and it works without any tuning nor hustle seems to be a great benefit of the SmartSense functionality.

schematic / トップレベル回路図

CapSense Configuration / キャップセンスの設定

各ボタン電極のチューニング実験をしてみたかったので

本来は一つのウィジェットで3つボタンの設定でも行けるのですが

あえて三つのウィジェットに各ボタンを割り振ってみました。

As I was planning to play with tuning each button electrode,

I assigned each button to different widgets.

It should work with one widget of 3 buttons, though.

Pins /  ピン設定

main.c

#include "project.h"
#include <stdio.h>
#include <string.h>
#include <math.h>
#include "TFT.h"
#include "Arial12x12.h"
#include "Arial28x28.h"

#define USE_TUNER 1u

#define STR_BUF_LEN 64
char    str[STR_BUF_LEN+1] ;

typedef struct _button {
    int value ;
    int x ;
    int y ;
    int w ;
    int h ;
} Button_Type ;

#define BUTTON_WIDTH 70
#define BUTTON_HEIGHT 70

Button_Type button[3] = {
    { 0,  30, 70, 70, 70 },
    { 0, 130, 70, 70, 70 },
    { 0, 230, 70, 70, 70 }
} ;

typedef struct I2CRamBuffer
{
    uint16 u16_rawdata[CapSense_TOTAL_SENSORS];    
    uint16 u16_baseline[CapSense_TOTAL_SENSORS];    
    uint16 u16_signal[CapSense_TOTAL_SENSORS];     
    
    uint8  u8_sensorStatus;     
    
} I2CRamBuffer;	

void draw_button(Button_Type *button, uint16_t color)
{
    TFT_fillrect(button->x, button->y, button->x + button->w, button->y+button->h, color) ;
}
    
void init_hardware(void)
{
    CyGlobalIntEnable; /* Enable global interrupts. */

#if USE_TUNER
    EZI2C_Start() ;
    EZI2C_EzI2CSetBuffer1(
        sizeof(CapSense_dsRam),
        sizeof(CapSense_dsRam),
        (uint8_t *)&(CapSense_dsRam)) ;
#endif
    
    TFT_CS_Write(1) ;
    TFT_DC_Write(0) ;
    TFT_BL_Write(0) ;
    
    SPI_Init() ;
    
    SPI_Start() ;

    TFT_BusEnable(1) ;
    TFT_Init() ;
    TFT_foreground(White) ;
    TFT_background(Black) ;
    TFT_BusEnable(1) ;
    TFT_cls() ;
    TFT_BusEnable(0) ;
    
    TFT_BL_Write(1) ;
    
    CapSense_Start() ;
    CapSense_ScanAllWidgets() ;   
}

int doCapSense(Button_Type *button)
{
    int result = 0 ;

    if (CapSense_NOT_BUSY == CapSense_IsBusy()) {
        CapSense_ProcessAllWidgets() ;
#if USE_TUNER
        CapSense_RunTuner() ;
#endif
        if (CapSense_IsWidgetActive(CapSense_BUTTON0_WDGT_ID)) {
            button[0].value = CapSense_IsSensorActive(CapSense_BUTTON0_WDGT_ID, CapSense_BUTTON0_SNS0_ID) ;
            result = 1 ;
        } else {
            if (button[0].value != 0) {
                button[0].value = 0 ;
                result = 1 ;
            }
        }
        if (CapSense_IsWidgetActive(CapSense_BUTTON1_WDGT_ID)) {
            button[1].value = CapSense_IsSensorActive(CapSense_BUTTON1_WDGT_ID, CapSense_BUTTON1_SNS0_ID) ;
            result = 2 ;
        } else {
            if (button[1].value != 0) {
                button[1].value = 0 ;
                result = 2 ;
            }
        }
        if (CapSense_IsWidgetActive(CapSense_BUTTON2_WDGT_ID)) {    
            button[2].value = CapSense_IsSensorActive(CapSense_BUTTON2_WDGT_ID, CapSense_BUTTON2_SNS0_ID) ;
            result = 4 ;
        } else {
            if (button[2].value != 0) {
                button[2].value = 0 ;
                result = 4 ;
            }
        }
    }

    CapSense_ScanAllWidgets() ;
    return( result ) ;
}

int prev_button[3] = { 0, 0, 0} ;

void draw_a_button(Button_Type *button)
{
    TFT_BusEnable(1) ;
    TFT_set_font(Arial12x12) ;   
    TFT_locate(button->x + 25, button->y + 30) ;
    if (button->value) {
        draw_button(button, Yellow) ;
        TFT_background(Yellow) ;
        TFT_foreground(Black) ;
        TFT_putstr("ON ") ;
    } else {
        draw_button(button, Blue) ;
        TFT_background(Blue) ;
        TFT_foreground(White) ;
        TFT_putstr("OFF") ;
    }
    CyDelay(10) ;
    TFT_BusEnable(0) ;
}
    
void draw_buttons(Button_Type *button)
{
    int i = 0 ;
    for (i = 0 ; i < 3  ; i++ ) {     
        draw_a_button(&button[i]) ;
    }
}

int main(void)
{
    int i ;
    
    init_hardware() ;
   
    draw_buttons(button) ;
            
    for(;;) {
        if (doCapSense(button)) {
            for (i = 0 ; i < 3 ; i++ ) {
                if (button[i].value != prev_button[i]) {
                    draw_a_button(&button[i]) ;
                    prev_button[i] = button[i].value ;
                }
            }
        }
    }
}

moto

Hi,

Here I submitting my version of the 24-bit DDS arbitrary frequency generator component. It is useful for applications requiring precision frequency generation. Provided below are: component library, datasheet, application note and several demo projects exemplifying use of the component.

Many thanks to authors of various previous incarnations of DDSs: <PSoC73>, <pavloven>, <vdvorak>, <kabron>, <JLS1>.

This component was developed as part of Warp Verilog study and does not pursue any particular purpose.

odissey1

video link: DDS tunable frequency / phase generator using Cypress PSoC5 - YouTube

Hi,

Uploaded below is a demo project showing 16-bit PWM DAC using 8-bit Fractional PWM and 8-bit Delta-Sigma Modulator and simple RC-filter.

The PWM DACs are popular in budget audio applications due to their simplicity. The known issue of this approach is very slow response due to the necessity to filter out the main PWM harmonic: PWM_Clock / 2^N, where N - is the number of PWM bits.  For 16-bit PWM, and clock frequency of 48MHz, this results in 48MHz / 2^16 =  732 Hz, which is  rather slow for audio use. For 8-bit PWM, the main lobe is located at 48MHz / 2^8 =  187.5 kHz, which is acceptable for audio applications. Unfortunately, 8-bit output amplitude is not nearly enough in most cases. The project below tries to resolve this dilemma by using fast 8-bit Fractional PWM, where output duty cycle is externally switched between the (MSB) and (MSB+1) positions using custom Delta-Sigma Modulator. The PWM provides the MSB (most significant bit), while Delta-Sigma Modulator provides the LSB. This way the PWM can operate at high frequency of 187.5kHz, while the DeltaSigma Modulator provides extra bits of resolution.

As usual with PWM DACs, the absolute accuracy depends on the stability of the driving voltage Vdd, output buffer speed and symmetry against Vdd and Vss (Gnd). Any fluctuations on the power rail directly affect the DAC output. Simple RC filter provides -43dB suppression of the PWM main harmonic. Using (pseudo-) second-order filter, made of two RC filters in series, suppresses it below -75dB. 

Attached are two projects: basic and extended. The basic project includes all necessary components, and simply outputs a single voltage. The extended project scans the output from 0-65535, and uses ADC for sampling the DAC values and displaying them using SerialPlot charting software.

/odissey1

Projects include modified 1-st-order Delta-Sigma Modulator, originally developed by FY_ZHU

Extended project also uses additional custom components:

SerialPlot v0.0: Interface to real-time data charts 

PSoC Annotation Library v1.0 (optional)

Figure1. Fractional PWM DAC using 8-bit PWM modulated by 1-st order 8-bit DeltaSigma Modulator

Figure 2. PWM output is filtered by simple 1-st order RC filter with R1=2.2k, C1=100nF.

Figure 3. Project annotation using PSoC Annotation Library v1.0. The ADC serves as a voltmeter. The physical connection between Pin 12.7 (UART TX) and the SerialPlot charting software is not required.  

Figure 4. SerialPlot output while scanning DAC code 0 to 65500. Blue -  DAC code, Red  - result measured by ADC, Green - residual (ADC sample - DAC Code). R1=2.2k.

Figure 5. SerialPlot output of the residual (ADC sample - DAC code)  for R1=2.2k. Note that the shape of the curve varies with R1 value. The noise is due to the Vdd instability of the USB-powered PSoC prototyping board.

Figure 6. SerialPlot output of the residual (ADC sample - DAC code)  for R1=1.0k.

Figure 7. SerialPlot output of the residual (ADC sample - DAC code)  for R1=4.7k.

Figure 8. FFT of the AC-coupled DAC output at mid-scale (DAC code = 32767), after single RC filter (R1=2.2k, C1=100nF). The PWM at 187.5 kHz p-p is ~40mV (-43dB). The noise floor is at about -75dB.

Figure 9. FFT of the AC-coupled DAC output at mid-scale (DAC code = 32767), filtered using double serial filter R1C1-R2C2 (R1=2.2k, C1=100nF, R2=2.2k, C2=100nF). The PWM noise at 187.5 kHz is not discernible above the noise floor (-75dB).

Hello everyone,

I am sharing a project that shows a basic example of how we can use the SCB UART block to wake up the PSoC 4 from DeepSleep mode. I have seen multiple examples of using the I2C for waking up PSoC 4 from DeepSleep. The example with UART is a useful one that can be used in various projects.

Kit used: CY8CKIT-145-40XX PSoC 4000S Prototyping Kit (Link)

Softwares used: PSoC Creator 4.4, Tera Term

Documents referred: PSoC 4 Serial Communication Block (SCB) Component Datasheet (Link)

Method:

• Select an empty project
• In the TopDesign add the UART component (Make sure it is SCB version of UART not UDB) 
• Mark the option “Enable wakeup from Deep Sleep Mode” in the configuration window option for the UART SCB block component
• I have attached the screenshot of what configuration I have done for the UART 

• Also, add a Digital Output pin in the TopDesign which will be used in connecting an LED that will indicate in which mode PSoC 4 is currently in. 

• The next step of the project is the Pin Assignment
• Attaching the screenshot of my pin assignment for the project attached. You may change it according to the board used by you

Code:

int main(void)
{
CyGlobalIntEnable;
UART_Start();

for(;;)
{

LED_Write(0); CyDelay(100);
LED_Write(1); CyDelay(100);
LED_Write(0); CyDelay(100);
LED_Write(1); CyDelay(100);
LED_Write(0); CyDelay(100);
LED_Write(1); CyDelay(100);

UART_Sleep();  // required to be used to use the feature of UART to wakeup the device from DeepSleep
CySysPmDeepSleep();
UART_Wakeup();

}
}

Observations:

The program is written such that the LED will remain off in the deep sleep mode but when the device enters the active mode it will blink 3 times after which the device enters the deep sleep mode again.

After configuring any terminal software(I have used Tera Term) you can connect to the PSoC kit with UART. After which entering any character which will make the device Wakeup from the DeepSleep mode. Thus any character entered in the terminal will lead to the LED getting blicked 3 times.

Attaching the project here

Thanks and regards,

Ronak H

Hi,

Provided below is custom implementation of the button switch debouncer component (ButtonSw32). The component uses vertical stack counters algorithm to detect button pressed and released events, and can simultaneously process up to 32 switches without loss of performance.

Component can be useful whenever a simple button switch event need to be detected by PSoC with high reliability, such as control switches, panel-mounted momentary buttons, mechanical joysticks, etc. Component is useful when PSoC hardware debouncing is not justified for handling simple switch button, or for a system with limited hardware resources, such as PSoC4.

The component was tested using CY8KIT-059 PSoC5 prototyping kit and CY8KIT-042 PSoC4 Pioneer Board. Several demo projects are provided alongside the Application Note.

Component major features:

      Implements vertical counters algorithm.

      Detects button pressed and released events.

      Detects simultaneously up to 32 buttons.

      Does not consume hardware resources.

Attached archive contains component library, component datasheet and several demo projects for PSoC5 and PSoC4. Please read installation instructions in the readme.txt.

The component provided as-is, no liabilities. It is free to use and modify.

regards,

odissey1

=============================================================================

=============================================================================

P.S. Another useful component for HMI can be found here:

Quad Decoder with Button Switch component for rotary shaft encoders