![]() Next: This creates loopback nullmodem so you can program against the data being sent from the first device. ![]() is a neat little program that sends data to a com port - so if you create a text file with data you expect to receive from your data collection device, you can set the params to make your interface think it's talking to your data collection device, without having the expensive(?) device in your hands. The concepts should be comparable if you use it for spreadsheet, etc.įirst: the testing environment. Note: I'm building my interface in OOO Base. Your use of the components is up to your tolerance level. I'm going to provide links to cost-free software, but they aren't GPL. While I know this is a VERY old topic, it is one that came up on searches for serial port interfaces, and there isn't a good answer. It was his pointing out the kB article which gave me the idea, so the honours really belong to ms777 The truth is that I've come back to this "No responses" Q a couple of times and couldn't think of an easy solution. WinXP et al) specific.Īnd an apology to ms777 for seeming to jump on his/her suggestion. Also read section 3 of the SDK which tells you how to call com components, but once you've done that using a COM component is really quite straight forward but unfortunately MS OS (e.g. One of the early hits was which seems to do what you want. However, since you can use COM controls through the UNO bridge, this got me thinking about simpler non-MS approaches and did a google on "com port vbscript" (since the programmatic approach is the same as writing a vbscript, but I'll get far more hits on vbscript than OOo Basic!). Net controls which should be accessible through the UNO bridge, and these will require you to download the relevant. There is a potential issue over legality / licensing. Do a google on "mscomm32.ocx download" for more information and avaialbility. The first uses the MSComm Control (MSCOMM32.OCX). As far as I understand this happens because the compiler interprets there is some components embedded into another related library which was already copied.If you read this article, it basically discusses two approaches. The problem happens because on being that parameter set as "true" the library was not being copied in to the "bin" folder during the compilation. vbproj file in the part where the library interop.MSCommlib is included (Reference Include="Interop.MSCommLib") and changed the parameter "EmbedInteropTypes" from "true" to "false". Consider changing the 'Embed Interop Types' property on either assembly. Vbc : warning BC40059: A reference was created to embedded interop assembly 'Interop.MSCommLib' because of an indirect reference to that assembly from assembly 'AxInterop.MSCommLib'. On compiling I could notice this warning: The error appeared on running time, not compilation time. ![]() ![]() ![]() I am not sure if this could help, but I had exactly the same error using Visual Studio 2013 with the library. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |