Cloverleaf Migration Issue from 5.3 to 5.8

[Graham Hartley]

Hi,

I am currently in the process of migrating our interfaces from Cloverleaf 5.3 to 5.8 and have run into a problem that I am struggling to resolve or explain.  Both versions run on Windows Server 2003.

We have an old interface (developer left years ago) that enters data onto our PAS (Isoft Clinicom) system via telnet. This interface no longer works on the new version.  I think the problem is down to how Cloverleaf converts data from the pdl to an inbound Cloverleaf message.

Below are some logfile extracts to demonstrate…

From version 5.3 (working version)  

Code:

] input buffer accepted 15 bytes, now 15
]  ff fd 18 ff  fd 20 ff fd  |….. ..|
]  23 ff fd 27  ff fd 24     |#..’..$|

…..

[pd  :pdtd:INFO/3:     CLINICOM] [0.0.2478784] IB pre-SMS message details
msg: 0x008CA370
   msgType           : DATA
   msgClass          : PROTOCOL
   msgState          : Unknown: 0 (0)
   msgPriority       : 5120
   msgRecoveryDbState: 1
   msgFlags          : 0x2
   msgMid            : [0.0.2478784]
   msgSrcMid         : midNULL
   msgSrcMidGroup    : midNULL
   msgOrigSrcThread  : CLINICOM
   msgOrigDestThread :
   msgSrcThread      : CLINICOM
   msgDestThread     :
   msgXlateThread    :
   msgSkipXlate      : 0
   msgSepChars       :
   msgNumRetries     : 0
   msgGroupId        : 0
   msgDriverControl  :
   msgRecordFormat   :
   msgRoutes         :
   msgUserData       :
   msgStaticIsDirty  : 0
   msgVariableIsDirty: 0
   msgTimeStartIb    : 1327424203.369
   msgTimeStartOb    : 1327424202.822
   msgTimeCurQueStart: 0.000
   msgTimeTotalQue   : 0.000
   msgTimeRecovery   : 1327424202.822
   msgEoConfig       : 0x00000000
   msgData (BO)      : 0x008CA41C
   message           : ‘xff’

From version 5.8

Topic

[Boris Perov]

Have you tried switching the encoding from “ANSI” to “windows-1252”?

[Graham Hartley]

Thanks for your suggestion. I have tried changing the encoding on the thread to various types including windows-1252 and this has no effect.  I note that in version 5.3 there is no encoding dropdown.  

Unfortunatly I think the issue may be quite a complex one to solve!

[Boris Perov]

Hi Graham,

The encoding is one of the new “enhancements” that came along with the multi-byte changes in 5.8…

[Graham Hartley]

Thanks Boris,  I will give that a try and let you know how I get on.

[Russ Ross]

Just for grins I was curious if I could use hcitcptest to send hex values

From what I saw I think so.

I suspect hcitcptest could be helpful to give you control to generate your own hex messages and not have to wait around for the next hex message.

What I did to see if this works is to start a TCP/IP listener on port 13177 to receive raw data

Code:

hcitcptest -p 13177 -t nlf

Next I started a TCP/IP sender on port 13177 to send raw data

Code:

hcitcptest -h mdahub4 -p 13177 -t nlf

then I typed the following at the hcitcptest sender prompt

Code:

x23xffxfdx27xffxfdx24

and hit enter and this is what showed on the hcitcptest receiver

Code:

Got 7 bytes of data from host:
0x00000000 (00000)   23fffd27 fffd24                       #..’..$

Russ Ross
RussRoss318@gmail.com

[David Harrison]

Not sure I understand the problem but we have CliniCom and I

[Graham Hartley]

Thanks for all your help on this.  In the end changing the thread so that it uses windows-1252 encoding seems to resolve the problems I have been experiencing.  

David

[Author]

Replies