PSoC™ Creator & Designer Forum Discussions

Here is an example where customer placed a DFB and an OpAmp, neither of

which is available for chosen part number.

          http://www.cypress.com/?app=forum&id=2233&rID=99512

Creator component selector should show ALL PSOC components, but ones

not available to specific part chosen should be grayed out.

Regards, Dana.

 A short time ago I posted a question relating to setting up a time to determine when a packet has completed transmission.

I would like to use a small state machine that resets the timer each time a byte is received and sets a flag when packet is complete. The pseudo code is what I think should work but I needed to know if it is ok to stop the UART interrupt inside a timer interrupt and whether resetting the timer period is ok inside an interrupt. I have not shown the init routines or exact syntax but kept it simple to show the concept. I am also not sure if I have to do some sort of read in timer isr to keep timer running.

CY_ISR(TimerInterrupt)  //this routine fires when no bytes received for more than 20ms
{
    if(Mode == RECEIVING)  //only set flag if data reception has begin, else ignore timeout
    {
      DatainBuf = true;  
      UART_Stop();  //stop UART to prevent state changing after timeout
    }
}

CY_ISR(ComInterrupt)
{
    if(Mode == IDLE)  //reset stae machine, add incoing data to buffer and reset timer
    {
       DatainBuf = false;
       Mode = RECEIVING;
       Ptr = 0
    }
    ComBuf[Ptr] = UART_Read();
    Timer_WritePeriod(ms20);
}

ResetCom()  // call this before when ready to receive data
{
  Mode = IDLE;
  UART_Start();
}

if(DatainBuf) ProcessCom();  /

 I'm trying to drive a calibration voltage from a VDAC through an op-amp (for higher current drive) and monitor the voltage at the same time (I'm driving a variable load and want to manually compensate it).

I can't figure out how to get PSoC Creator to let me do this. From a routing perspective it's trivial, I can hand-route it, but I'm wondering if there's a way to do it "normally" and just not seeing it.

The pin I'm using (bottom left) is the direct output from one of the uncommitted op amps. When I try to generate this design, Creator complains that the op-amp output is only designed to drive one pin. If I try to use an AMUX (with the intention of connecting both "inputs" to the "output", Creator complains that you can't connect the common of a mux to the input of another. If I rotate the AMUX I get similar errors.

I really don't want to use a "throwaway" pin to feed the signal back. Is there a Creator-sanctioned way to do this?

What kit is best for building blood glucose meter?

Where can I get this kit in india?

Is  there software, pcb an d projrect file available?

Pramod Rao

Hello everyone,

I am a beginner for the PSoC creator. I'd like to know how to use the emfile component to communicate with MicroSDcard. I had read the emfile datasheet which it writed of way of extracting the emfile_v322b to the folder. Please see the picture below or on page 2 of emfile datasheet.

[url=http://image.ohozaa.com/view2/xMXSZMEDHPxkjZq8][/url]

Thank you so much.

In the SAR datasheet you have a reference to this define, and it is typed two

different ways -

CY_GET_REG16( ADC_SAR_1_WRK0_PTR  )

CY_GET_REG16( ADC_SAR_1_SAR_WRK0_PTR  )

Looks like the latter is what works.

Regards, Dana.

This post should really belong on a section of forum for general electrical

issues, I am requesting a new topic area be added to forum. That being said

see the video discussed below, very informative.

Take a look at this youtube video on C dependence on bias voltage.

          https://www.youtube.com/watch?v=2MQyQUkwmVMk

C dependence on its applied V, both DC and RMS, not new but rarely discussed,

or shown in datasheets in any meaningful way. Kind of like the single rail input

stage crossover distortion of OpAmps, rarely highlighted in datasheets.

Even more troubling note the discussion on how the C does not follow its own exponential

behaviour, gets very non linear. In a control loop, like use as a S/H cap, stability issues

come to mind, let alone accuracy of loop.

Needless to say if we have any of this stuff in signal path and are trying to achieve 20 bits

with DelSig, good luck.

Qualify your capacitors in short is the advice. In the very least, for bulk bypass, consider

specifiying values 2 X or more than what you need because of typical loss of C due to bias

voltage.

Regards, Dana.

Hello,

I have an issue with unstable readings from the ADC_DelSig for an unspecified period of time after the program begins, which eventually settles out. The ADC_DelSig is connected to an 8 channel AMux. As an experiment, the AMux was disconnected and one of the channels was routed directly into the ADC_DelSig.  There were no problems with the voltage readings which cast suspicion on the AMux. Has anyone seen this problem or have any ideas what might be causing the errant readings by way of the AMux. Is there a limitation on how many channels I can implement reliably?

I have been using the AMux with only 7 channels for a couple years now with no issues. I'm using  Creator 3.0.

Thanks, Nick

It would be welcome when Creator uses a module that requires

assigned pins, like LCD, that the tool, or datasheet, defines what

settings are used on the pins. In order to see this now one looks

into auto generated code, usually the Start(), and wades thru code

trying to figure out how the pins were set up. It cannot be seen in pin

view in *.cydwr tab.

I think I2C also another example of this problem.

Project datasheet like created in PSOC Designer ?

Regards, Dana.