Page 1 of 1

Knock Shield 2

Posted: 19 Apr 2022 14:25
by DonP
Just out of curisosity:
What purpose will the two additional resistors R10 and R11 on pins 7 and 14 serve?
Thank you.

PS: will the add-on board as can be seen next to the new Knock Shield 2 (http://www.bylund-automotive.com/educat ... _Promo.png) be available for both the knock shield and the lambda shield?

Re: Knock Shield 2

Posted: 20 Apr 2022 12:30
by DonP
One more question: if I used the Knock Schield 2 (which seems to come without the headers) on a basic Arduino Uno or Uno WiFi, would I still be able to feed a tach signal to the shield or Uno? Or will I have to resort to the soldering iron? Many thanks!

Re: Knock Shield 2

Posted: 22 Apr 2022 09:18
by Christian_Bylund
Hello DonP,

Thank you for the positive feedback.
DonP wrote:
19 Apr 2022 14:25
What purpose will the two additional resistors R10 and R11 on pins 7 and 14 serve?
R10 and R11 are just pull-down resistors for the HOLD and TEST pins. I added them for good design practice in the new revision.
DonP wrote:
19 Apr 2022 14:25
will the add-on board as can be seen next to the new Knock Shield 2 be available for both the knock shield and the lambda shield?
Yes, the expansion shields will be compatible with Knock Shield 2, Lambda Shield 2 and NOx Shield.
DonP wrote:
20 Apr 2022 12:30
if I used the Knock Schield 2 (which seems to come without the headers) on a basic Arduino Uno or Uno WiFi, would I still be able to feed a tach signal to the shield or Uno? Or will I have to resort to the soldering iron?
Unfortunately you need to resort to soldering for the UNO's.

I hope it answers your questions.

Re: Knock Shield 2

Posted: 22 Apr 2022 16:52
by K6EcuUser
Hi Folks, I'm a bit of a newbie to this, however it does seem that a tach input and rpm scaling would be very useful. So given that the Shield masks or even plugs into the headers (not sure) what soldering is required, could anyone elaborate? thanks.

Re: Knock Shield 2

Posted: 24 Apr 2022 20:11
by DonP
According to the source code of the Knock Shield Interrupt Example, it should be pin 2:

"#define TACH_INPUT_PIN 2 /* Pin used for tach signal from ECU. */"

https://github.com/Bylund/Knock-Shield- ... pt-Example


A very good intro by Christian can be found here:

https://youtu.be/47qFX65oJoo

Re: Knock Shield 2

Posted: 26 Apr 2022 12:37
by K6EcuUser
Thank you Don for your reply. I have studied the video and all the documentation. I have also found some other videos on YouTube that solder Arduino header pins. Whilst this is not my first use of Arduino, having implemented previously a fuel pressure and fuel temperature gauge, I still feel that soldering header pins is a potentially dangerous activity, given the consequences of engine knock. There seem to be 4 physical inputs to the Knock shield, why couldn't the factory offer a fifth, given the benefits of monitoring RPM for both data logging and rpm scaling? So this is not a good way to start as far as I am concerned. A better way to start, IMHO, is monitor knock in stages, say 2k - 3k rpm, then 3k - 4k rpm and so on, and match the gain constant to each band. I think I will also be tempted to run the "Det Can" (headphone/microphone) approach in parallel to build confidence in the system. Thoughts welcome. Thanks.

Re: Knock Shield 2

Posted: 27 Apr 2022 15:03
by K6EcuUser
Correction to my last post. Gain constant (Ap) is a calculated value. Integrator time constant is the one that could be usefully varied with engine speed.

Re: Knock Shield 2

Posted: 04 Jul 2022 18:44
by Christian_Bylund
Hello K6EcuUser,
K6EcuUser wrote:
22 Apr 2022 16:52
Hi Folks, I'm a bit of a newbie to this, however it does seem that a tach input and rpm scaling would be very useful. So given that the Shield masks or even plugs into the headers (not sure) what soldering is required, could anyone elaborate? thanks.
The idea is that you use Arduino Mega 2560 if you want to connect hardware or signals.
Image
K6EcuUser wrote:
27 Apr 2022 15:03
Integrator time constant is the one that could be usefully varied with engine speed.
Absolutely correct.