+3

Automated diagnostic table of I/O for devices to show on touchscreens

Jorge 3 weeks ago in IQANdesign • updated 2 weeks ago • 3

Right now, in order for us to make diagnostic pages of inputs and outputs we have to create them manually by linking the outputs of our program to objects on the touchscreen, in small proyects it isn't much of a problem, but when we start to have multiple devices on a single proyect full of inputs and outputs, it starts to get tedious, we lose a lot of time in reviewing those screens to make sure all inputs and outputs are displayed.

As such, i think it would be great if we could have a new subcategory on the menu screen for the MD5 touchscreens were it automatically displayed the inputs and outputs we have configured, with the name that appears on the program aswell as it's value. 

I think this would reduce the probability of human error on the programmer's side, while also saving quite a lot of time in not having to create those pages ourselves.

Many years ago, I recall the MD3 had this in its default menu structure and it was useful certainly on smaller projects with a handful of inputs only.


Perhaps the ability to enable or disable these additional menu item screens could be advantageous in IQAN Design, just in case the programmer doesn't want to them visible to the end user.

Dragging and dropping channels to a measure group is quite fast but viewing channels as a list isn't visually the best solution, as you said it would be really useful to have for an example same kind of automatically generated block diagram view to each module with color indications and channel values like we already have in simulation view.

I actually had not thought of that Markus, i will use that from now on when testing projects, but as you said, viewing the inputs outputs as a list is not ideal.