Your comments
Hi Alistair,
I just wanted to let you know we have made some progress with the rev. K devices. We did build the cable described in the programmer's guide (and it is not at all the same as Cisqo cable, as you pointed out).
At the Hospital of the University of Pennsylvania they have two kinds of MP70 monitors -- the first kind has 4 RJ45 serial ports (not counting the LAN port) and the second kind has only two such ports. I believe the latter is the same monitor as the one they have at the MD PnP lab though theirs is running rev. J (I paid them a visit a couple of weeks ago).
After lots of unsuccessful attempts with the 4-port version, we were finally able to talk to a monitor with 2 ports (running rev. K). The first time we tried with it, it worked right off the bat. The second time it didn't, so we played a little bit with the port settings -- after some fiddling we found that the configuration DtOut1 and GM worked fine, and we were able to talk to the monitor again. However, the LED lights on the back were misleading -- the port that was set up for data export actually had the arrow going in but we were still able to get the data.
Hopefully, next time we go we'll get to test with a monitor with 4 ports again (it's a bit of a hit-or-miss, depending on which room is available when we go there). But it seems that after some playing with port settings and power cycling, we should be able to get that to work as well.
Hope this helps.
Rado
Hi Achilleas,
Where are you getting the 39 fields? Are you talking about the logger app provided by OpenICE? I believe if you inspect the actual message received on the serial port (e.g., using a minicom) you will see all variables. We had a similar problem but noticed that OpenICE only keeps track of a small number of variables.
Hope this helps.
Rado
Hi guys,
Any update on this?
Thanks,
Rado
Hm, do you have the programmer's manual for the Philips monitors? I wonder if it's just some minor revision in the communication protocol that is causing everything to break down.
Rado
Hi Jeff.
We started a collaboration with RTI recently and asked them about this problem that DDS has with Ubuntu. They gave us the following response (copied below). Does this make sense? If it does, do you think you guys can fix this at some point?
Thanks,
Rado
------------------------------------------------------------------------------------------------------------------
I believe they might be running into this problem: https://research.rti.
- disable multicast discovery address.
Hi Alistair,
Did you have any luck with the new DB9 cable?
Thanks,
Rado
I saw that picture but like you, I assumed that it is the standard pin-out of the RJ45 to DB9 cable, so we got a few of those. Do let me know if the new cable does the trick!
Thanks,
Rado
Rado
As far as I know, it is not possible to use the current version of OpenICE on Ubuntu offline. Based on a conversation I had with Jeff in one of the other threads, the spring schemas are looking for a network connection (could be a local connection, not necessarily an internet connection).
The way I see it, there are two ways to proceed (unless OpenICE is somehow modified). The first is to strip down the OpenICE code so that it doesn't include the networking stuff. The downside here is that you'll have to do this every time OpenICE is updated.
The other option (I'm speculating here) is to try to simulate an open connection and see if that works. I haven't had time to try these things but we'll eventually get a Master's student to try.
Thanks,
Rado
Customer support service by UserEcho
I see. This is good to know, thanks! We suspected that the LAN port might be messing things up -- maybe that's why we had to cycle power before we could talk to the monitor.
Just out of curiosity -- does your MP have 4 or 2 RJ45 ports? Not sure if there is any difference, but we have only been able to talk to the 2-port variant as of yet.