Compile Error

[BobO]

I'd like n-dimensional arrays (wuth slicing syntax and math ops to boot)  and nested UDTs, too.

We'll definitely do n-dimension and nested UDTs. In evaluating the engine implementation, we realized that the memory math required to do arrays of structs of arrays of structs, etc, n-dimension arrays, and simple parameter math, was all basically the same. We have some pretty good ideas and are quite excited about the potential. Just gotta get the BRX analog modules rolled out and then we're going start investigating more deeply.

[RBPLC]

To me lack of "mid-line outputs" may not necessarily be a big deal as I better understand how to optimally use the software. It just threw me off because I was initially trying to copy ladder code from Mitsubishi verbatim into DMD. I agree that long ladder runs can get overwhelming and confusing to read. In this particular program there are several instances of long runs that get hard to follow but I didn't write the initial program. I was going to initially copy everything verbatim and then re-work it where it made sense. It's just my inexperience with DMD and lack of seeing this issue before that was throwing me for a loop because I assumed that I would have no problem copying the program verbatim. When I went to compile it and got error messages or broken code I thought I was missing something. It would definitely be nice to have the ability to do what I'm trying to do but may not be a showstopper. As mentioned, I would also like to see 2-D arrays, implicit EIP and websever and a fix to the issue discussed in this thread. From my experience, these are some of the very few areas in which DMD falls short in comparison to Productivity Suite software (of which most of my other experience comes from). I know you guys are actively working on implicit EIP and webserver.   

[jwbaker3]

I agree we need 2D and 3D arrays, Implicit E/IP. These are the biggest issues for me. We use 3D arrays and manage them with OPC and excel for CIP (clean in place) systems in the food and beverage industry and all of the drives, flow meters, conductivity meters, etc. use implicit ethernet/ip messaging. As said in another post without these things it will not keep me from using the DoMore but we will have to use other platforms (AB, Siemens, GE/IP) for these types of projects.

JW

[Controls Guy]

We'll definitely do n-dimension and nested UDTs. In evaluating the engine implementation, we realized that the memory math required to do arrays of structs of arrays of structs, etc, n-dimension arrays, and simple parameter math, was all basically the same.

Awesome, all those things will make my programming life easier and lead to cleaner programs.   Thank you in advance!

[RBPLC]

So...I've tried to implement stage programming for the example given previously and for this application stage is not the answer. When looking at the code, there is an element that could be staged but it is not ideal. Stage is meant to handle sequential actions. The example I posted is more a machine safety circuit with multiple parts of the machine coming on at the same time, not sequentially, and staying on unless a fault condition is seen. Even with stage, additional status bits and replication of code has to be done. I vote for fixing the mid-line output issue.