Miro Hlozka

I'm switching to delphi from c++ builder. I am rewriting part of the application from C++ to Delphi. I use the CPortLib component for serial communication there the write and read function worked for me in C++ without problems. The pointer to the char array pointed to the data. for delphi the function is defined as: TcustomComPort.Write(void type, integer) function Write(Const Buffer, Count integer) TcustomComPort.Reade(void type@, integer) function Read(var Buffer; Count: Integer): Integer; The write / read functions give incorrect data. Can you advise how to enter the first parameter for the read / write function in Delphi? PS: if I use WriteLn, ReadLn and enter the data in a string, it works fine. Thank you for your response 🙂

Thank you very much, I will try :-)

Hi, I would like to ask you not to look at the problem I am solving now. Maybe you have already met something similar and you will be able to advise me. 2 different applications have been running on Windows XP for many years and also on - without any problems. 1.) When switching to Windows 10, Windows 10 will randomly terminate the application after any time without any error message. Both applications are on different PCs with different motherboards and with Windows 10 professional. 2.) Applications are written in C ++ Builder 5 and use ComPort library components by Dejan Crnil and Brian Gochnauer 3.) Application1 communicates via 3 to 5 serial ports, application 2 communicates via 7 serial ports 4.) Application 1 runs continuously and windows 10 professional closes it after a few days from the start of the application - - the time of running the program before it closes with windows is different. Now I have increased the PC memory from 8 to 16 GB and maybe it helped - but it has to be deployed in a real environment with the customer and then they will see. 5.) Application 2 runs for 16 hours. Windows 10 professional closes it after about an hour, sometimes after a few hours from the start of the application - the time of running the program before it closes with windows is different. Increasing the PC memory to 64 GB did not help here 6.) In the appendix I attach the AppCrash report for application 2 how it was pulled out by the system. Well thank you Miro Hlozka Report.wer Report1.wer Report2.wer

MadExcept is probably a very useful program This clarification: 1. serial communication runs in 7 threads for reception. 6 threads have the highest priority, 1 thread has the idle priority. In some of these threads, it is also easy to acknowledge received messages ACK, NAK, CAN ... 2. The transmission and calling device is in the transmission threade with priority normal. 😊

thank you for your answers. Not specified: 1. Serial ports are AXAGO - via PCIe bus. 2 pieces with 4x COM 2. in power seting, I have switched off the saving mode also for PCIe. 3. I tried to use MadExcept nothing reported. I simulated division by zero - MadExcept displayed an error and logged it. I'll try it with him again, should I cancel all my own exception handling? I have used MadExcept for the first time now, I have no experience with it.