I am trying to connect HT9032D with arduino. The Dout pin is connected to the RX pin on the arduino. The circuit setup is exactly same as in the datasheet. Still I'm not getting any reading from the RX pin. Can someone tell me where the mistake is found.
HT9032D.pdf (237 KB)
The mistake is your belief that the application circuit will work as shown in the datasheet. It’s a non-specific example with a non-existent program listing. It’s what we call a conceptual drawing. Holtek provides the concept, you provide the details. So far, you’ve provided no details.
sailek:
I am trying to connect HT9032D with arduino. The Dout pin is connected to the RX pin on the arduino. The circuit setup is exactly same as in the datasheet. Still I'm not getting any reading from the RX pin. Can someone tell me where the mistake is found.
With the limited information you have given, it's impossible for anyone to give an answer.
What code are you using?
Show us a schematic of how you have this all connected.
Do you actually have this connected to a land-line telephone circuit?
Is your program detecting the "ringing" of the telephone?
Paul
sailek:
I am trying to connect HT9032D with arduino. The Dout pin is connected to the RX pin on the arduino. The circuit setup is exactly same as in the datasheet. Still I'm not getting any reading from the RX pin. Can someone tell me where the mistake is found.
Well, I don't see anything in the datasheet regarding the protocol of either the DOUT or DOUTC outputs. So, to assume the protocol is TTL level RS232, might be an error.
Have a look at this Application Note from Holtek -- scroll down to the Serial Interface section at the bottom of the document -- that seems to be the most likely place to get insight on the protocol: http://www.holtek.com.tw/documents/10179/116745/an0053e.pdf
I searched the above document for the term "RS232" and found nothing, so this may be a proprietary protocol, and if so, you might have to roll your own receiver, in software.
BTW: are you seeing any kind of signal occurring at the DOUT or DOUTC outputs? That would at least give you an indication of whether or not this thing is decoding anything.
UPDATE: It looks like what this thing is doing is translating the FSK signal into a TTL bit stream. So, more than likely, the protocol information is all in sections regarding what it's receiving. I just briefly scanned the document, so I can't say for sure -- in depth reading is your job 
Before you can expect any data output this must occur:
This pin presents the output of the demodulator whenever CDET pin is low.
This data stream includes the alternate 1 and 0 pattern, the marking, and
the data. At all other times, this pin is held high.
So, check CDET to be low, which means the carrier was detected. With no carrier(tone), there is no data.
You still have not told us this is connected to a regular telephone line!!!
Paul
Paul_KD7HB:
With the limited information you have given, it's impossible for anyone to give an answer.What code are you using?
Show us a schematic of how you have this all connected.
Do you actually have this connected to a land-line telephone circuit?
Is your program detecting the "ringing" of the telephone?
Paul
It is connected to a regular telephone. And it is not detecting the "ringing". Actually I am using the 8 dip HT9032D which does not have a ringing detection.
sailek:
It is connected to a regular telephone. And it is not detecting the "ringing". Actually I am using the 8 dip HT9032D which does not have a ringing detection.
Ok, Do you see the 1700 Hz signal in your oscilloscope?
Is the chip still in power-down mode?
Paul
avr_fred:
The mistake is your belief that the application circuit will work as shown in the datasheet. It’s a non-specific example with a non-existent program listing. It’s what we call a conceptual drawing. Holtek provides the concept, you provide the details. So far, you’ve provided no details.
When my phone is idle it is 48.1 V. And i am using HT9032D 8 dip.
And i am using HT9032D 8 dip.
The data sheet has no such variant.
You can have a HT9032B 8 dip, or a HT9032F-A 8 dip, or a HT9032S 8 sop but not what you said.
Grumpy_Mike:
The data sheet has no such variant.You can have a HT9032B 8 dip, or a HT9032F-A 8 dip, or a HT9032S 8 sop but not what you said.
It is a HT9032D: 8-pin SOP package.
Dout is connected to pin 11 of arduino and Pdwn is connected to pin 10 of arduino.
The code is:
#include <SoftwareSerial.h>
SoftwareSerial mySerial(10, 11); // RX, TX
char SBUF0 = 0;
void setup()
{
Serial.begin(1200);
}
void loop()
{
Ht9032_get();
}
void Ht9032_get()
{
while (Serial.available() > 0)
{
//Serial.flush();
SBUF0 = Serial.read();
Serial.print(SBUF0);
}
}
I was also not able to open serial monitor
HT9032D.pdf (237 KB)
while (Serial.available() > 0)
You have nothing connected to the serial port you would have to use the mySerial port here, if indeed the chip provides you with asynchronous at 1200 baud.
Also you need to start it off with mySerial.begin
Grumpy_Mike:
You have nothing connected to the serial port you would have to use the mySerial port here, if indeed the chip provides you with asynchronous at 1200 baud.Also you need to start it off with mySerial.begin
I have done that but still not getting any results. I want to confirm whether Dout on HT9032D should be connected to the pin 10 on arduino.
I have done that but still not getting any results.
When you get to that point, it is customary to post your code so we can check if you have done it right.
I want to confirm whether Dout on HT9032D should be connected to the pin 10 on arduino.
It could be connected to any pin but the software looking at that pin might not of the right sort.
#include <SoftwareSerial.h>
#include <LiquidCrystal.h>
char SBUF0 = 0;
SoftwareSerial mySerial(10, 11); // RX, TX
LiquidCrystal lcd(12, 11, 5, 4, 3, 2);
void setup()
{
// Open serial communications and wait for port to open:
Serial.begin(9600);
mySerial.begin(1200);
lcd.begin(16, 2);
lcd.print("lcd");
// lcd.print(SBUF0);
}
void loop()
{
Ht9032_get();
Serial.print(SBUF0);
// lcd.setCursor(0, 1);
// print the number of seconds since reset:
//lcd.print(millis() / 1000);
}
void Ht9032_get()
{
while (mySerial.available() > 0)
{
//Serial.flush();
SBUF0 = Serial.read();
Serial.print((float)SBUF0);
lcd.print(SBUF0);
}
}
In my serial monitor, I obtain some symbols like "///////////////////////////////////////////////"
How do I convert into useful information.
Your Ht9032_get simply reads all the characters into the same variable until the buffer is empty and then returns the last character it read. You don't want to do that do you?
SoftwareSerial mySerial(10, 11); // RX, TX
LiquidCrystal lcd(12, 11, 5, 4, 3, 2);
Note you are using pin 11 for both those statements. I know you are not using TX but the code should set the pin high and this might interfere with the function of the LCD, so pick another unused pin for the TX definition ( don't pick 0 or 1 )
How do I convert into useful information.
We need to see it this indeed is what the chip is giving you in terms of serial data first before we see if the data is indeed asynchronous serial data.
Grumpy_Mike:
Your Ht9032_get simply reads all the characters into the same variable until the buffer is empty and then returns the last character it read. You don't want to do that do you?SoftwareSerial mySerial(10, 11); // RX, TX
LiquidCrystal lcd(12, 11, 5, 4, 3, 2);
Note you are using pin 11 for both those statements. I know you are not using TX but the code should set the pin high and this might interfere with the function of the LCD, so pick another unused pin for the TX definition ( don't pick 0 or 1 ) We need to see it this indeed is what the chip is giving you in terms of serial data first before we see if the data is indeed asynchronous serial data.
This time I removed the lcd display code from it. I do not get any results on the serial monitor when the phone rings. I wonder if the baud rate I set for Serial.begin(9600) is correct.
The Serial.begin just sets the baud rate for communication between the Arduino and the serial monitor. This can be anything providing both the Arduino and serial monitor are set to the right thing. It is the software serial that is critical as 1200 baud.
However unless you have corrected your code from the last code you posted to read the software serial correctly you are wasting your time looking at other things.
Check this out from a forum post I found at [Reddit - Dive into anything]:
I've successfully used the HT9032C chip (see: http://www.holtek.com/pdf/comm/9032v141.pdf
). It connects via UART pins (D0, D1) to the Arduino.
I can confirm it works in Canada but should work in USA too. I've read that many telcos in Europe use DTMF tones instead.