-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ascii data receive from POS client processing #69
Comments
Hi! Which one do you expect? You may refer to toString() method specification here: https://nodejs.org/api/buffer.html#buffer_buf_tostring_encoding_start_end |
Hi Igor; |
I suggest you debug your logic, dump the contents of your Buffer object and see how source data corresponds to what stored inside object and where it may get skewed. |
H Igor,
Im facing an issue when using is SQ as server to accept POS transactions according to new logical i add.
But all POS sends ASCII /utf8array encoded message to SQ. At my end why i convert using .toString('hex'), the result is different than the one i excpected.
here is the result after hex convertion
16030100FFFD010000FFFD030312607EFFFD3A5DFFFD46FFFDFFFD5A6A614DFFFDFFFD350E4CFFFD5EFFFD4F4D53FFFDFFFD3E6C68FFFD00002EFFFD2BFFFD2CFFFD2FFFFD3000FFFD00FFFDFFFD09FFFD0AFFFD13FFFD140033003900320038FFFD07FFFD1100FFFD00FFFD002F00350005000400FFFD01000064000B000403000102000A00340032000E000D0019000B000C00180009000A00160017000800060007001400150004000500120013000100020003000F00100011000D0020001E060106020603050105020503040104020403030103020303020102020203
Kindly assist
The text was updated successfully, but these errors were encountered: