PSoC™ 4 Forum Discussions

Hi...

I am using psco part CY8C4246AZI-L445 with USB output...

I wanted to implement the kind of touch feedback in my design...

Please suggest me the best suitable part number having at least haptic + USB + 3 UART feature.

or any other part with low cost having haptic feedback..

Thanks in advance...

Hello Everyone,

EDIT:  I've solved it. I did not have a clear enough understanding of the CAN Protocol and the Transceiver I was using.  There were 2 things I did to solve my issue:

     1) I connected the Tx Signal to the Transceiver.  I previously did not have it connected to anything and was just probing the pin.

     2) I calculated the Sync parameters on the receiving end.

All is well now, but I'll leave this up in case anyone comes across this issue.

ORIGINAL MESSAGE:

I am trying to send data using the CAN peripherals on the CY8CKit-044 and it does not send any data. Below is my code, and I've attached the full project for context.

I'm monitoring the return value of CAN_SendMsg() and it returns a success 8 times then constantly fails.  When CAN_SendMsg() succeeds there is no signal on the physical pin (TX: P0[1], RX: P0[0]) when I probe it.  It doesn't look like it is actually transmitting anything before it fails.

I'm absolutely lost. I followed the Component Datasheet (incl. trimming with WCO).  Even when I load the example project there is no signal on the pins.  Has anyone encountered this? Am I forgetting to enable or reset something?

Any insight on this would be a huge help.

/* ---- MAIN LOOP ---- */

CAN_TX_MSG CAN_Msg;

CAN_DATA_BYTES_MSG txData;

#define CAN_MESSAGE_ID (0x1AAu)

#define CAN_MESSAGE_IDE (0u)    /* Standard message */

#define CAN_MESSAGE_IRQ (0u)    /* No transmit IRQ */

#define CAN_MESSAGE_RTR (0u)    /* No RTR */

#define TX_DATA_SIZE (25u)

uint8 MESSAGE[] = {0x00,0x11,0x00,0x11,0x00,0x11,0x00,0x11}; //define 8 bytes of data

int main(void)

{     

    CAN_Msg.dlc = CAN_TX_DLC_MAX_VALUE;

    CAN_Msg.id  = CAN_MESSAGE_ID;

    CAN_Msg.ide = CAN_MESSAGE_IDE;

    CAN_Msg.irq = CAN_MESSAGE_IRQ;

    CAN_Msg.msg = &txData;

    CAN_Msg.rtr = CAN_MESSAGE_RTR;

    uint8 error = 0;

    uint8 i;

    RGB_Init();

    USB_Bridge_Start();

    CAN_Start();

    CAN_SetOpMode(CAN_ACTIVE_RUN_MODE);

    CyGlobalIntEnable; /* Enable global interrupts. */

    for(i=0; i < CAN_TX_DLC_MAX_VALUE; i++){

        txData.byte = MESSAGE; /* move data to the structure */

    }

    for(;;)

    {

        error = CAN_SendMsg(&CAN_Msg);

        if(error == CAN_FAIL)

        {

            RGB_Blink(Red, 1);

        }

        else if(error == CYRET_SUCCESS)

        {

            RGB_Blink(Green, 1);

        }

    }

}

Hello Together,

we made a Bluetooth Dongle, which sends Data from Com-Port to a BLE-Device.

we use the CyBle_GattcWriteLongCharacteristicValues, but only 16 Bytes where received on the BLE-Device.

The handler is build up like this:

      CYBLE_GATTC_PREP_WRITE_REQ_T tempHandle;

    tempHandle.handleValuePair.attrHandle = cyBle_customCServ[CYBLE_CUSTOMC_SERVER_UART_SERVICE_INDEX]

        .customServChar[CYBLE_CUSTOMC_SERVER_UART_SERVER_UART_RX_DATA_CHAR_INDEX]

        .customServCharHandle;

    tempHandle.handleValuePair.value.val = UART_data;

    tempHandle.handleValuePair.value.len = dataLen;  

    volatile CYBLE_API_RESULT_T t = CyBle_GattcWriteLongCharacteristicValues(cyBle_connHandle, &tempHandle);

The dataLen is 60 and all Data are in the UART_data.

We dont know the mistake yet, maybe you guys have an idea, what is wrong with this method.

Thank you.

i'm playing with the capsense function of PSOC 4 pioneer kit. i'm using the matrix widget to control the LED.

the collumns work fine but the second i try to use rows nothing happens. i dont know how or why it doesnt work?

i tried CapSense_CheckIsSensorActive(CapSense_SENSOR_MATRIXBUTTON0_ROW0__MB) but this does nothing

so the question is how do i use the rows of the matrix?

Hello

It is not normal case.

I need to reset MCU using external reset pin.

I need to reset every minutes.

It is home appliance application.

so It always power on and reset every minutes.

Is this reset make any problem of MCU?

Hi,
I was wondering why is the minimum recommended overlay thickness for a CSX touchpad 0.5mm? Is it due to the fact that the capacitance starts to increase at a certain point? I am not sure I understand this electric phenomenon.

Also, for touchpads, we recommend a 0.5 mm thick overlay max (basically 0.5mm is the only option for CSX touchpads). Is there any design considerations we could make to increase this maximum overlay thickness for CSX touchpads? maybe finding a high dielectric constant overlay, increasing the distance between RX and TX elements, etc? Thank you!

Hi,

In an older post, it has been mentioned that capsense is more recent for PsoC 4100S Plus.

Original comment in older post Developping CapSense trackpads with PSOC4 and 6 :

No, PSoC 4100S and 4100S plus are different architectures and are different family of controllers. PSoC 4100S Plus has a newer CapSense IP compared to 4100S. The PSoC 4100S Plus family of devices offer larger flash memory, more peripherals, and more I/Os when compared to the PSoC 4100S. You can refer this KBA for referenece: Differences between PSoC 4100S Plus and PSoC 4100S Family of Devices - KBA222580

I haven't been able to determine how the 2 different IPs (intellectual property?) are impacting performance of capsense for the Plus series. In the datasheets of the 2 series, the only way to compare them is with the 10-bit capsense ADC specs table, and the info is really technical. I wanted to know if the Plus series is actually significantly to be more robust, and would offer better performance, say for a CSX touchpad widget (not just in term of frequency, but in term of signal quality) than the normal 4100 Series.

Thank you!

Hi,

I would like to know how to cycle through endpoints on using CyUSB?  Does someone have some sample code they could make available to me?  I would like to max out the number of endpoints.  On the device side it is clear that you pass the functions the endpoint number.  The PC side is not so clear to me.

I was looking at "Cypress CyUSB .NET DLL Programmer's Reference" and didn't find clarity.

Thank you.