A well-known problem in many areas that have something to do with light, such as LED control or photography, is the subjective perception of brightness in relation to the actual power of the light. The problem here lies in the characteristic curve of the human eye. This is not linear, or more precisely: it is almost logarithmic. This makes it possible to perceive a very wide brightness range, from a full moon with ¼ lux to normal desk lighting with 750 lux to a bright summer day with up to 100,000 lux. Such highly dynamic signals can only be handled with a logarithmic characteristic curve.

To counteract this effect, there is the so-called gamma correction. Mathematically, this function is a power function with an exponent, often called gamma for short, as the only parameter. We have now added exactly this function to the daily planning. Pre-calculations, previously made with more powerful computers, increase the accuracy and relieve the comparatively small processor of the SunRiser.

In the function test, on the other hand, we work with the direct power value, i.e. the value 1 to 1000 stands for the actual power that the LED consumes, 500 would therefore mean that 50% of the maximum current power is applied. If you now specify 50% in the daily planning, this means that the planning tries to produce a 50% brightness, this is then approximately at the value 32 in the function test (one cannot say this exactly because the time factor also plays a role here and therefore the final value sometimes deviates in order to improve a smoother transition to the next stage).

In planning, however, for users who want to have full control over performance, is to create an option that turns off this gamma correction and thus does an absolute, linear performance fading over the set time period. A further step after that would be the possibility to adjust the gamma correction instead of just switching it off.

If you activate the moon, it will shine according to reality, this can also be during the day. This can of course be an undesirable effect. It is best to use a separate LED for the moon simulation. On http://www.mondverlauf.de/ you can check when the moon rises and sets, in one of the next versions you will be able to determine the GPS coordination for the calculation yourself.

Another helpful option that we will add soon is the setting of the period of the day where a moonrise can only happen.

Rain is handled in fronts in the same way as thunderstorms, i.e. a rain front is defined randomly in between, but since the rain tries to work off a certain % of rain per day, it is not (currently) possible for the user to influence this. Please note that the rain always occurs in combination with the thunderstorm, as long as a thunderstorm is set.

The entire web frontend uses an API to bring your configuration to the SunRiser. This API allows you to set the configuration, install firmware or any other functions you have in the web interface.

The communication for this runs as a MessagePack over HTTP from the SunRiser. We plan to add at least one more API via GET parameters to be integrated in systems like Fhem. On request we will also document the MessagePack API, but we plan to do this only for the GET API.

This will most likely be the rain or cloud simulation. Depending on how high the current value of the daily or weekly planning is, this can lead to very noticeable flickering, which some customers have already reported as a malfunction. When switching off the simulation, please note that the setting is available separately for each profile, so you must make sure to switch off the simulation in all profiles.

In the expert menu we have provided a function that allows you to copy back and forth between the programmes of the weekly planning or the daily planning. The markings in the programme or the daily planning are converted into comma-separated lists with the minutes of the day and the performance alternating. Simply copy from one field to another. You can also edit the values directly here, just make sure that the daily minute can be a maximum of 1439 and the power a maximum of 100.

If the SunRiser restarts sporadically, does not save settings, activates the LEDs unscheduled or does not load the web interface completely, there may be a defect (write/read error) on the SD card of the SunRiser.

In spite of several function tests by us before shipment, such an error of the MicroSD card can unfortunately not be avoided completely.

Solution 1

Often this problem can be solved with our factory tool. The internal SD card of the Suniser 8 is reformatted, the current firmware is installed and then your configuration is reloaded into the fresh system. If there are problems loading and restoring your configuration - please dispense with this point, repeat the process and select "no". After the restart, you can import your personal backup file in the usual way.

Let's go, open this link and follow the instructions/options.

http://sunriser.ledaquaristik.de/factory.html

Solution 2

If the above procedure is unsuccessful, you can alternatively open the SunRiser 8 and remove the MicroSD card.

See a photo at:http://srdemo.ledaquaristik.de/img/sdcard.jpg

Attention: Before you start, disconnect the power supply and disconnect all plugs of the LEDs.

Replacing the microSD card does not affect the guarantee or warranty, we consider this as regular use of the unit.

Now reformat the microSD card (FAT32, no quick formatting) and then save the firmware file "NEW.BEE" on the reformatted card. (You can also use another/new SD card of any size (from 2GB)).

Download the latest SunRiser 8 firmware ("NEW.BEE") at: http://sunriser.ledaquaristik.de/NEW.BEE.

Then insert the card back into the SunRiser 8 and close the unit. The firmware will be installed automatically when the unit is switched on and the SunRiser will restart. After the restart you can read in your personal backup file in the usual way.

No, the clouds and rain are not visible when the brightness setting is set to 0%, because they only work by lowering the brightness for a short time. Nevertheless, the SunRiser tries to maintain a certain minimum brightness.

The probability refers to the complete day, i.e. to see clouds (or rain) all day, you must set the probability to 100%. If the probability is set to e.g. 50%, the SunRiser will literally flip a coin every day and if it is heads there will be clouds. It is still possible that the amount of clouds or rain on these days may be very low to almost non-existent.

Possible solutions:

Connect the SunRiser to the router. If necessary, do without repeaters or PowerLAN.
Call up the SunRiser Finderhttp://sunriser.ledaquaristik.de/

Also:

If you use a GBit switch, make sure that it also accepts 10/100Mbit devices.
DHCP should be enabled in your router
Check that the SunRiser is not blocked by the router's MAC address filter.
Eco or energy saving mode of the router: off
If necessary, disconnect other network devices as a test

The rain simulation and the cloud simulation differ primarily in the commonality and in the duration of the brightness changes. A raindrop is a short darkening, while a cloud can darken over a longer period of time. Also, with clouds, all LEDs are connected together. If 3-4 LED bars are assigned to the cloud simulation, they all darken together. When it rains, on the other hand, all LED bars produce raindrops independently to support the image of a "chaotic" rain.

The higher the value, the more intensively clouds and rain darken the lighting. It is a relative value, i.e. it becomes less and less dark when the general brightness is low anyway.