RT Target Resources and Distributed System Manager

[Mr._Jim]

Hello all,

Does anyone know of some potential reasons why an RT target might not publish its CPU and memory usage?  This particular target is a cFP-2200 running a complete installation of FieldPoint 6.0.2 (RT 8.6) including System State Publisher.  For some reason I can't view the memory usage on this target and I haven't been able to figure it out.

Thanks in advance,

Jim

[Hillman]

Hi Jim,

Thanks for the post and I hope your well.

I haven't heard of an issue like this before.

Are you using the Real-Time System Manager (RTSM)?

Can you check:

• That you are using the correct IP address.
• That you can target the controller from LabVIEW
  i.e.:
  • The correct software is installed
  • The IP address is configured correctly
  • The system boots without errors

•  To configure VI Server on the remote syste correctly.

I know its expected for Field Point - but maybe true for cFP - the CPU usage is 100% as the CPU polls the I/O constant - unless you alter the pause in MAX.

Please update us so when can continue to help resolve your issue.

Kind Regards,
James.

[Mr._Jim]

Hello Hillman,

Thanks for your reply!  I sort of figured that this one would go by the wayside and not be answered.  Actually, I'm not using RTSM; I'm using the Distributed System Manager - It's a relatively new tool that ships with LabVIEW RT 8.6.  In my humble opinion, I find it to be much superior to the RT System Manager in its own way.  The only downside, really, is that you can't log with it natively, but there are ways around that.

You've got some great suggestions.  I definitely was using the correct IP, I could target it with LabVIEW because I loaded my application on there, and I didn't get any boot errors when I connected.  You're absolutely right, too, that the CPU is always maxed out at 100%.

I guess I was perplexed because, one moment I could see the resources in DSM (is that acronym valid yet?), and after I reloaded the software from scratch, I could see lots of variables on the target, but for some reason the system resources weren't showing up.  After no one jumped on the question, I went back to tweaking various settings and realized that I hadn't rebooted after enabling VI Server.  In fact, I didn't think that VI Server would be the issue and hadn't really thought of checking there.  My reasoning followed that, if all of the other variables showed up, surely it wouldn't be VI Server, but that fixed it.

I definitely appreciate your getting back to me, though.

Cheers,

Jim