1

I have 3rd party device that create PWM output which I want to measure it with Arduino, the problem I have is when I shared ground between the two boards which cause the Pulsein output to become zero. (why this is happening, and how to fix it)

The reason I am connecting the ground since I need measure other signals on that board. (All other signals are responding fine)

schematic

simulate this circuit – Schematic created using CircuitLab

code:

#define pulse_ip 3
unsigned long duration;
int ontime,offtime,duty;
float freq,period;
void setup() {
  // put your setup code here, to run once:
  Serial.begin(115200);
  pinMode(pulse_ip, INPUT);
}
   
void loop() {
  // put your main code here, to run repeatedly:

  ontime = pulseIn(pulse_ip, HIGH);
  offtime = pulseIn(pulse_ip, LOW);
  period = ontime + offtime;
  freq = 1000000.0 / period;
  duty = (ontime / period) * 100;
  Serial.print(offtime);
  Serial.print("-");
  Serial.print(ontime);
  Serial.print("-");
  Serial.print(period);
  Serial.print("-");
  Serial.print(freq);
  Serial.print("-");
  Serial.print((duty * 255) / 100);
  Serial.print("-");
  Serial.println(duty);
  delay(1000);
  
}
11
  • what is your question?
    – jsotola
    Commented Aug 2, 2021 at 16:21
  • 1
    why I am getting zero when I share the ground
    – Shahreza
    Commented Aug 2, 2021 at 16:32
  • are you sure you don't get only random pulses without common ground?
    – Juraj
    Commented Aug 2, 2021 at 16:41
  • 1
    The reason I am connecting the ground since I need measure other signals on that board. -- no, the reason you connect the grounds is because you have to. majenko.co.uk/blog/our-blog-1/…
    – Majenko
    Commented Aug 2, 2021 at 17:55
  • 1
    What (approximate) frequency is the PWM signal? And what voltage levels?
    – Majenko
    Commented Aug 2, 2021 at 18:02

1 Answer 1

1

Without connected grounds the signal on the input pin you read with pulseIn must be random noise.

Two pulseIn one waiting for HIGH change and second waiting for LOW don't make sense because for parameter HIGH, pulseIn waits for the pin to go from LOW to HIGH, starts timing, then waits for the pin to go LOW and stops timing. Then it returns the length of the pulse in microseconds.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.