Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Problems with MSComm control
Message
De
14/06/2001 05:13:29
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Contrôles ActiveX en VFP
Divers
Thread ID:
00515479
Message ID:
00519208
Vues:
22
>>What are the non default settings of the control? What are you doing with the DEC response?
>
>Non-default settings: DTREnable is set to .T. EOFEnable is set to .T. (haven't seen this make a diefference no matter how it is set. Handshaking is set to 1 (XOn/XOff). InputMode is set to 0 (text). NullDiscard is set to .T. ParityReplace is set to (None). RThreshold is 1, SThreshold is 1, Settings is 9600,n,8,1.
>
>Just grabbing the response (from the input property) and sticking it in an editbox. Unfortunately, it just shows that I printed some control characters on the screen. Thanks Jim,
>John

Since your RThreshold is 1, I'm assuming you are using event driven processing. Let me see your Oncomm event code.

Will your cabling/DEC hardware support CTS/RTS hand shaking? Not your problem, just the way I like to do things.

Since I can't see any extra data on the wire here, I think I would try and parse the data returned and see exactly what the DEC is responding with. The garbage in an edit box is not very useful. See if you can determine what exact control sequence is returned.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform