Welcome!On this forum you can discuss iRidium with other users. iRidium consist of 2 main components - i3 pro app and iRidium Server. Please post here your questions, ideas or errors you find.
Please send your questions to support team as a private messages.
Suggestion: on the panel side of the iridium studio, when you import a server project you obtain the complete list of the Commands and Feedback. It would be better if this list will be grouped into the original driver. For example, if you have 5 or 6 driver it is much better to have 5 or 6 group subdivided by driver type (all KNX commads will be under KNX group, all modbus will be under modbus groups, and so on ...). Imangin 1000 commands, from 10 drivers/devices, and you need to find all the KNX commands ...
We want logical expressions in the Studio Editor. Not to use the "Schemes", but (for example), in State1 of an item:
This is more simple then using the "Schemes" (available in the next Beta-version ;-) )
It would be great if we have an option in the Macro Editor:
Show System Menu
For every project again. Because every installer need this option in a project to quickly change settings in the client, and to prevent end-users to click in the project for 8 seconds (what is a problem for many end-users) to open the system-menu.
So, in the menu below we want an extra option: ShowSystemMenu, that we can drag & drop to the list with Macros in the Macro editor.
It has been implemented from iRidium Studio 184.108.40.20606 (beta)
For the modbus protocol we must use an On-Press command, sending a '1' to the Modbus register, always followed by an 'On-Release-command', sending a '0'.
The questions: can you improve the Modbus protocol, so this will be done in the default On-Press command? So the On-Press command is sending the 1, followed by the 0? Or make a special command (only if the installer is using a Modbus protocol), with this function build-in? Because now, for every button that will be used in a project, the installer has to made 2 commands, and that's not logical, so it's better to build-in this in the protocol for Modbus.
This should be a great improvement for all Modbus users!
It was added in iRidium Studio
1. AV drivers, created in dynamics, save the queue, when connection is restored they send all accumulated data into the net. It can be possibly corrected with switching a definite parameter when a driver is created. What parameter?
2. On trends and panels with data the status does not change when the connection is lost.
It would be good to change the looks of a itemn if data don't come to it, for example, they can become black and white or shaded or marked with an exclamation mark in the corner.
Parts of trends when data were not written in the bases should be marked to see when there was loss of connection or any other failure. It can be marked with shaded area.
In the project device tree, when hovering the mouse over a command or feedback, we can see in which page and item a specific command or feedback is used. This is great, because it's a usefull tool for debugging.
We want this option also for dynamic images: if we move (hoover) the mouse over an dynamic image in the Project Gallery, a little 'tooltip' showes the page or pages where this dynamic image is used. Including a parameter (number) how many times the dynamic image is used.
When adding feedbacks, we currently have to use the mouse to select Value, Text or more...
= Multiple mouse click
Can we please change this to be a form like adding commands,
- so it remembers the last selection
- we hit the enter button does the ok, the same as adding commands.
= after the first feedback is done, we then have one mouse click and one keyboard enter to add subsequent feedbacks of the same type.
This will be much much faster, and we don't have to use the mouse quite so much
This is what we want:
Create a new project
Insert KNX-driver (or other driver)
Drag & Drop a command to the canvas
Release the command on the canvas
Now, a new button is auto-created, with the command automatically assigned to this button!
This will save many, many time with creating test-projects, demo-projects, prototyping, etc.
The 'default' button must be pre-configured in the GUI Editor settings: what type (button, Multi-state button), colors, etc.
Now there is no easy way to run a server scheme or a script from i3 pro or Rules editor. There should be.
Most simple way to do this is to be able to attach virtual group values to script or scheme.
Consider entering hotkeys to manage z order
Очень не удобно размещать айтемы по вертикали без горячих клавиш. Попробуйте - нужно прыгать по экрану, особенно когда айтемы перекрываются. В оверьвью выбираешь, уводишь мышь на поляну, кликаешь выбираешь один шажок вниз, окно закрывается, и снова и снова..
Куда удобнее было б выбрать в овервью, и гор.клавишей вверх/вниз наблюдать как айтем перепрыгивает по ветке.
Customer support service by UserEcho