Maybe use wait(13) to check the string textline for CR and then decide what was received?
Something like ARRAYREAD textline,not_cr_found,[wait(13)]
will jump to not_cr_found. So 8 bytes were received that were not a CR.
Have not tested.
Ioannnis
|
Re: Determining which command caused SERIN2 to trigger?
Maybe use wait(13) to check the string textline for CR and then decide what was received?
Something like ARRAYREAD textline,not_cr_found,[wait(13)]
will jump to not_cr_found. So 8 bytes were received that were not a CR.
Have not tested.
Ioannnis
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks