Home/ Questions/Q 5955651
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-22T18:08:39+00:00

I am developing Delphi application on Delphi 2010 XE RAD Studio under Windows 7.

  • 0

I am developing Delphi application on Delphi 2010 XE RAD Studio under Windows 7. My application talks on the serial port non-stop. I am using AsyncPro for Delphi 2010. Serial communication and everything else on the computer I develop with works great without any problem. However, when my release version of my application is run on another Windows 7 system, serial communication completely fails. We probed the serial communication itself for an answer and found out that Request to Send (RTS) line is not dropped right after sending all the bytes, whereas on my development computer RTS line is dropped correctly.

Even when I explicitly drop the RTS line to low or false state, RTS line doesn’t drop right away but after good 15 milliseconds. Thus, serial communication on my release version is failing.

Am I missing important information about Windows 7 and serial communication issues?

UPDATE: I just found the bug with my Aysncpro 5.0 for Delphi XE. It is weird. When my Delphi XE IDE is open or running, my program is communicating flawlessly. When I shutdown or close my Delphi XE IDE while my program is running, the same program doesn’t communicate very well or it times out.

Chime in if you have any idea why it is happening.

Any help will be appreciated.

Thank you,

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Sounds like a timer resolution problem to me. I had the same problem trying to write to a USB FTDI driver using an event based timer with timeSetEvent()… When Delphi loads, it changes the timer resolution to less than 20ms, which made my app work fine. When the IDE wasn’t running I couldn’t get things to work below 20ms +/- 5ms (the default Windows resolution I believe).

    To fix the problem, I call timeBeginPeriod(1) in the thread to set the minimum system wide timer resolution.

    I believe this affects the resolution of other time based events, because I get better than +/-5ms accuracy on other (non-multimedia timer) wait events in my app when I use timeBeginPeriod().

    So, what I’m suggesting is that somewhere in the AsyncPro code it’s using some time based event or call back… That would be affected by Delphi’s change to the timer resolution when it is loaded. Try calling timeBeginPeriod(1) somewhere in your app when it starts and see if there is a change.

    Oh, and don’t forget to call timeEndPeriod(1) when your app shuts down.

    N@

    • 0