Forum Replies Created
-
Posts
-
Perhaps the PIN setting is wrong – some OSs will default to 0000 without asking? The correct PIN for the lung monitor is 8158
/Jacoband probably not available to the public…
On a second thought, I found that the Monica -> Milou communication seems to be using a protocol defined by Philips. Try Googleing "Philips series 50 CTG Protocol". The first link I got was a PDF which seems to hold the protocol (i only spent a minute browsing through it).I still don't know if it was made available to the public on purpose, though... 😉
Ad 1)As far as I know, the communication between the OT server and KIH still uses the OIOXML MDSS format defined here (in Danish):http://medcom.dk/wm112638EDIT: I totally forgot that (limited) English documentation is available too:http://4s-online.dk/wiki/doku.php?id=kih-database:overviewI am pretty sure that the Milou/CTG communication is proprietary, and probably not available to the public...Ad 2)(Just adding to Mike's answer here) When you look at tablet/smart phone specs, this feature is often presented as "USB-OTG". Look at this Wikipedia article for more info:https://en.wikipedia.org/wiki/USB_On-The-Go
I am not familiar with your current setup, so the following is some general debugging steps to help you figure out, what is going on at the MySQL server:First of all, as Mike noted in red: You are absolutely sure, that your username is "username"??The next step will be to look at the server-side log. Log in to the MySQL server as root and do:
Code:mysql> SHOW VARIABLES LIKE 'general_log%'G*************************** 1. row ***************************Variable_name: general_log    Value: OFF*************************** 2. row ***************************Variable_name: general_log_file    Value: /var/lib/mysql/mysql.log2 rows in set (0.00 sec)The general_log_file variable is the filename of the logfile and the general_log is a switch (either 'ON' or 'OFF')Change the location of the log file if necessary and switch the logging on (SET GLOBAL general_log='ON';).Now attempt the login again and look in the server log file for any indication of what the server is doing (or not doing). Compare to a successful login by the same user from the same host (for instance using the mysql command-line tool).Remember to turn the logging off (SET GLOBAL general_log='OFF';) when you finish your investigations as it would otherwise grow huge! (unless you have some logrotation service running that takes care of that)For MySQL user/login debugging, it may also be helpful to know, that the MySQL server stores all the user details (including hashed passwords) in the table mysql.user. Access rights are stored in similar tables in the "mysql" database. To access these tables, you must log on the MySQL server as user "root". Then you can do USE mysql; to select the "mysql" database and inspect the tables (e.g. SELECT * FROM user;)One thing that may come as a "gotcha!" when it comes to the MySQL credential handling is that in MySQL the user identity comprises the user name AND the host (which could be either an IP address or a host name). So the same user name logging in from different hosts may have different passwords and different access rights! Therefore, always notice the hostname! What you would normally think of as a "user name" is the ENTIRE STRING 'username'@'localhost' in your case - and not "just" the 'username' part!Hoping these tips will help you debug the connection problems...
