-
```
What steps will reproduce the problem?
1. p = ISO8583()
2. p.setBit(18, 6011)
3. v1 = p.getBitsAndValues()
What is the expected output? What do you see instead?
6011 , 0046011
What version of t…
-
```
If is in ASCII then there is a way to send in HEX?
```
Original issue reported on code.google.com by `cbay...@i2c-net.com` on 6 May 2015 at 9:02
-
```
Here is the 0820 message that I generated. Notice that I omitted the length and
that the first 4 bytes are the MTI. (this string wear produced with pprint().
'0820\x82
\x00\x00\x00\x00\x00\x00\…
-
```
What steps will reproduce the problem?
1. I have an implementation of ISO 8583 on .net on a microsoft server
2. I'm making a advance monitoring of the service by F5 LTM.
3. I want to now if there …
-
bignum tostring do not support base 2
Error: Error unpacking data from bit 1
Packager: { length: 16, name: 'Bitmap', type: 'b' }: Invalid base, only 10 and 16 are supported
-
```
I have a requirement to create an ISO8583 message where the private data field
127 has certain subfields populated, in this case 127.22 specifically.
This requires me to create a bitmap for fiel…
-
```
According to ISO8583 standard, the secondary bitmap is optional. This issue
make nucleus8583 unable to unpack message if the secondary bitmap is off.
```
Original issue reported on code.google.c…
-
```
Q1:ISO8583 structure problem
ISO8583 is the structure : msg-len+TPDU+MSG
I test your module. I do not find it(TPDU).
Q2: ISO8583 sending message:
1.msg_len is nible type
2.MTI is nible ty…
-
```
Q1:ISO8583 structure problem
ISO8583 is the structure : msg-len+TPDU+MSG
I test your module. I do not find it(TPDU).
Q2: ISO8583 sending message:
1.msg_len is nible type
2.MTI is nible ty…
-
```
Q1:ISO8583 structure problem
ISO8583 is the structure : msg-len+TPDU+MSG
I test your module. I do not find it(TPDU).
Q2: ISO8583 sending message:
1.msg_len is nible type
2.MTI is nible ty…