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.
This is (again) a request to finish the full integration for the Beckhoff ADS Driver.
In 2.2 the development was started, and partly implemented.
For 3.0 the full implementation was promised, and (as far as we now) started.
But now, we see in the roadmap, the ADS-driver has 'low priortiy'.
We have many, many installers asking for the Beckhoff ADS-driver, and we think it's a good thing to let vote for this ADS-driver, so the iRidium mobile team can see these installers want it and need it.
So, let's vote for it!!!!
From my personal work with static lists I would suggest to update it's behavior:
- when first or last popup is selected, it should not try to move further, opening background
- there should be "infinite mode" when after last popup first popup is shown
- there should be "non-page" mode, when drag stops immediately, once finger is up
i think it's good to have an auto-updating feature in iRidium Studio / Server / Windows i3 Pro.
This is absolutely a 'must' when 3.0 will be released; we can not ask installers to manually update all software!!
Please implement auto-updating in the next beta-build, so we can test this functionallity before it will be released.
would it be possible that i3 Server pro can act and react like a real HDL-Buss Device?
In a real installation, there is a mix of Control-Panels like an iPad/iPhone/Android-Tab and real HDL-Bus enabled panels like the DLP panel or switches. It wouldn't be possible to control actions on the i3 server from other panels than i3 panels.
For example, it should be possible to send dimmervalues directly to the i3 server. the i3 server should act like a 12channel dimmer for example. So it would be possible to trigger normal dimming actions from every HDL Bus Device like it would be a real dimmer. Or for example the i3 server should have UniversalSwitches like the HDL LogicModule, so that we can set and read this UniversalSwitches from any HDL-Bus device, etc.
So, please include a method to add "virtual" HDL-Bus-Devices per channel basis like a DimmerChannel or a UniversalSwitch. Also, additional "virtual" devices would be fine like a temperatur module or a curtain module that gets the values from within i3 Server variables...
Also, please include an option to update the current time and GMT+/-offset via the i3 Server to the LogicModule. So that the annoying daylightsaving time would be automatically corrected on the HDL-Bus.
With best regards,
Martin Lang - MEB Austria
Can we please look at reducing the time it takes to
1. save and run the emulator (by the way this should not say 'save' as it is not saving)
2. save and send to transfer
3. save the project
Why does it needs to save before running the emulator or sending to transfer?
On a reasonable sized project this can take 30-40 seconds. This is way too long. I use other professional programming IDE's and they do not take this long for similar sized (MB) project
This is a major frustration
Installers need the option, that end-users can change the scheduled timers/clocks that are defined in iRidium Server.
Also values, used in routines, have to be changeble by end-users. For example set-points for temperatures etc: end-users must be able to change them by theirself.
PLease implement this.
The logger is a great thing to have. But if you could implement highlighting of messages in it, it would be perfect:
- errors and warnings - RED
- user messages - BLUE
- service messages - BLACK
It would be very useful and time saving when scripts are saved the syntax of the script is checked. ie functions, variables, operators, conditional statements ( for, if, while, switch ) At this time when you run the emulator or transfer an project with a script which is known to generate an exception because of bad syntax, there is nothing being checked. You have to wait. Now depending on the system you are developing on that can be 30 secs to minutes of time wasted waiting for the emulator to start only to discover that you forgot to add an closing bracket ' }' on an if statement, It would save sooo much time if at the point of saving the script the syntax is checked and if there is an error, a dialogue displays what is wrong,
This system of syntax checking exists in many other development environments and is an feature which is missing from the iRidium script editor, Even the Logic Machine from Embedded Systems has this built in their lua scripting editor
When installer scan the Domintell-bus, the description from the Domintell-commands and feedbacks are NOT imported in the GUI Editor.
The installer has to manually edit all descriptions of commands and feedbacks, and this take lot of time.
Please improve the scanning of Domintell-bus, so the names of the commands and feedbacks are displayed correct in the Project Device Tree.
Customer support service by UserEcho