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

How to use .dll file in uVision? Please help me out

I need to make 51 controller communicate with one device, which takes ASCII command. In the CD coming with that device, there are some VC files and one *.dll file. My question is can I make it in C language since I'm using 51 controller? I don't have any clue on how to do this. Can anyone help me out? Thanks a lot!

Parents
  • "2. Your 'controller' needs to communicate over an RS232 link..."

    One thing to note is that your 8051 neither knows nor cares what is on the other end of the RS232 link (nor does it need to).

    As far as your 8051 is concerned, it just sends bytes (characters) to its serial port, and receives bytes from its serial port - where those bytes ultimately go to or come from is entirely irrelevant to the 8051.

    Therefore you can consider this in two levels:

    1. a low-level "driver" which simply handles the sending & receiving of bytes to/from the serial port.
    You can test this with a dumb terminal, or a terminal emulator (eg, Hypoterminal).

    2. an upper-level handler for the specific "protocol" used by the 3rd-party "device"

    Note also that the uVision simulator can use the PC COM: port for its simulated serial input and output - so you can run your code in the simulator, while using a real RS232 connection (on the PC's COM port) to your real 3rd-party "device"

Reply
  • "2. Your 'controller' needs to communicate over an RS232 link..."

    One thing to note is that your 8051 neither knows nor cares what is on the other end of the RS232 link (nor does it need to).

    As far as your 8051 is concerned, it just sends bytes (characters) to its serial port, and receives bytes from its serial port - where those bytes ultimately go to or come from is entirely irrelevant to the 8051.

    Therefore you can consider this in two levels:

    1. a low-level "driver" which simply handles the sending & receiving of bytes to/from the serial port.
    You can test this with a dumb terminal, or a terminal emulator (eg, Hypoterminal).

    2. an upper-level handler for the specific "protocol" used by the 3rd-party "device"

    Note also that the uVision simulator can use the PC COM: port for its simulated serial input and output - so you can run your code in the simulator, while using a real RS232 connection (on the PC's COM port) to your real 3rd-party "device"

Children
No data