in reply to serial port hex only

1. Insufficient information
BUT...
2. why not have your script expect an ASCII representation and handle it in a way that allows the next function/process/line-of-code to treat it as hex... for which, prepending '0x' may suffice.

Replies are listed 'Best First'.
Re^2: serial port hex only
by ccherri (Acolyte) on Apr 26, 2012 at 21:37 UTC
    processing it once I get it back in the perl script is not the problem. What I need is bit level control of the serial port within my script. Perhaps win32::serialport is not the way to go...
      Have you looked at Win32API::CommPort? It provides the low level/raw access that Win32::SerialPort is built-upon. It's included with Wn32::SerialPort, so you should already have it.

      Elda Taluta; Sarks Sark; Ark Arks
      My deviantART gallery

        I doubt that this level of control (includes fiddling with control signals like RTS (Request to Send), CLS (Clear to Send), etc is needed. I think all that is needed here is binary data send/receive (not low level access to the flow control signals).

        A modern computer can keep up easily with the port, even at "high" baud rate settings.

        Also many of the computers nowadays have very limited RS-232 support and all of the flow control signals may not be even available! xon/xoff flow control is the way to go (if possible and needed) - however even no flow control at all is often fine!

        The serial port chip or emulator will have at least 16 bytes of buffer. If this is a simple request/response protocol (no asynchronous messages being used), the programming should be fairly straight-forward.

        RS-232 serial port communication is going the way of the dodo bird although it will "live" and be useful for a very long time.