Messages

1

Support Questions / Re: BasicDataLogger file size limiting

« on: April 07, 2015, 09:11:26 PM »

Thanks for the suggestions and advice guys!
I had seen the post that Archie referred to and had started playing with it but ran out of time and haven't gotten back to it. And in the meantime, I had also thought of doing just what you had suggested Godra. So! I think we're all thinking similar thoughts. Just need the time to put some to the test!
I will update when I can.. Life has gotten busy all of a sudden and it may be some time before I get anywhere with this. But thanks again for the help!

2

Additional Components / Re: Quick Chart

« on: April 04, 2015, 12:28:14 PM »

I'm really liking the work you have done Godra!!
I have modified it a bit to my needs but appreciate very much your work!

My problem now is how to limit the size of the log file and to get it to roll off old data.... Fun stuff!!

3

Support Questions / Re: BasicDataLogger file size limiting

« on: April 04, 2015, 12:22:54 PM »

Thanks for the reply!
You're right on to what I'm trying to accomplish. I do need to 'roll off' the old lines when the file reaches that 'MaximumPoints' size.

Seems like it ought to be easy but from what I've thought and read, one must check the files size, and if too long, you must read in the file, then write it back minus the first line..... and if the file contains very many points, this can be quite burdensome on the machine.
Would be sweet if there was a way to delete the first line of text in a file as it is to append a new line to the end...

I feel like I may be getting away from the BasicDataLogger control and that's precisely what I don't want to do!!

Any suggestions??

I have been working with some of the stuff Godra posted on his Quick Chart and liking it!

4

Support Questions / BasicDataLogger file size limiting

« on: April 03, 2015, 06:03:55 PM »

Can anyone tell me if there is a simple way to limit the size of log files created by the BasicDataLogger control?
More specifically, is there a way to set a time frame such as I only want a days worth of data in the log then have the old data roll off?

5

Open Discussion / Re: Best way to move a project from one version of AdvancedHMI to a newer version

« on: July 14, 2014, 05:37:10 PM »

Thanks Archie! So far so good! It seems to be working. I noticed some changes to the Modbus driver as well as a new Modbus RTU driver I am excited to give a try on another little project I am going to try.
The simple water system SCADA project I have running has done really well. The only thing I had was the Modbus Comm Fail - 20 error box that kept popping up about once a day or so. Everything kept running and it has to do with the way I am pulling data to chart for trends. None of the actual control functions have ever given me any errors or problems. And reading from another post, you make the comment to take out the line 621 from the Modbus driver code to not have the message box pop up. I haven't really looked at the changes to the driver code, but am trying it to see if that will solve my pesky little annoyance error box. Maybe I should try it with it left in first... don't know. I will try both.
I need to come up with a better way of getting the data for charting that is synced with the rest of the ip requests so it gets handled better.

Anyway! I really like AdvancedHMI!! It's been fun and a learning experience and it works!

6

Open Discussion / Best way to move a project from one version of AdvancedHMI to a newer version

« on: July 14, 2014, 02:21:44 PM »

I hate asking dumb questions... but what is the proper and easiest way to move a working project from an older version of AdvancedHMI to a newer one???
I see the latest version has some new goodies I'd like to incorporate into my existing project... Can it be done without starting over??

7

Support Questions / Re: ModbusTCP - Comms Failure 20 - Code to reset it automatically?

« on: April 23, 2014, 12:56:29 AM »

I'm curious what you have come up with as a cure for this issue.. I am having a similar problem when I 'read' a Modbus value and chart it's value. Because I'm just reading the value, it's not critical that it be a 100% and I occasionally get an exception message of Comm fail - 20. When I click the continue button on the message box, it goes away and all is well. Btw.. the charting will go on un interrupted even though the exception message is on the screen.
I get the feeling that the reason the exception is happening is because the PLC I'm talking to, is busy and therefore the vb code for the charting I'm doing throws the error. I am really a novice when it comes to all this and have read a bit that suggests that if I could subscribe to the plc address rather than just read it, it may put the request in line with other requests that are being made and would be successful.. Could this be the case? And if so, how in vb code??
Anyone with ideas?? Am I totally up in the night??
If there was a way to just get the exception message box to go away automatically,.... that would be a way to have it be less annoying... But I would rather get the code so that it handles the requests and exceptions correctly rather than just making it out of sight out of mind...

Ideas??

8

Tips & Tricks / Re: Hear Your Alarms, not just an annoying buzzer

« on: November 18, 2013, 09:53:19 PM »

I realize this thread is a couple months old but was wondering if I am doing something wrong.
I have the message speaking to me, but.. it appears that it is storing triggers each time it gets data from the plc (using modbustcp if that makes any difference) and will repeat the same message as long as it takes to speak it as many times as it was triggered from the plc even though the plc may have changed the value and a new message is now supposed to be heard.
The text for the message changes instantly as it should but it continues to speak the old message until it goes through the number of times it received it from the plc then starts speaking the new message the number of times it was received! I can see where in a very short time it could take forever to go through the numbers of triggers that are stored... Any ideas?

Fun stuff!!