Hi Jeff,

To get back to the MP70 discussion (we got a little sidetracked in this topic), we just went to have another go at the MP70 monitors at HUP (Hospital of UPenn). Turns out they are revision K (you guys seem to have J if I'm not mistaken). In any case, OpenICE gets stuck at the association step - we are getting some message from the monitor but I can't figure out what it is (I think I stored it but who knows - I just have byte array). Also, don't know if this is important or no, but since I updated to the latest version of OpenICE, the code seems to be doing something slightly different, though we are still unable to communicate.

Do you guys know what are the differences between rev. J and K? I'd imagine they're not so big if the two are just one generation apart but maybe I'm wrong.

Thanks,
Rado

Hi Jeff,

Don't know if this makes any difference but we are not using the recorder app that you guys provide (we're not quite sure what's the functionality of it). We're actually using our own ad-hoc data collector -- since the PB840 messages are human (and machine) readable, we're just storing the messages themselves. So essentially, we're just using the (modified) PB840 device-adapter.

So, if nothing else works, we may try to strip down OpenICE to just the PB code and only run that on the beagle.

But yes, from our perspective it would be great if you guys have an option to only provide device adapters. I guess this already works on Windows/Mac but unfortunately we can't figure out how to do it on a small board without using Ubuntu.

Thanks,
Rado

Hi Jeff,

Our current plan is to just tape the beagle to a Puritan Bennett (and possibly an MP70, though it seems like that will take some more time) and let it collect data for a few weeks, while clinicians move it around and hook it up to different patients. So, I don't think we can expect nurses to also connect the beagle to a laptop.

Is there any way to disable the DDS code? We won't be needing it for this project.

Thanks,
Rado

Hi Jeff,

So the workaround is to simulate a network interface? How can I do this on a regular Ubuntu machine (i.e., not a VM)? Our goal is to run OpenICE on a beagle board, which will definitely not have internet access.

Thanks,
Rado

Hi Jeff,

Thanks for checking in. We haven't had a chance to play with the MP70 recently but will go soon. We were waiting for you guys to first fix the other bug with Ubuntu not begin able to work offline since that project is higher priority. Do you know how that's going?

Thanks,
Rado

Hi Dave,

I was using the term "ethernet" loosely. I meant that it has RJ45 ports, which are used as serial, as far as I understood. And we are getting structured messages from them, which openICE is able to parse. But we are stuck at the association stage.

BTW, our philips monitor only has 2 ports. The one that Jeff showed a picture of in an older topic has four, so I was just wondering if this is an indication of a different protocol or something like that.

Thanks,
Rado

So, I run it using eclipse, and the classpath is whatever eclipse produces. Do you want to me paste the classpath from eclipse here?

I was actually looking at the classpaths yesterday. Under windows, where everything is fine, all the schemas are added to the eclipse classpath, whereas under ubuntu they just remain in some jars in a gradle dependency folder, which is never used, I'm guessing.

Rado

Sure, no problem. Please let me know when you guys fix this.

Thanks,
Rado

To make this even more confusing, I can't even run demo-apps with a simulated device with no internet on ubuntu. So it's not a compilation problem.

Hi Jeff,

Thank you for the explanation. I believe we have a different problem, though, and hopefully simpler.

I'm pretty sure we have a compilation issue because we can get our laptops running Windows or Mac to connect to devices even when offline. But on Ubuntu it just crashes when there's no internet connection (even if we just use a laptop). As far as I understand, this is a problem with the spring framework of gradle where for some reason under ubuntu it goes online every time to download some beans schema. This may also be an eclipse-gradle bug under ubuntu (and may also be a java problem). So I was hoping you guys may have encountered this problem before or have some insight.

As for the problem you describe, for now we will solve it by collecting data locally on each board, since the devices we are interested in already provide enough measurements. We will worry about interoperability issues once we get this first step working smoothly.

Thanks,
Rado