[Logo] Mango Community
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
Messages posted by: mlohbihler
Forum Index » Profile for mlohbihler » Messages posted by mlohbihler
Author Message
Hi Roberto,

Yes, the header.js calls the corresponding function in the common.js. I'm sorry, but I can't say what is going on because it works in every other instance of Mango that we run. I can only suggest that perhaps your browser cache is hanging on to an old version of the common.js file. To refresh, press ctrl+F5; hopefully that will correct the problem.
That is likely related to something else. Please try again and see if they appear now. If not, please make note of the icon URL.
Mango currently only stores its data into it's own SQL database. The database that is used is Derby entirely because its embedded nature greatly simplifies the installation of Mango.

I have attached the current (0.9.2) table create script for your information. I hope this helps.
That error message is strange because the line number does not correspond to executable code. Also, all references to javax.comm.* were removed in version 0.9.2.

Did you upgrade from a previous version, or download 0.9.2 and install fresh? If you upgraded, can you try the upgrade again? Perhaps it didn't install correctly for some reason.
Hi Roberto,

Two things:

1) Please confirm the version of Mango you are using. 0.9.2 should not have any references to javax.comm.*.

2) Errors like that or gnu.io* indicate incorrectly configured serial i/o. Please check the instructions on the download page.
Hi Roberto,

Thanks for reporting the problem. After some further investigation we think we found a bug. Luckily, the fix is quite easy.

Edit the file WEB-INF/jsp/pointHierarchy.jsp. At line 62 there is a function called "addFolder". Add the line as shown below:



When you save the file and go to the page again, the page will be automatically recompiled, and you no longer should have the problem.

Note that this fix has not been "proven", but we hope it will do the trick. Please let us know if it works.

(Note, this fix applies to Mango version 0.9.2, and possibly some earlier versions)
Hi Keith,

Thanks for the information. We in fact have code about 75% complete to implement 1-wire, but due to other (paying) project work, have not had time to complete the implementation. Watch the site for updates!
Ok, great. Thanks for the resolution.
Make sure the DLL is in the <jdk1.6-home>\jre\bin directory. (You wrote jdk/bin).

If that's not the problem, the only other thing i can think of at the moment is that the correct JDK is not getting started when you run Tomcat. Do you have any other JDKs installed on your machine?

Hi,

Data sources are just mechanisms for collecting data; the number that you can run at a time depends on many factors, but in most cases you should be able to run enough to monitor more equipment than is currently imaginable.

By transactions i assume you mean data point values (i.e. historical records of data point values at specific times). Individual data point values take up tiny amounts of database space, but, sure, tens of millions of them can add up. In the end though, the amount that you can store only really depends on the size of your hard drive (or other persistent storage).

Mango can manage data purging for you. You can choose the point value purging characteristics at the level of the data point itself.

As for transferring data over from an existing database, it should be possible, but depends entirely on the structure of the data there, specifically how well it fits into the Mango structure. If you need details on the Mango database schema, let me know.
Hi Prodyut,

Thanks for the suggestion. Sadly it may be some time before we get to this due to (paying) project work that is keeping us very busy. Of course, Mango is open source software, and so we encourage those with a development yen to feel free and implement new stuff.
Hi,

The comm handling has been changed to RXTX in order to consolidate the package use across all platforms. It seems the upgrade instructions did not highlight this well enough, since many users appear to be having the same problem.

(The problem is not due to cygwin, since i personally also have it installed, and everything works fine.)

What you need to do is download RXTXcomm.jar from the download page and put it in the specified directory. If you use serial-based protocols you'll also need to download the dll file.

Let me know if this helps.
Hello Roger,

I can't speak too confidently for Matt, but since there appears to be a problem with his domain i'll tell you what i know.

Matt used some functionality with the VK011 to connect it to a SQL database, and then used Mango to read and update values on the same database. I don't know if there is a more direct route between the VK011 and Mango (such as using Modbus or something), but if not, the database that he used was MySQL, which is a free download, and for Fedora is available from the "add software" interface or using yum.
Hi,

If you have recently updated your Mango M2M installation, be sure that you followed all of the upgrade instructions on the download page. In particular, check that you have properly installed the RXTX libraries that have replaced JavaComm.
Please note that the installation of RXTX is required when updating to this release. Please see the installation notes for this package on the download page.
 
Forum Index » Profile for mlohbihler » Messages posted by mlohbihler
Go to:   
Powered by JForum 2.1.9 © JForum Team