Epson TM-H6000IV-DT ePOS-Device XML Users Manual - Page 34

If Reconnecting to the TM-Intelligent when the Network was Cut Off, Device, Applic

Page 34 highlights

If Reconnecting to the TM-Intelligent when the Network was Cut Off If network communication with the TM-Intelligent is cut off, the client application will reconnect. By reconnecting, you can use the devices that were open without reopening them. Also, through the settings for opening, the data to be sent to the client application that occurred while the network was cut off can be received upon reconnection. The following sequence explains the message flow necessary upon reconnection and the necessary parameters. Applications ePOS-Device Device 1 : Establishment of TCP/IP connection() TCP connection to Socket I/F from the native application 2 : connect message(client_id=0001) Establish a communication path to ePOS-Device Service I/F 3 : open_device message(buffer=true) Response(data_id=1) 4.1 : device_data message(Data, data_id=2) 4 : Data occurred() Network is cut off 5 : Data occurred() 5.1 : Retains inside (data_id=3) 6 : Establishment of TCP/IP connection() connect message(client_id=0002) 7: reconnect message (new_client_id = 0002, old_client_id = 0001, received_id = 2) Response(OK) 8 : device_data message(Data, data_id=3) To open an unopen device from the client, be sure to send a message when closing the application. Also, in cases where you cannot send a message when closing the application, store the previous in the application's permanent memory beforehand, and upon the next start-up, use the previous to send a message. 34

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218

34
If Reconnecting to the TM-Intelligent when the Network was Cut Off
If network communication with the TM-Intelligent is cut off, the client application will reconnect. By
reconnecting, you can use the devices that were open without reopening them. Also, through the settings
for opening, the data to be sent to the client application that occurred while the network was cut off can
be received upon reconnection. The following sequence explains the message flow necessary upon
reconnection and the necessary parameters.
To open an unopen device from the client, be sure to send a <disconnect> message when
closing the application. Also, in cases where you cannot send a <disconnect> message
when closing the application, store the previous <client_id> in the application's permanent
memory beforehand, and upon the next start-up, use the previous <client_id> to send a
<disconnect> message.
ePO
S
-Device
Device
Applic
a
tion
s
1 : E
s
t
a
bli
s
hment of TCP/IP connection()
3 : open_device me
ssa
ge(b
u
ffer=tr
u
e)
Re
s
pon
s
e(d
a
t
a
_id=1)
2 : connect me
ssa
ge(client_id=0001)
TCP connection to
S
ocket I/F from
the n
a
tive
a
pplic
a
tion
E
s
t
a
bli
s
h
a
comm
u
nic
a
tion p
a
th to
ePO
S
-Device
S
ervice I/F
4 : D
a
t
a
occ
u
rred()
4.1 : device_d
a
t
a
me
ssa
ge(D
a
t
a
, d
a
t
a
_id=2)
Network i
s
c
u
t off
5 : D
a
t
a
occ
u
rred()
5.1 : Ret
a
in
s
in
s
ide (d
a
t
a
_id=3)
6 : E
s
t
a
bli
s
hment of TCP/IP connection()
connect me
ssa
ge(client_id=0002)
7: reconnect me
ssa
ge
(new_client_id = 0002, old_client_id = 0001,
received_id = 2)
Re
s
pon
s
e(OK)
8 : device_d
a
t
a
me
ssa
ge(D
a
t
a
, d
a
t
a
_id=3)