Hello all,

I sample the Watchdog counter periodically (e.g., each 1 msec) to verify validity of Watchdog.

The Watchdog counter must be reset (CySysWdtResetCounters) periodically (e.g., each 1000 msec) to prevent interrupt or PSoC reset.

The Watchdog counter remains 0 after the first CySysWdtResetCounters for about 1000 times (seems till the second reset counter) and after it counts normal.

Has anyone seen this phenomenon?

Thanks in advance for advise.

Yacob.

Hello, we use cyc84148AZI to design our faucet project. we use two channels to sense object(like hand) one for faucet , another for Soap pump. the system has two parts, one is called universal controller, there are two buttons and led display for monitor and setting on the controller, other part is sensor with cypress chip. the controller supply 3.3v to sensor . the system is basically work, but  we cannot understand some phenomena. 

We have three ways to handle steel sink: faucet shield connected to the sink, ground connected to the sink, and sink floating(no connection of any ground or shield.

• When the sink is ground or float, touch sink will cause both faucet and soap signal go up that could cause fake trigger, while when sink is connected to faucet shield, the both signals go down that could prevent false trigger
• In all scenarios , when grab universal controller or touch button, both senses signal of faucet and soap  will rise, that can cause false activation
• When touch faucet or soap spout , the touching signal will go to saturation value, the non-touched signal will drop down
• When sink is shield the approached signal will increase much, while the other signal will increase a little. as for sink grounded or floating, the non-approached signal will keep unaffected

We are not clear why it work like that and how can we prevent from some performances that can cause fake activation, like grabbing  universal controller cord, tapping  the sink or pressing universal controller buttons. 

could you please explain why like this and give us a solution

Thanks

soap pumper. 

Just like a year ago, I was absent from CDC for a couple of weeks.

This time it was the 14th annual FPGA design course at the Ryukoku University.

昨年と同じように今年も先週、先々週と CDC をお休み(?)していました。

今回は14回目になる龍谷大学での FPGA設計講座でした。

FPGA and PSoC Course at Ryukoku University

Every year, I enjoyed the limited time campus life and the goldfish living in the fountain in front of the main building.

毎年、期間限定のキャンパスライフと一号館前の噴水で暮らしている金魚さんたちに会うのを楽しみにしていました。

https://twitter.com/ryukokust/status/1297071003131162624?s=21

But this year, thanks for the COVID-19 all the students were studying from home and the course took place in cyberspace.

So although physically I was in the same location, I could not afford to do anything else.

しかし今年はコロナ禍のおかげで学生さんたちもテレワークで講義を受講しているということで、私の講座もサイバースペースで行われることになりました。

その為、物理的にはいつもと同じ場所にいたのですが、とても他のことをする余裕はありませんでした。

And because of the increased number of attending students, we realized that the number of FPGA boards we had for this course was not enough.

So we needed to switch to the off the shelf FPGA board, which resulted that I needed to redesign and/or update all the circuits in the text and update the text itself. (T^T)

また、諸事情によって受講者が増えた為に、これまでこの講座に使用していた FPGA 基板では数が足りない事が判明しました。

急遽、FPGA 基板を市販のものに変更することになり、教科書の書き直しと全回路の再設計を余儀なくされました。 (T^T)

Anyway I barely made it. Then a couple of days before the first day,

we found that oscilloscopes were not available either. This made me to perform another hack.

何はともあれ、何とかなりそうだ！と思った矢先、本番2日前に(当然ながら)オシロスコープも足りない！ということが判明。

下記 URL のトピックの急ぎ仕事が発生しました。

A Simple Oscilloscope (CY8CKIT-044) using SerialPlotter

And finally the course started.

ようやく講習が開始されました。

The following picture was an error screen of one of the most challenging error, which the student noticed that he gave a wrong name for the project after creating the project and he renamed the project folder from the Windows. And the poor PSoC Creator could not notice the situation when it tried to save the project (to the original location).

下記写真の画面に表示されているエラーは、もっとも手ごわかったものの一つで、プロジェクトを作成した学生さんが、プロジェクト名が教科書と違うことに気が付いてウィンドウズからプロジェクトフォルダ名を変更しちゃったのですが、その時実行中だった PSoC Creator はそれを知るよしもなく・・・

The primary purpose of using an oscilloscope is to show the students bouncing of a mechanical switch.

BUT, thanks for the FPGA board maker's effort, probably they added an external low pass filter (capacitor) to the switch,

on the students' FPGA board bouncing did not take place. orz

Note: My older FPGA board shows the bouncing.

もともとオシロスコープを使用する最初の目的は機械スイッチのチャタリングを観測してもらうことでした。

し　か　し、FPGA 基板のメーカーさんが頑張っちゃって、チャタリングを除去する外付け回路を追加してくれたようです、

おかげさまでチャタリング発生しないし・・・ orz

※少し古い版の私の FPGA 基板では発生するのですが。

Then I utilized the PSoC 4 oscilloscope with the servo-motor controlling project.

次に、サーボモータ制御のプロジェクトに PSoC 4 オシロを適用してみました。

And we could monitor the change of PWM pulse width.

今回は無事に PWM のデューティが変化することを観測していただくことができました。

Anyway, I'm back in one piece 😉

なにはともあれ、ただいま(?)です (^_^)v

moto