This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Write data in file using "fopen( )" in C51 - µVision2

Hello everybody giving a helping hand,

got me some trouble here. I was making a program that reads out the duty cycle of an ADXL202 sensor. Everything works, except the part were i want to print my data in a file using this :

 FILE *stream, *fopen();

                 if ( (stream = fopen(...)) != NULL)
                                 fscanf(stream,''%s'', string);

Ok this is were my problems start. The compiler gives me the error that he doesn't know this type FILE ore the function fopen (). This seems to be logical to me since i looked in my stdio.h header and found nothing really according to that declaration.
Is there a posibility that this is stored in another source file or does not exist???
Or .... how do i get my data's in a *.txt file ???

Thanks for the help i'm about to receive :))

P.S: Im using a 80C535 µC, sorry for not mantuening

Parents
  • "I think you missed my point."

    Some of it, yes!

    "if the M$ ODBC text driver can work directly on a text file, while the Hyperterminal is capturing data"

    But this is still not serial data direct into Excel, is it?
    This still requires running Hypoterminal and setting it up to capture the data - the OP doesn't want to do that.

    I think Dan's suggestion of the "Serial Wedge" is probably the best - whether this is a physical Wedge that goes in the keyboard line (but might be too slow?) or a "Virtual" wedge that works straight from the COM port...

    Or perhaps the M$ ODBC text driver can handle the COM port as a "file"...?

Reply
  • "I think you missed my point."

    Some of it, yes!

    "if the M$ ODBC text driver can work directly on a text file, while the Hyperterminal is capturing data"

    But this is still not serial data direct into Excel, is it?
    This still requires running Hypoterminal and setting it up to capture the data - the OP doesn't want to do that.

    I think Dan's suggestion of the "Serial Wedge" is probably the best - whether this is a physical Wedge that goes in the keyboard line (but might be too slow?) or a "Virtual" wedge that works straight from the COM port...

    Or perhaps the M$ ODBC text driver can handle the COM port as a "file"...?

Children