Page 2 of 3
Posted: Wed Jan 26, 2005 3:58 pm
by Klonk
Anotehr vote for possibility to access COM-ports
Posted: Wed Jan 26, 2005 4:09 pm
by RichardL
MVCom works well for me. I made a routine to search for an active port over the range COM0 to COM9 then interrogated each working port for my hardware's signature. No problems... but I seem to remember ports numbered above 9 could not be used... grey cell failure for details... getting old
Customers never know what ports they have and USB converters seem to make up their own numbers so a port search was a good idea.
Posted: Thu Jan 27, 2005 3:28 am
by kwag
Dano wrote:One more vote here for native com port I/O support .
I second that too
-Karl
Posted: Tue Jun 14, 2005 5:01 am
by Intrigued
Though I'm new to PB... I'm tossing in my vote for innate support in PB for COM port functions (procedures)

Posted: Tue Jun 14, 2005 8:58 am
by Klonk
In the meantime we coudl work with the MVCOM library (with windows)
Posted: Thu Jun 16, 2005 5:23 pm
by mlwhitt
yeah I could use Com port / serial port routines and commands for various controllers that I want to talk to.
Intrigued wrote:Though I'm new to PB... I'm tossing in my vote for innate support in PB for COM port functions (procedures)

Posted: Fri Jun 17, 2005 1:22 pm
by Flype
i'm agree. RS programming is still alive...
in my work, i need to drive some 'RS232' hardware like POS ( Point Of Sale system, Bank Card Reader, Cheque Printer ).
So i would be pleased to have a set of commands. :roll:
Posted: Fri Jun 17, 2005 8:11 pm
by BinoX
That'd be really useful for me too. I've wanted to write a hydraulics control system that works under windows xp. (My old one is DOS based and just doesn't want to run... plus I've lost the source code.. heh)
Posted: Sat Jul 16, 2005 1:19 pm
by mlwhitt
I've got to try the MVCom library, but I would love to see builtin serial support in 4.0. That would be totally awesome.
Posted: Tue Jul 19, 2005 8:58 am
by KlausS
Here is the next vote for native COM commands.
I work for a company that develops medical equipment. Mostly all of this equipment uses RS232 connections for programming, updating, configuration, service and other things.
The reason is that the RS232 interface is easy to use, well known, robust, secure and allows for longer cables. In addition this interface is supported by neary all microcontrollers.
No other protocol can be monitored as easy as the RS232 protocol just by using any or your favourit terminal program!

Posted: Tue Jul 19, 2005 10:53 am
by Psychophanta
There is another protocol much more professional and with more capabilities for distances between equipments, and others.
I'm talking about RS422.
It sounds wierd to me the use of RS232 for that instead RS422 or another different intefaced systems using USB, optical, parallel-fiberchannel, firewire...

Posted: Tue Jul 19, 2005 9:49 pm
by woki
I also vote for nativ COM commands and nativ USB handling.
Neither RS232 nor RS422 are protocols I think, they only describe the physical layer. It's up to the user to define his protocol. RS232 is as professional as RS422. Indeed RS422 more insensible to electric distortion and the better choice for long distances.
The MVCom library is fine, but only for windows. So nativ support would be a graete enhancement.
Posted: Fri Aug 12, 2005 9:51 pm
by SimpleMind
You can use serial communication commands from the WIN32API in PureBasic. It's as native as can be. The only thing you have to do is reading, thinking and coding. Think Forth!
Posted: Sat Aug 13, 2005 2:02 am
by woki
You can use serial communication commands from the WIN32API in PureBasic. It's as native as can be. The only thing you have to do is reading, thinking and coding. Think Forth!
That's what I do.
Nativ to PB and cross platform, I mean.
Posted: Sat Aug 13, 2005 8:20 am
by Dreglor
suposeably you can Write with this piece of assembly
p is the port address and n is the number to send out
althought it crashes here, im not sure why
not sure what input is thought