Your comments

hi Vija. Sorry, I don't know about your monitor. We were using MP/MX series over a year ago and needed a special adapter. I don't know what's changed with CM120/HL7. Good luck.

2 ports. - one is for the EMR, the second we are using as Dtout2

hi Rado - thanks for the follow up. I actually have been working on a direct plug and play driver using C++ instead of Java. Doing this I've learned the MP series will only export wave data to one output - the first that requests it. So if the LAN port is in use then the RJ45 will only output numerics. Also the LAN uses IP/TCP protocol but the RJ45 can do fixed baudrate - which is what we are interested in using . The process for receiving and parsing data is complex and I've hired a professional programmer to tackle it. We can associate (at a baudrate of 115200) and receive data. We're currently fixing some memory caching issues. Overall this is an easier solution for us, but I hope to come back at some point to work again with OpenICE. Best of luck

Well, I got the custom RJ45-DB9 cable from MediCollector and repeated the whole adapter setup process. I can see the times are synchronized. OpenICE recognizes the adaptor and it shows up as an image, but I am still stuck at the Requesting Association, like before. I had to change the terminal command to address ttyO2 because that is the serial port on the BBB Revision C card that I have. I don't know if this is causing an issue or not. Frustrating. I've been trying to get this to work for months.

Alistair

Not with my first try - I made the connections like I thought - based on the diagram- but still got no data. When I tried to pull out the wires to try a different configuration I broke one of them. Rather than order a new modular adaptor, I just ordered a $30 cable from medicollector.com so that I can have something that should work and that I can look at to make my own in the future. I'll let you know if the new cable works.

Hi Tyler (and Jeff)- Reading through your post, I've also gotten stuck at the negotiating phase. (negotiating - requesting association). Can you tell me how you rewired the custom RJ45-DB9 adaptor? Assuming we're both using the SF cable adaptor, I found this chart online:
Pin1 -- Blue
Pin2 -- Orange
Pin3 -- Black
Pin4 -- Red
Pin5 -- Green
Pin6 -- Yellow
Pin7 -- Brown
Pin8 -- White
So I've used the red, green and brown wires (4,5,7) but noticed you had blue, black and green. I've tried red->5, green->2, brown->3, and red->5, green->3, brown->2, but still only get the 'negotiating -requesting association' (how long does this step usually take? more than a minute?).
Any help you might have I'd greatly appreciate.
Thanks,Alistair.
Hi Rado - Like you, i've been stuck at the 'requesting association' stage of trying to get the device adapter to work. I just realized that my problem might be that I'm using a standard Cisco RJ45 to DB9 cable and not the modular adapter that requires a unique configuration (see the diagram on the device-adapter page). For some reason I glossed over that image thinking my Cisco cable must have the correct configuration, rather than realizing that it does not. I wonder if this is something you've already looked at and whether or not it solved your problem. I'm waiting for amazon to ship me the adapter and am hopeful its the source of my stuck association problem.
I think I just realized where the problem is - I've been using the Cisco RJ45 to DB9 cable and not the modular adapter. Just ordered the adapter from Amazon. Hoping this will get me past my 'negotiating - requesting association' spot.
Hi Jeff-

Thanks for the reply. I'm actually only trying to run the Device-Adapter, not the Supervisor program. Following the Device-Adapter Beaglebone Setup instructions on OpenICE, at the bottom of the first page it says:

Your new device-adapter is ready to use. You can start the software with OpenICE-0.6.3/bin/OpenICE from the home directory. Check out the next page for more instructions.

This was where I ran into the big error message. Does the device-adaptor work without this command? The supervisor program on my computer recognizes the Beaglebone on the local network - initially with clock and exclamation point which disappear once the modem is on an active network/NTP. But I'm not able to get any vital sign data at all from the RJ45 port (outgoing) of a Philips Intellivue MP70 (version K) because I get stuck at a "Negotiating - requesting association connection." I'll paste a screenshot so you can see. I've stopped and started the service with the terminal sudo commands, but can't seem to get beyond this point. I've tried different machines - including MX800s and different ports (LAN) to no avail. Any help would be greatly appreciated!!








Hello Jeff-

will the MP70 driver work with the mx800? We are not having any success with the MP70 version E, MP30 version J, or MX800 version K. We don't know if this is a driver issue or not.

thanks,
Alistair