Couple quick Qs about Socket Programming?
08-18-2009
, 04:07 AM
08-18-2009
, 08:29 AM
Quote:
Gimmick account ldo, but had a few questions about socket programming.
Basically I have some sort of machine that is controlled via a serial connection (does it matter if it's RS232 or RS485? pretty sure it's the latter). I need to write some cpp code that controls it. Basically how I assume this works is you just set the bits for what you want to do, and it does it.
Is this any different for either of the RS protocols? I'm hoping you just set the "COM1" or whatever to whichever port we're trying to use, and read/writing should be simple.
Sorry if this is mangled and vague, I'm learning it on the fly and would appreciate any tips you guys might have. I'm good on binary, hex and all of that, so I'm just mainly just worried with the protocol for actually reading and writing to and from the serial port. Hopefully it's not too complicated. Thanks!
Basically I have some sort of machine that is controlled via a serial connection (does it matter if it's RS232 or RS485? pretty sure it's the latter). I need to write some cpp code that controls it. Basically how I assume this works is you just set the bits for what you want to do, and it does it.
Is this any different for either of the RS protocols? I'm hoping you just set the "COM1" or whatever to whichever port we're trying to use, and read/writing should be simple.
Sorry if this is mangled and vague, I'm learning it on the fly and would appreciate any tips you guys might have. I'm good on binary, hex and all of that, so I'm just mainly just worried with the protocol for actually reading and writing to and from the serial port. Hopefully it's not too complicated. Thanks!
http://www.codeproject.com/KB/system/serial.aspx
http://tldp.org/HOWTO/Serial-HOWTO.html
IIRC, it's not even that hard to work with the chips directly if you have to.
Juk
08-18-2009
, 05:45 PM
08-21-2009
, 03:22 AM
Quote:
Not sure which OS your controlling machine will be running in, but if it's Windows or Linux then these should help:
http://www.codeproject.com/KB/system/serial.aspx
http://tldp.org/HOWTO/Serial-HOWTO.html
IIRC, it's not even that hard to work with the chips directly if you have to.
Juk
http://www.codeproject.com/KB/system/serial.aspx
http://tldp.org/HOWTO/Serial-HOWTO.html
IIRC, it's not even that hard to work with the chips directly if you have to.
Juk
Quote:
What is your target platform? Windows? Windows won't let you directly access the port unless you are writing virtual device driver in assembly language following strict Microsoft procedures.
Also there are many ready made (and free) socket mangling solutions coming with most development environments like Visual Cpp, Inprise Turbo Cpp, etc.
What exactly is the hardware you want to control/read? Does it have native drivers? Maybe you can search the internet and find the pin mapping if you really insist on low level access. Just a thought.
Also there are many ready made (and free) socket mangling solutions coming with most development environments like Visual Cpp, Inprise Turbo Cpp, etc.
What exactly is the hardware you want to control/read? Does it have native drivers? Maybe you can search the internet and find the pin mapping if you really insist on low level access. Just a thought.
It's a machine that comes with a dedicated computer. You connect to this computer via serial, which basically just waits for input via the buffer. So i'm assuming all I need to do is read from the buffer and write to the buffer. visual cpp on windows. I have the codes/switches of the controls I read/write so that's not really a problem.
A couple questions though:
I haven't tested the hardware yet, so if I cant find anything I'll just do trial and error.
1) To open the port, it says
Code:
serial.Open(_T("COM1"));
serial.Setup(CSerial::EBaud9600,CSerial::EData8,CSerial::EParNone,CSerial::EStop1);
serial.SetupHandshaking(CSerial::EHandshakeHardware);
2) As a convention, should I be sending the buffer binary or hex? It's expecting 32bit input I think. I'm assuming hex because binary would be tedious and unwieldy.
Hope these questions are really easy to answer, if it requires any research on your end don't bother. I'll keep googling or ask a dedicated coding forum. Thanks!
08-21-2009
, 07:46 AM
Quote:
2) As a convention, should I be sending the buffer binary or hex? It's expecting 32bit input I think. I'm assuming hex because binary would be tedious and unwieldy.
When sending it you will just need to send it in "chunks" the size the C++ send function is expecting (ie: single bytes, 16 bit words, 32 bit words or whatever it uses). I think it will most likely just take single bytes (or at least have an overload for it).
Juk
08-21-2009
, 12:41 PM