Host Engineering Forum

General Category => Do-more CPUs and Do-more Designer Software => Topic started by: Evilbeard on April 22, 2017, 04:38:20 PM

Title: File Log Error
Post by: Evilbeard on April 22, 2017, 04:38:20 PM
I added a line of logic to record blocks of 31 data points on a monthly basis.

(https://forum.hosteng.com/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FXSq1MZp.png&hash=3cde4d9af13afa2a8224c06029f6f77ba0af294e)

When I tried to load this into my PLC, I got this error:

(https://forum.hosteng.com/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FBQTUS6X.png&hash=a48c9392e228687d767677c6872e98d37e319c99)

This is just a DM1E. Is this due to the limit on the RAM size?
Title: Re: File Log Error
Post by: BobO on April 22, 2017, 05:51:12 PM
No. Sounds like we may have a program encode issue. Please send the project to support@hosteng.com and we'll take a look at it. That's a fairly long list of points, I'm betting we have an error in a length limitation somewhere...DmD is allowing something that the controller is disallowing, or something like that.
Title: Re: File Log Error
Post by: franji1 on April 24, 2017, 09:07:29 AM
It's most likely a missed error check by the instruction editor.  FILELOG editor was missing a few "limit" checks, which SHOULD have been reported as errors when the instruction was edited (e.g. too many entries).  We have already fixed a few of these that will be in the next release.  I would still like to see the project file, however, or at least that one instruction.  Please send it to support@hosteng.com.

Regardless, there is a limit to what a single FILELOG instruction can handle.  The work-around is to split it up across 2 (or more) FILELOG instructions with different base file names (e.g. FILELOG w/RunDataA and another FILELOG w/RunDataB).
Title: Re: File Log Error
Post by: franji1 on April 24, 2017, 11:08:16 AM
Please send it to support@hosteng.com

Got it!  Thanks!
Title: Re: File Log Error
Post by: franji1 on April 24, 2017, 12:06:19 PM
The new FILELOG validation check would have caught your situation within the editor.  In the next rev, you will get an error message like the attached.