Rainbow Function Resets

[neek0la]

It seems that the rainbow function on the clock is not completing a full loop for me.

Basically there is a smooth transition whilst changing colors then all of a sudden the color "resets" to a completely new color. It happens every 4 seconds or so.

[lancewilhelm]

Hi @neek0la, thanks for reaching out. OK, can you tell me what the setup of your clock is? Maybe what color you are using for background and text, as well as what you are trying to display on the screen? Also, are you trying to scroll the text as well?

I have yet to see this problem, or at least I can't remember it. Let's see if we can get to the bottom of it.

Of course, make sure you are using the most up to date master branch code. Thanks!

[neek0la]

So regardless if the numbers are "rainbow" and background is black (off) or the background is rainbow and text is black it seems to reset.

Though in saying that it, could it be my power supply. Currently im running the whole project from a 5a power supply? Im waiting for my 8a power supply to get delivered

[lancewilhelm]

Hmmm. I think your power supply might not be the issue. This might be a bit deeper, possibly something with the configuration of your clock. Is there any way that you can capture what your settings.txt file says when this is happening? I can try and replicate over here. I have not seen this yet on my clock however.

Thanks!

[neek0la]

This is what is contained in the settings.txt file.
I have changed the time and date on the with raspi-config but nothing else.

"fontName":"digits", "tempUnits": "f", "bgColor": ["solid", 0], "lineCount": 1, "timeFormat": "24h", "boardType": "normal", "brightness": 125, "content": ["time 0"], "customText": "Test", "animationSpeed": [0.0, 0], "textSpacing": 0,"text $ <

[Foxdudes]

It seems that the rainbow function on the clock is not completing a full loop for me.

Basically there is a smooth transition whilst changing colors then all of a sudden the color "resets" to a completely new color. It happens every 4 seconds or so.

I have the exact same problem, any fixes yet?

[Foxdudes]

I found a solution to this problem, the problem is caused because only half of the animation is played. This is because the animation is played for the led_count witch is only half the amount when you use 30led/m strip compared to planetary.

ACTUAL FIX:
in the file LedUtils ,change at the bottom the led_count to led_count*2

[nkilders]

ACTUAL FIX:
in the file LedUtils ,change at the bottom the led_count to led_count*2

https://github.com/PlanetaryMotion/pingPongBallClock/blob/e7ceb039a824b56e44a7bd24193f230b50d6ba3a/code/LEDUtils.py#L593
Changing this line to self.led_count = self.num_balls * PIXEL_RATIO * 2 has also fixed it for me.
(I also use a pixel density of 30 led/m)