I have used SdpoSerial as the RS232 handler in a class which is used in a test application. In this I create the SdpoSerial component in code in the constructor of my class like this:. I keep track of various communication states in the FCommState variable (it is indicating the state in a state machine).
The problem I have is that even though I open a non-existing port the SdpoSerial does not indicate this. Following the Open method Active is true even though a completely bogus port number has been given! Why is this and how can I fix it? I need to know if the port is actually working or not.
The Serial Port and USB devices work with a serial protocol. Because the processor and thus programming languages all work on a parallel approach to data, access to these kinds of protocols is easier to be implemented on the software side. Serial Port Component For Lazarus Project. This is the latest DS18B20 1-Wire digital temperature sensor from Maxim IC. Reports degrees C with 9 to 12-bit precision, -55C to 125C (+/-0.5C).
Hi, Two things: a) if possible post a compilable (even better runnable) example. There are some detail missing that could hold the reason for your trouble. What leads me to. B) have you redefined 'Active' in your class and it is hiding the TSdpoSerial active property?
Paulo Costa - Lazarus mailing list. On 22:10, Bo Berglund wrote: I have used SdpoSerial as the RS232 handler in a class which is used in a test application. In this I create the SdpoSerial component in code in the constructor of my class like this:. I keep track of various communication states in the FCommState variable (it is indicating the state in a state machine). The problem I have is that even though I open a non-existing port the SdpoSerial does not indicate this. Following the Open method Active is true even though a completely bogus port number has been given!
Why is this and how can I fix it? I need to know if the port is actually working or not. HiTwo things: a) if possible post a compilable (even better runnable) example. There are some detail missing that could hold the reason for your trouble. The application is quite extensive now because it holds the complete syntax of the data acquisition equipment I woark towards.
So it is not really realistic to post it all. But it does work, it is just that the user gets no indication whatever if he selects a port that either does not exist or is already used by another application. In all of my RS232 experience in Delphi (been at it since 1996) it was always the case that the serial component barfed if one tried to open a non-existing or already open port. I have used several different ones and they all had a property similar to Active or Open, which showed the actual state even if they did not throw an exception on opening an erroneous port. Not so with SdpoSerial (or I have yet to find it). What leads me to.
b) have you redefined 'Active' in your class and it is hiding the TSdpoSerial active property? No, as I showed I only create the FComm object as a TSdpoSerial instance, then set its properties including Active. I have tested the program now in the original development PC (a VMWare virtual XP-Pro machine) and my Win7X64 laptop and as long as I use a physical com port all seems to work OK.
In the virtual machine it means mapping the laptop docking station COM1 into the VM. THen it works just fine.
But when I involve a USB connected serial port (which I have to do if I undock my laptop) I get all kinds of strange errors, basically no communications at all! I have two different ones but both are problematic (ATEN RS232USB and SUNIX 4-port ComHub). Do you know of any problems related to SynaSer via USB connected RS232 adapters on Windows7 or WindowsXP?
Right now I am moving the Lazarus application around to different computers (real and virtual) and different COM ports (real or USB connected) to try to figure out why it is so hard making it always work. And this is when I found that I tried ports that were already reserved for the virtual machine or actually unplugged without SdpoSerial saying anything about it. Bo Berglund Developer in Sweden - Lazarus mailing list. On Thu, 10 Feb 2011 00:38:56 +0100, Alex Kovacic wrote: Bo have a look at the TurboPower Async Professional project they have components (control of serial ports) that might be better suited for your project. Well, I use AsyncPro 4.07 on Delphi (Windows) in a lot of programs, so I know about it. But there are a few things that keeps me off AsyncPro for this project: 1) AP is very big and has way too many bells and whistles for me. I just want the RS232 communications running without any extras like TAPI, BBS:es etc.
A simple component like SdpoSerial looked OK to my needs. 2) The final target for the program I am developing is an embedded ARM system running Embedded Debian. I think I should be better off using what comes with FPC/Lazarus than a port of a product like AP to the FPC environment. I may be wrong, but those were my criteria for selecting SdpoSerial plus advice obtained here. Bo Berglund Developer in Sweden - Lazarus mailing list.
I have tested the program now in the original development PC (a VMWare virtual XP-Pro machine) and my Win7X64 laptop and as long as I use a physical com port all seems to work OK. In the virtual machine it means mapping the laptop docking station COM1 into the VM. THen it works just fine.
But when I involve a USB connected serial port (which I have to do if I undock my laptop) I get all kinds of strange errors, basically no communications at all! I have two different ones but both are problematic (ATEN RS232USB and SUNIX 4-port ComHub). Do you know of any problems related to SynaSer via USB connected RS232 adapters on Windows7 or WindowsXP? Right now I am moving the Lazarus application around to different computers (real and virtual) and different COM ports (real or USB connected) to try to figure out why it is so hard making it always work. And this is when I found that I tried ports that were already reserved for the virtual machine or actually unplugged without SdpoSerial saying anything about it. Please test your ports with: and see if the problem also appears with this application. Paulo Costa - Lazarus mailing list.
On 23:12, Bo Berglund wrote: I have tested the program now in the original development PC (a VMWare virtual XP-Pro machine) and my Win7X64 laptop and as long as I use a physical com port all seems to work OK. In the virtual machine it means mapping the laptop docking station COM1 into the VM. THen it works just fine. But when I involve a USB connected serial port (which I have to do if I undock my laptop) I get all kinds of strange errors, basically no communications at all! I have two different ones but both are problematic (ATEN RS232USB and SUNIX 4-port ComHub).
Do you know of any problems related to SynaSer via USB connected RS232 adapters on Windows7 or WindowsXP? Right now I am moving the Lazarus application around to different computers (real and virtual) and different COM ports (real or USB connected) to try to figure out why it is so hard making it always work. And this is when I found that I tried ports that were already reserved for the virtual machine or actually unplugged without SdpoSerial saying anything about it. Please test your ports with: and see if the problem also appears with this application. Paulo Costa Some questions: 1) How do I set the baudrate with this application?
2) What means 'Server' and 'Client' in the RS232 context? 3) Is there some form of use instruction too? I don't really understand it. Bo Berglund Developer in Sweden - Lazarus mailing list.
On 12:53 AM, Bo Berglund wrote: 1) AP is very big and has way too many bells and whistles for me. I just want the RS232 communications running without any extras like TAPI, BBS:es etc.
So just extract the code you need and make it run with Lazarus. This really would be great to have and on the long run could be distributed with Lazarus as a viable extension of the library. Let me know if I can be helpful with testing it.Michael - Lazarus mailing list. But when I involve a USB connected serial port (which I have to do if I undock my laptop) I get all kinds of strange errors, basically no communications at all! I have two different ones but both are problematic (ATEN RS232USB and SUNIX 4-port ComHub).
Do you know of any problems related to SynaSer via USB connected RS232 adapters on Windows7 or WindowsXP? Right now I am moving the Lazarus application around to different computers (real and virtual) and different COM ports (real or USB connected) to try to figure out why it is so hard making it always work. And this is when I found that I tried ports that were already reserved for the virtual machine or actually unplugged without SdpoSerial saying anything about it.
Dont know if its any help at all, but I am also having serial port problems using USB adaptors. I am developing under Ubuntu using synaser and have found that I can only connect to the port about once every 5 or so trys.
Cant say if it is directly related SynaSer/ USB adaptor though, as I dont have an onboard one to test against. Side notes - if I use 'serial port terminal' it connects every time. If I use 'cat /dev/ttyUSB0 /tmp/test.txt' it tends to not connect more than it connects (similar to synaser) Suggests it may be necessary to 'reset' the port somehow before using I have a small sample program for testing if anybody wants it SteveG - Lazarus mailing list. Some questions: 1) How do I set the baudrate with this application? 2) What means 'Server' and 'Client' in the RS232 context? 3) Is there some form of use instruction too? I don't really understand it.
Thata was only to see what happens when you try to open a 'bad' COM port. This application also uses the SdpoSerial component. So, I wanted to know it it also exhibits the problem that you described. Paulo Costa - Lazarus mailing list. On 12:53 AM, Bo Berglund wrote: 1) AP is very big and has way too many bells and whistles for me.
I just want the RS232 communications running without any extras like TAPI, BBS:es etc. So just extract the code you need and make it run with Lazarus. This really would be great to have and on the long run could be distributed with Lazarus as a viable extension of the library. Let me know if I can be helpful with testing it. Concerning AsyncPro extraction: I once (4-5 years ago) tried to isolate the files needed by the serial port component by copying file after file to a directory included in the library path of Delphi from the AsyncPro source dir, which I removed from library path. Then I made a syntax check to see what was missing etc.
After a while I gave up because it looked like I would need more than 50% of the original files or maybe even all of them.:-( So it is not really possible to isolate just the port. Bo Berglund Developer in Sweden - Lazarus mailing list. On 06:47, Bo Berglund wrote: Some questions: 1) How do I set the baudrate with this application? 2) What means 'Server' and 'Client' in the RS232 context?
3) Is there some form of use instruction too? I don't really understand it.
Thata was only to see what happens when you try to open a 'bad' COM port. This application also uses the SdpoSerial component. So, I wanted to know it it also exhibits the problem that you described.
After I was having the problems with the long list of errors I now see only some maybe 'normal' messages when I am trying com ports that are already in use. The dialog offers to 'kill' the application, which I think is a bit on the extreme side for entering a wrong number. But it appears to be inside the SdpoSerial component because I get the same dialog if I try with my program. I have not been able to again trigger the strange window I saw the other day, though. Bo Berglund Developer in Sweden - Lazarus mailing list. But when I involve a USB connected serial port (which I have to do if I undock my laptop) I get all kinds of strange errors, basically no communications at all!
I have two different ones but both are problematic (ATEN RS232USB and SUNIX 4-port ComHub). Do you know of any problems related to SynaSer via USB connected RS232 adapters on Windows7 or WindowsXP? Right now I am moving the Lazarus application around to different computers (real and virtual) and different COM ports (real or USB connected) to try to figure out why it is so hard making it always work. And this is when I found that I tried ports that were already reserved for the virtual machine or actually unplugged without SdpoSerial saying anything about it. Dont know if its any help at all, but I am also having serial port problems using USB adaptors.
I am developing under Ubuntu using synaser and have found that I can only connect to the port about once every 5 or so trys. Cant say if it is directly related SynaSer/ USB adaptor though, as I dont have an onboard one to test against. side notes - if I use 'serial port terminal' it connects every time. if I use 'cat /dev/ttyUSB0 /tmp/test.txt' it tends to not connect more than it connects (similar to synaser) Suggests it may be necessary to 'reset' the port somehow before using I have a small sample program for testing if anybody wants it It is very strange how Windows handles the com ports. Somehow there seems to be some hidden deeper issues that makes some components not work in some situations.
Examples: We used a 3rd party serial component in Delphi for many years without real problems (WinNT4, Win95, Win2000 and now XP). But then we encountered a case where the component simply would not trigger any reception events. This happened on a Panasonic wireless gadget that was an extension of a WinXP PC with a touch screen and a few extras like a serial port. We used the serial port for an RFID reader and it simply would not read. If I added a timer and let it poll the component for data then I could make it work for this simple case, but that was a real kludge. So then I modified the program to use AsyncPro instead and it started working.
Don't know why the difference. Later, around 2008, I had another problem with an automation program communicating with a machine tool via RS232. At that time I.was. using AsyncPro, and it worked just fine on my laptop when connected to the machine.
But the same software running on the customer's PC:s refused to communicate. These PC:s had.real.
com ports and were running XP. So as a test I switched this program over to using the old serial component we used before, and amazingly then it worked just fine! Now I have problems with USB attached serial ports and lazarus programs using SdpoSerial as described in this thread. In this case the comm works fine as long as I use the.real.
com port in my docking station. But won't work if I use one of the 4 com ports in my newly bought SUNIX ComHub UTS2009P4 or for that matter if I use a USB single channel com port adapter from ATEN. But the latter can be used if it is not transferred to the virtual machine where I develop the software. Really very confusing, and I was not planning on doing research into this. I was programming a comm application for data collection. Do you think there is any chance of using my old serial component (housed in a single pas file) with lazarus?
It is a Delphi component and I don't know what you need to do in order to use it with lazarus. I realize that it would not work as a cross-platform unit but could be interesting for testing. In the end of course what I need to do is to get it working on the embedded ARM system with Linux. Bo Berglund Developer in Sweden - Lazarus mailing list.
On 08:47 PM, Bo Berglund wrote: After a while I gave up because it looked like I would need more than 50% of the original files or maybe even all of them.:-( So it is not really possible to isolate just the port. Of course this is not doable just on a file base. But I suppose you can delete some 90% of the code lines to get a working basic package. I would do that with Delphi: - create a simple working example - so you know which files are necessary (you say some 50%) - look what active code gets actually lines get compiled in and 'ifdef out' the code sequences that are not compiled. locate the header definitions that are not necessary and 'ifdef out' - locate the unit definitions that are not necessary and 'ifdef out' - now supposedly you can remove some files - now there might be stuff that gets compiled because the code 'might' use it, but from your project you do know that it will not happen. This can be 'ifdef out' with a little bit more effort.Michael - Lazarus mailing list. Now I have problems with USB attached serial ports and lazarus programs using SdpoSerial as described in this thread.
In this case the comm works fine as long as I use the.real. com port in my docking station. But won't work if I use one of the 4 com ports in my newly bought SUNIX ComHub UTS2009P4 or for that matter if I use a USB single channel com port adapter from ATEN. But the latter can be used if it is not transferred to the virtual machine where I develop the software. Really very confusing, and I was not planning on doing research into this. I was programming a comm application for data collection.
UPDATE: Now I think I have solved the connectivity issue via the USB-Serial converter so I can move on with the lazarus software development! I suspected the Windows driver for the ComHub so I downloaded the latest one from SUNIX, but that did not solve the problem. In Device manager I let Windows 7 try to update the driver from the web, but it told me that the driver was up-to-date at version 3.3.5.something Then I tried googling on 'prolific usb-to-rs232' which shows up in device manager as the driver used by the ports. And I found a number of hits that led to a website at Prolific itself (the chip manufacturer) and there it was possible to download a driver with version 3.3.11.152. After installing this and rebooting the laptop it now seems like the ports are working as intended! So the fact that the hardware supplier does not have the latest driver and Windows Update does not know of a later one seems not to mean that one does not exist.
In this case it is a revision step from 5 to 11 no less and this did the trick. On Windows7X64 that is.
Bo Berglund - Lazarus mailing list.
Hi All, I have been using BCB6 and TurboPower Async Pro for almost ten years now. The majority of my programs require support for serial ports. Recently, I decided to upgrade to C Builder 2010.
Much to my dismay, I then discovered that Async Pro does not work with CB 2010. My CB 2010 now sits collecting dust. There seem to be several issues at play here. One is Unicode. Another is the that all the current supporters of Async Pro are Delphi guys.
Another problem is that CB 2010, unlike BCB 6, does not compile Delphi packages. I don't understand all the details but it seems clear that Async Pro is a dead end for C Builder programmers. I would like to know if there are other packages out there that are known to work with CB 2010, preferably ones that don't cost hundreds of dollars.
Also, does anyone know why, after all these years, Borland/Emvbarcadero has never provided serial support? Thanks for any help.
Daniel Bissett. Hi All, I have been using BCB6 and TurboPower Async Pro for almost ten years now. The majority of my programs require support for serial ports. Recently, I decided to upgrade to C Builder 2010.
Much to my dismay, I then discovered that Async Pro does not work with CB 2010. My CB 2010 now sits collecting dust. There seem to be several issues at play here. One is Unicode. Another is the that all the current supporters of Async Pro are Delphi guys. Another problem is that CB 2010, unlike BCB 6, does not compile Delphi packages. I don't understand all the details but it seems clear that Async Pro is a dead end for C Builder programmers.
I would like to know if there are other packages out there that are known to work with CB 2010, preferably ones that don't cost hundreds of dollars. Also, does anyone know why, after all these years, Borland/Emvbarcadero has never provided serial support?
Thanks for any help. Daniel Bissett That's a question that much other people does. The only people that uses CB instead of Visual C or GNU in the business sector I work are those related to hardware stuff that needs communicate with a PC, for example utilities to save configuration in boards and/or vending machines with a PC into them and so.
All people has solved their way. Some had done a simple component. Other uses a class that encapsulates CreateFile/WriteFile/ReadFile stuff, other uses old MSCOMM OCX control, but all does it as a temporary solution until 'borland' will add a serial port component. Rafael Ontivero wrote: That's a question that much other people does. The only people that uses CB instead of Visual C or GNU in the business sector I work are those related to hardware stuff that needs communicate with a PC, for example utilities to save configuration in boards and/or vending machines with a PC into them and so. I work in broadcasting and television and spend my time getting different pieces of equipment to talk to each other.
Believe me, serial communication is NOT dead. A public example of my work can be found here: Rafael, thanks for your support. Rafael Ontivero wrote: That's a question that much other people does. The only people that uses CB instead of Visual C or GNU in the business sector I work are those related to hardware stuff that needs communicate with a PC, for example utilities to save configuration in boards and/or vending machines with a PC into them and so.
I work in broadcasting and television and spend my time getting different pieces of equipment to talk to each other. Believe me, serial communication is NOT dead.
A public example of my work can be found here: Rafael, thanks for your support. Hi All, I have been using BCB6 and TurboPower Async Pro for almost ten years now. The majority of my programs require support for serial ports. Recently, I decided to upgrade to C Builder 2010. Much to my dismay, I then discovered that Async Pro does not work with CB 2010. My CB 2010 now sits collecting dust.
There seem to be several issues at play here. One is Unicode.
Another is the that all the current supporters of Async Pro are Delphi guys. Another problem is that CB 2010, unlike BCB 6, does not compile Delphi packages. That may be true, but only if you do not have RAD Studio, and only from within the IDE. You're not at a dead-end. CB2010 comes with a Delphi compiler, so it should be able to compile Delphi packages from the command line. I do not have CB2010, so I cannot confirm that 100%, but it seems likely (every previous version of CBuilder has included a Delphi compiler that could compile Delphi packages). However, even if you cannot compile Delphi packages, you can compile CBuilder packages, and since CBuilder packages can contain Delphi source code, if yiou had to, you could create a CBuilder package that contains the AsyncPro source code and build it that way.
Dennis Jones wrote: That may be true, but only if you do not have RAD Studio, and only from within the IDE. What I did was to download the demo version of RAD Studio and install Async Pro. It compiled correctly and the components loaded into the Delphi IDE. However, I could do nothing to get the components loaded into the C Builder IDE. While the issue of CB2010 being able to compile Delphi code is an obstacle, it is not the only problem. I really don't want to be thought of as someone who throws stones at open source developers.
They do a great deal of work and they do it without compensation. The Async Pro developers should be applauded for their efforts. A great number of Delphi users are dependent on and happy with their efforts. In spite of this, it is clear that their resources are too limited to support the C side. Dennis Jones wrote: Probably because it is not trivial and because companies like TurboPower and Greenleaf had already done a good job of it, so why re-invent the wheel? However, now that AsyncPro is in the public domain, it could easily become part of normal Delphi/CBuilder releases (like they are doing with Boost).
If Embarcadero were to add the component to the releases, it would imply at least some level of commitment to assisting the open source developers. The packages would at least have to be kept up to date to work with with the current release.
The current problem is that this has failed to happen on the C side. I think this would be great for the users but Embarcadero would have to decide if they have the time (spoken money) to make this commitment. My original question still stands; What can I use today? Daniel Edited by: Bissett Daniel on Jun 19, 2010 12:32 PM. What I did was to download the demo version of RAD Studio and install Async Pro. It compiled correctly and the components loaded into the Delphi IDE.
However, I could do nothing to get the components loaded into the C Builder IDE. While the issue of CB2010 being able to compile Delphi code is an obstacle, it is not the only problem. Did you try to set the 'Linker output' option for the Delphi compiler to 'Generate all CBuilder files (including package libs)'? If you change that setting after the package was installed once, you'll probably need to clear the package cache (a long-standing bug): - Moritz 'Hey, it compiles!
Dennis Jones wrote: That may be true, but only if you do not have RAD Studio, and only from within the IDE. What I did was to download the demo version of RAD Studio and install Async Pro.
It compiled correctly and the components loaded into the Delphi IDE. However, I could do nothing to get the components loaded into the C Builder IDE. While the issue of CB2010 being able to compile Delphi code is an obstacle, it is not the only problem. I really don't want to be thought of as someone who throws stones at open source developers. They do a great deal of work and they do it without compensation.
The Async Pro developers should be applauded for their efforts. A great number of Delphi users are dependent on and happy with their efforts. In spite of this, it is clear that their resources are too limited to support the C side. Dennis Jones wrote: Probably because it is not trivial and because companies like TurboPower and Greenleaf had already done a good job of it, so why re-invent the wheel? However, now that AsyncPro is in the public domain, it could easily become part of normal Delphi/CBuilder releases (like they are doing with Boost).
If Embarcadero were to add the component to the releases, it would imply at least some level of commitment to assisting the open source developers. The packages would at least have to be kept up to date to work with with the current release. The current problem is that this has failed to happen on the C side. I think this would be great for the users but Embarcadero would have to decide if they have the time (spoken money) to make this commitment.
My original question still stands; What can I use today? Daniel Edited by: Bissett Daniel on Jun 19, 2010 12:32 PM Did you ever resolve this? Think in similar position (BCB6 and async pro for god knows how long), and utterly annoyed to say the least that it's not in CB2010. Think i'm going back to my bcb6. I have been using BCB6 and TurboPower Async Pro for almost ten years now.
The majority of my programs require support for serial ports. Recently, I decided to upgrade to C Builder 2010. Much to my dismay, I then discovered that Async Pro does not work with CB 2010. My CB 2010 now sits collecting dust.
There seem to be several issues at play here. One is Unicode. Another is the that all the current supporters of Async Pro are Delphi guys. Another problem is that CB 2010, unlike BCB 6, does not compile Delphi packages. I don't understand all the details but it seems clear that Async Pro is a dead end for C Builder programmers. I would like to know if there are other packages out there that are known to work with CB 2010, preferably ones that don't cost hundreds of dollars.
Also, does anyone know why, after all these years, Borland/Emvbarcadero has never provided serial support? ComPort component supports CB 2010 erik salaj. I have been using BCB6 and TurboPower Async Pro for almost ten years now.
The majority of my programs require support for serial ports. Recently, I decided to upgrade to C Builder 2010.
Much to my dismay, I then discovered that Async Pro does not work with CB 2010. My CB 2010 now sits collecting dust. There seem to be several issues at play here. One is Unicode. Another is the that all the current supporters of Async Pro are Delphi guys.
Another problem is that CB 2010, unlike BCB 6, does not compile Delphi packages. I don't understand all the details but it seems clear that Async Pro is a dead end for C Builder programmers. I would like to know if there are other packages out there that are known to work with CB 2010, preferably ones that don't cost hundreds of dollars. Also, does anyone know why, after all these years, Borland/Emvbarcadero has never provided serial support? ComPort component supports CB 2010 erik salaj I have the same problem as the OP. I am trying to install AsyncPro, which is now apparently available only in Delphi source format.
I am using a trial version of RAD Studio XE. I can't figure how to start the Delphi compiler (or even if there is one as part of the program, despite the fact that the product description says there is). It's possible that I did the installation wrong but I don't recall any compiler choices there.
If I try to compile with the IDE I get a 'missing Delphi.personality' message. I attempted the command line approach but the trial version doesn't seem to support command line compiling. I am completely at a loss. I will buy the Studio package if I can figure how to get this package installed- it's mandatory since my applications are serial/usb intensive. I am trying to upgrade from C Builder5 and AsyncPro 3, which has worked well in the past but is getting dated, plus when I try to use the 'build with run time packages' option I am now getting access violations for some reason.
Any help would be most appreciated. I have also tried the ComPort utility from Winsoft as described in the previous post. All I really need is a com port object, no fax, TCP/IP, etc, so this tool would suffice in place of Async Pro. However, after installation, the ComPort item shows up checked in the 'install packages'-design packages window, but no trace of the ComPort item where it's supposed to be in the 'System' palette area of the tool box.
I am probably doing something wrong, the IDE has changed a lot since CBuilder 5. I should also note that the first time I installed Comport, it apparently installed the tool in the earlier CBuilder 5 program (successfully I think, it showed up in the tool box). I then uninstalled version 5 and comport, re-installed comport, but still no comport tool in the toolbox in XE.
Very frustrating, I've been stalled for days and any help would be a huge relief. Thanks, Harry. Gents, I too found myself in the position of going on using CBuilder 6 and the free Turbopower serial port component for much longer than I expected. I had a couple of warnings about this cosy state of affairs. The first being that after getting XE I could not load the Turbopower component.
I also could not load the Turbopower component into CBuilder 6 when installed on Windows 7 (my company is shortly to move to this OS). So I thought I should come up with a solution. I created a class in a thread which allows the creation of multiple COM ports in an application. There is a project here: Which gives an example of a simple app with 2 COM ports. You will need to change the code for the COM ports on your PC. Once you have done this you can send a message by pressing the button. Just connect pins 2 & 3 on your serial port and you can stream data.
Full source code is provided. I hope you find this of some assistance. Simon Quin wrote: Which gives an example of a simple app with 2 COM ports. You will need to change the code for the COM ports on your PC. Once you have done this you can send a message by pressing the button.
Just connect pins 2 & 3 on your serial port and you can stream data. Full source code is provided. I hope you find this of some assistance. Hi Simon, Thanks for sharing your work.
I am using C XE5, and when running your project I get this error: bcc32 Error EthernetThreadtestMain.cpp(8): E2209 Unable to open include file 'EnetThread.h' any idea? I have also tried the ComPort utility from Winsoft as described in the previous post. All I really need is a com port object, no fax, TCP/IP, etc, so this tool would suffice in place of Async Pro. However, after installation, the ComPort item shows up checked in the 'install packages'-design packages window, but no trace of the ComPort item where it's supposed to be in the 'System' palette area of the tool box. I am probably doing something wrong, the IDE has changed a lot since CBuilder 5.
![]()
I should al so note that the first time I installed Comport, it apparently installed the tool in the earlier CBuilder 5 program (successfully I think, it showed up in the tool box). I then uninstalled version 5 and comport, re-installed comport, but still no comport tool in the toolbox in XE. Very frustrating, I've been stalled for days and any help would be a huge relief. Check, whether Winsoft ComPort Component package is enabled (menu Component/Install packages), try to switch off another ComPort components 2.
ComPort component could be placed on another component palette 3. Check, whether comportp.bpl package was created. Compilation uses dcc32 command line compiler when installing component. Some C Builder editions may not contain this compiler, in this case compile the package manually - directly in C Builder IDE. Erik Salaj, WINSOFT.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |