To display the data on a form or interacts with an object subject to access by other threads (in which case, you might consider locks or other exclusionary measures). Your data-receive function will be operating on a different thread, but that's not much of a problem unless your data-receive function attempts
well there IS some threading going on but it's largely invisible to you. users need only instantiate the SerialPort class, open a serial port, and attach their data-receive function to the event (i.e. My guess is that working with binary data across a serial port might pose a problem that I've never encountered, but I can tell you that Microsoft's SerialPortĬlass works exceptionally well when the data passed back and forth are printable strings, for instance. Now I should caution you that our experience is limited to passing strings back and forth. We work with instrumentation here, communicating with the devices over actual or virtual serial ports, or over a USB connection to embedded FTDI chips. > driver supports access to the core flash and bios part. > buffer for reading and writing ranges between 256 bytes and 8KB. > configurable x1, x2, and x4 command/address/data modes.
Well, since no one has replied to your post, I'll give it a try. > clock frequency, selectable 3-byte or 4-byte addressing and a.
0 kommentar(er)
