Windows 10: RS232 serial data

Using Gartrip to transfer data to and from old Garmin handheld GPS. This works fine on Windows 7 but not Windows 10. What can I do?

:)

 

serial data transmission through RS232 port between two PC

I need to transmit a data between two pc through RS232 port, give me steps to do that .

 

Transfer Serial data from Omega DP80 legacy hardware to computer

Can anyone provide me with some guidance on setting up a legacy serial connection on an Omega (brand) thermocouple display? I would like to use the serial data interface (Omega DP80-Ser) to reliably transfer an ASCII text string over RS-232 serial connection:RS232-NMC-100 - EasySync - D-Sub Cables - Kynix Semiconductor.

Additional information is listed below if you think you can help. Thank you for having a look at my question!

I purchased a lightly used Omega DP86T ( http://www.omega.com/pptst/DP80.html ) several months ago. The unit included several expansion cards:

• four 6-channel thermocouple cards
• a scaled voltage output cards which outputs a voltage proportional to a defined full-scale temperature for the channel that has been selected
• an RS232 card that outputs an ASCII text string that includes the device number, the value on the display, the units, and then some terminating characters (spaces, carriage returns, line feeds).

After I got the thermocouples setup and was confident that the unit was working well as a stand-alone temperature display I turned my sights to getting the serial communications working so that I could used the unit in conjunction with my computer as a temperature data logger. This, of course, is where the aggravation began.

The Omega manual ( http://www.omega.com/Manuals/manualpdf/M0511.pdf ) has a reasonable description of the serial card, installing it, and setting it up in two different areas:

• Page 2-21 talks about the layout of the card, installing it into the device, and the baud rate, word length, stop bits and parity settings.
• Page 3-44 goes into greater detail on the parameter settings settings and the ASCII output. There is a great deal of overlap between the two sections.

I currently have the Omega serial card setup for 4800baud, 8bit word length, 1 stop bit, and even parity.

I am using a few different free programs (Termite, RS232 Data Logger, and UltraMonitor) to scan the serial input to the computer.

Of course, I have a relatively new laptop that does not have a native RS232 port (no shock there, right?) so I bought the CablesToGo USB to DB25 RS232 converter. It was well reviewed a few different places by people that were trying to hook up legacy hardware to a modern computer. (Before anyone suggest it - no, this is NOT a parallel printer interface cable.)

Unfortunately, when I hooked the Omega temperature display up to the computer via the USB/RS232 converter I got gibberish transferred to the serial terminal program. I tried messing with the Windows Hardware settings for the COM port:

• I made sure they were exactly the same in the hardware manager; as on the Omega card; a in the logging software.
• I tried faster and slower baud rates, different word lengths, stop bits, and parity settings on the card.
• I tried different send/receive buffer sizes in the Windows hardware manager, and basically everything else I could think of.

Recently, I brought an old (2000) laptop home from work that still has a DB9 serial port. I connected the Omega box to the laptop with a DB9 to DB25 cable, verified the Windows settings and tried to run the data logging software but nothing happened.

This is interesting for one reason: When I was using my much newer laptop and the USB/RS232 cable the data logging software would record gibberish symbols. With the native serial port on the 12 year old laptop the system wont even handshake with the Omega box and therefore doesn't even generate the gibberish that the USB/RS232 cable did.

(For whatever it is worth, the RS232 cable by itself doesn't cause the software to log random characters.)

Most recently, I jumped pins 2&3 on the (25 pin) device end of the RS232 cable and verified that I can make a sent signal echo back to the terminal program. This test worked on but the old computer with native RS-232 interface and the new computer using USB/RS-232 adapter.

If I can't make the RS232 interface work I'll probably setup the scaled voltage output and feed that into an Arduino (or similar) so that I can get the computer interface as well as some closed loop control. So, all hope is not lost, but I'd still like to get the serial interface working - if only to win grudge match.

Any suggestions on software or hardware troubleshooting would be greatly appreciated. Thank you all.

 

Windows 10 serial on OEM


So I'll summarize steps made...

1. Saved serial number (taken with Belarc Advisory) from preinstalled (half chinese language) Windows 8.1 (don't know exactly the version, suspect Windows 8.1 with bing) on tablet
2. Formatted tablet
3. Tried to make a clean Windows 10 (HOME, HOME N and also PRO, everytime with the same result) install with ISO taken with MediaCreationTool, during install (and also after completing installation) it says that the saved serial is not valid
4. Tried to reinstall Windows 8.1 (ISO taken with MediaCreationTool again) HOME, it says that the serial is not valid

So i suspect that the saved serial, is from a WINDOWS 8.1 WITH BING OEM version and this kind of ISO is not accessible/downloadable anywhere (at least I can't find it, any suggestion?)

Still not tried SHOWKEY with that serial, I am in office now, and the serial is saved on a usb pen at home, will try this evening.

So I'm stucked but if everything is like I suspect, it's incredible. If I have a tablet/notebook/netbook with Windows 8 preinstalled, it seems that I can update to Windows 10 without problems, but if I want to make a clean Windows 10 install that serial is not valid...