Questions? Search our site or call us at 1-800-722-6004

Data appears in Analyze window but does not show up after activation

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.

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 realise that Setting the Wedge for DDE 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.

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 and see if that works, if it does then it could be an incompatibility with the application you are trying to send the data to.

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.

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.

Finally, if you are inputting very large data records, you may also need to increase the size of the serial input buffer.

Categories: Troubleshooting

Last Updated: 2011.07.05

Need more help?

Don't hesitate to call or email us with your questions

Our office is open 9AM - 5PM Monday Through Friday (E.S.T.)

Technical Support: 215-496-0202

Toll-Free: 1 (800) 722-6004
Skype: taltech1 (Voice only)