When you analyze the incoming data using the Port > Analyze window, you see the expected data output from your device. However, upon activating WinWedge, there appears to be no communication between the device and WinWedge.
The fact that you are getting data in the analyze window and not when the wedge is activated implies that the communication is established and the wedge is receiving data.
Check if data appears in the WinWedge window
The first thing you should check is whether or not the WinWedge Window (when Activated) is displaying your data. If the data appears there but not in your application, then check which Mode you are in (Keystrokes or DDE) and verify that the settings are correct. It is important to realize that setting WinWedge in DDE Server Mode will not result in the data being sent to any open Window like it can in Keystrokes mode. In Excel, for instance, you must write macros to actually manage the DDE transactions.
Test for application compatibility issues
There is also a small number of applications (such as applications that run in a DOS Window) that cannot receive the keystrokes from WinWedge. Try sending the data into Notepad to see if that works. If it does, then it could be an incompatibility with the application you are trying to send the data to.
Verify your record structure
If no data appears in the WinWedge Window when it is activated, then the record structure is not defined properly. To correct this problem, take another look at the data in the Analyze window and make sure that the “Start of Record Event” and the “End of Record Event” have been defined properly. By default, WinWedge expects a carriage return as the end of a record. This will appear in the Analyze window as a music note character. If you do not receive this character from your device, then it means that WinWedge received your data but is still waiting for this carriage return character to signify the end of the record before transmitting the data to your application. To correct the problem, change the end of record event to a time delay between records, a fixed number of bytes received or a character that your device does transmit such as an ETX.
Check field parsing and filters
If you are confident that your start and end of record events are correctly defined, make sure that you have selected the proper parsing and filtering parameters for each field. Check your delimiters or field lengths, and try removing any filters you set to see if that corrects the problem.
Increase buffer size for large records
Finally, if you are inputting very large data records, you may also need to increase the size of the serial input buffer. Last modified on November 5, 2026
