New device drivers

Forum Home › Forums › Development and Integration › New device drivers

Tagged: 

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • February 11, 2021 at 12:00 pm #8283
    fedex
    Participant

    Hi,
    i want to develop a new device drivers.
    I want to know how to do the debug tests from VisualStudio?
    Thanks for the support.

    February 11, 2021 at 2:32 pm #8284
    Mikhail
    Moderator

    Hi,

    An article

    Driver examples

    To debus a DLL, you need to attach to the process that uses the DLL. In case of drivers, attach debugger to ScadaComm.exe

    February 11, 2021 at 3:42 pm #8285
    fedex
    Participant

    Hi,
    thanks for article and examples.
    Where do I find ScadaComm.exe, and how do I attach the dll to the process?
    Thanks for the support.

    February 12, 2021 at 8:10 am #8286
    fedex
    Participant

    Hi,
    I attach the dll to the process ScadaCommSvc.exe.
    Thanks for the support.

    February 12, 2021 at 2:35 pm #8287
    Mikhail
    Moderator

    OK

    August 5, 2022 at 11:17 am #10448
    Singapore
    Participant

    I attached the DLL process of the new driver to scadacommsvc.exe in the debug directory, scadacommsvc Exe is registered as a service. However, the breakpoint in the DLL is invalid. The prompt: the breakpoint will not be hit at present, and no symbols have been loaded for the document。What are the detailed steps of using VisualStudio to debug the driver?

    August 6, 2022 at 7:29 am #10452
    Mikhail
    Moderator

    You should build your DLL in the Debug configuration in VS. Then copy to the Communicator installation directory.

    What are the detailed steps of using VisualStudio to debug the driver?

    There is no special tricks for Rapid SCADA debugging. Search for general info how to debug dlls.

    August 6, 2022 at 8:20 am #10454
    Singapore
    Participant

    Hello, thank you very much for your reply. Can I understand that the newly developed driver DLL can not be debugged in the administrator application source code debugging mode, but can only create a new solution to debug the DLL separately or copy the DLL to the communicator installation directory? I wonder if there is any way to debug DLL in the administrator application source code debugging mode? Thank you very much for your support.

    August 8, 2022 at 8:28 am #10455
    Mikhail
    Moderator

    Hello,
    1. Run Visual Studio as administrator.
    2. Open the solution that contains the driver.
    3. Switch VS to Debug configuration and build the driver.
    4. Copy the created driver DLL to Communicator.
    5. Configure and start Communicator service.
    6. Attach to Communicator process from VS.

    August 8, 2022 at 10:10 am #10456
    Singapore
    Participant

    Hello, thank you very much for your answer. According to the steps provided by you, I can debug the DLL program normally. Thank you for your support.

  • Author
    Posts
Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.