PSoC™ 5, 3 & 1 Forum Discussions

Hello     

CyFiSNP has a strange behavior.     

I had been watching the CyFiSNP data packet, and find it.     

For example, case of using the FTK-3271.     

Sometime number of message queue is increasing when Hub is busy.     

When Hub comes ready, message queue is processed and queue will go decreasing.     

This is a normal process, but decreasing will never stop.     

Look at this, this is a my data packet dump.     

Number of remain queue will not stop at zero and repeat it eternally.     

Waste packets is transmitting forever.     

...     

ID=1 pre=D rss=8 que=2 dat=17414 : :44 :06 :70  len=3     

ID=1 pre=D rss=8 que=1 dat=17414 : :44 :06 :71  len=3     

ID=1 pre=D rss=7 que=0 dat=17414 : :44 :06 :72  len=3     

ID=1 pre=D rss=7 que=254 dat=17414 : :44 :06 :68 len=3     

ID=1 pre=D rss=9 que=253 dat=17414 : :44 :06 :69 len=3     

ID=1 pre=D rss=8 que=252 dat=17414 : :44 :06 :6A len=3     

...     

I had been checking CyFiSNP module routines     

But can't get a clue, I can't figured out where this was processed.     

CyFiSNP system has complex routines     

So some error still remain, it can't help, I guess     

However, this is a fatal error, I think     

Please Investigate it and Fix it.     

Regards.     

Howdy,

I am getting ready to do a Real Project with a PSoC and am familiarizing myself with the toolset.  We have a simple board with a CY8C20437, one debug LED, ISSP header, some capacitive switches and an I/O header.

I wanted to do a "hello world" by blinking my LED periodically.  Fair enough...throw in an LED user module, can turn on and off.  Well and good. Timer16...big problems.  (Incidentally, I've gotten the same sort of idea to work with a Sleep Timer...and I'm not even sure I'll need a full timer on my project, but it's the thought that counts - I have to figure this out now, or it will bug me for weeks!)

Basically, my LED blinks every timer interrupt - even with no LED toggle call.

Yes, I put an lcall into the TIMERWHATEVER.ASM file.  If I don't have it, or if I comment out either the Timer_EnableInt() or Timer_Start() call, the LED stays off.  (I set the pin up to default on, then turn it off at the beginning of my code.)

If I didn't know better, I'd say it looks for all the world like I'm getting a watchdog reset.  But I know better, because WDT is (was) disabled.  Actually, the code I'm attaching has it enabled and fed quite regularly just in case (actually, if I don't feed the poor watchdog, the LED stays on all the time...another interesting data point).

Using PSoC Designer 5.4.  Project and relevant schematic attached, although I really am just trying to follow the Timer16 d/s example.  Some of the code is from other ideas I've been trying in order to troubleshoot, i.e. don't take it as exactly my project code (notice some things are commented out).  Even without the other toggley count and toggley stuff I get the same problem.

I can't help but think that I'm missing something really simple here, but I just can't figure it out or find it in any UM d/s....

Anyhow, any and all help will be appreciated!

Chris

Hi Fellow Community Members,

Recently I got a chance to lay my hands on a simple servo motor (of type TS-53), which had to be interfaced with PSoC 3. Thought of sharing it on the forum.

This interface required the PSoC to give a PWM signal with the high pulse varying between 1ms and 2ms. 1 ms corresponding to 0 degrees and 2ms corresponding to max rotation possible (close to 150 degrees in my case).

The dead time between the two pulses was 40ms.

The on-board potentiometer available on CY8CKIT-001 was used to vary the position of the shaft.

The project is attached along with this post. It may come handy if someone is working on similar servos.

Hi,

I rencently began some tests on 2 CY3275 devkits communicating together (low voltage 12/24V PLC devkits).

I displayed the output signal (FSK) on an oscilloscope and figured out that the packet isn't transmitted within the expected time.

I modified the example programs in order to send a full 39B packet (1B (0xAB) + 6B header + 31B data + 1B CRC). So it should take approximately 130ms @ 2400bps to be transmitted.

The oscilloscope shows me that the packet takes 200ms to be transmitted.