Hi Paulo,
The device log which is accessible with the logcat command. For the mds log, if you got to:
You should see what looks like a list of items similar to this
| 01/21/2012 04:50:48 | /mds/json/procedure/submit/ |
0.7129s |
If you mouse click on the last item, which should be the last encounter you sent, it should drop down and you will see some additional lines similar to:
+0.489s openmrs.py:256 Validating permissions to manage sana queue
+0.491s openmrs.py:260 Got result {"status":"OK","code":"unspecified","message":"User has Manage Sana Queue privileges"}
+0.491s openmrs.py:267 Uploading procedure
+0.491s openmrs.py:279 Encoded parameters, checking files.
+0.491s openmrs.py:292 About to post to http://sana-demo.mit.edu:8081/openmrs/moduleServlet/moca/uploadServlet
+0.712s openmrs.py:294 Got result {"status":"FAIL","code":"unspecified","message":"Concept Undefined: (execute, Press button to calculate BP)"}
+0.712s openmrs.py:300 Done with upload
+0.713s api.py:307 API: RESULT = False
+0.713s json.py:229 Failed to register procedure: sp.pk -> 371, Concept Undefined: (execute, Press button to calculate BP)
What you are looking for is to see how far the message gets up the chain; i.e. did it actually make it to openmrs, fail at the mds level, no error on the server, etc. Let me know if you have more questions.
Eric