Hi Shoban,
If you look at the history of this conversation, you will see that I had the problems with the chainable leds since October 2015. Yes I have tried it with the 1.2.2 and that is what I am currently using.
I will try the 1.2.7 firmware if I am able to perform the upgrade.
After that I will try to upgrade to the Raspbian for Robots.
Many thanks for your fast replay. I will keep you posted.
Kind regards,
Freddy
Hi Shoban,
Me again.
I do not know what I am doing wrong but the command https://raw.githubusercontent.com/DexterInd/GrovePi/firmware_1_2_6/Firmware/Source/v1.2/grove_pi_v1_2_6/grove_pi_v1_2_6.cpp.hex is not working. The system just put the word bash in front of it.
Kind regards,
Freddy
Hi Shoban,
I was to early.
I am now on 1.2.6 and I will keep you posted.
Kind regards,
Freddy
HiShoban,
I tested the Leds with 1.2.2 and 1.2.6 and it is not working properly.
Sometimes the color change command is ignored.
Some year ago Karan promised me to test it in your environment so that I am sure that nothing is wrong with my hardware.
I also have ramdom port reading errors… I also mentioned this in another threath, but it seems that I am not the only one.
Concerning the uggrade to Raspbian for robots, I need an aditional memory card, because I do not want to take the risk of loosing everything.
Kind regards,
Freddy
Hi Shoban,
I have ordered a new pi3 and a new GrovePi+ startup kit to make sure that I do not have any hardware issues.
Normally it arrives today. I will then use it with Jessie…
As indicated 1.2.6 is not functioning with chainable leds.
Has the 1.2.6 firmware been tested with the DHT temperature and humidity sensors?
I have 2 sensors, a blue one and a white one (I changed the sensor type in my simple python program to test).
None of them seems to work with the 1.2.6. Is this a known issue?
As this is now going on for a very long time and no solution is provided or even foreseen in the near future i would appreciate your honest answer to the following questions:
For the last 2 days I am posting results from what I tried but it seems that nobody is reading my messages or bother to answer them.
I also posted another issue concerning unstable port reading.
Again, we know it is a reproducible problem, so I would like to know if there is a recommended python based workaround or solution for it. I posted in a previous threath how I handled t, but again it is not bullet proof.
Last but not least, I am from a small country Belgium, and it is very difficult to purchase a single GrovePi+ board here (startup kit is no problem). The prices they use are also very high comparing to the US especially your preferred dealer in France is ripping people off.
Have you any idea what the import taxes (in %) in Belgium would be if I purchase directly from Dexte?
Kind regards,
Freddy
@cluckers,
Sorry for taking this long to reply back. I had missed this post.
I just tested the chainable RGB led’s at my end and it seems to work. I think it has been working for some time and we also have a small project that uses it here.
Can you try out the following:
sudo chmod +x firmware_update.sh
then run it :
sudo ./firmware_update.sh
After this, can you check the firmware version from here and make sure it is 1.2.2. (I still have to test it in 1.2.6 and 1.2.7)
Next try out the two examples here other than old_grove_chainable_rgb_led.py which is there only for historical purpose.
Can you let us know if it works any better. Also, can you start with 4 Chainable LED’s because that is what we have tested with.
There are a few more pointers that you should be careful about:
Coming to the shipping and import duty, they are directly handled when the package enters your country, and most probably you’ll be charged the import duty depending on the import rules and regulation in Belgium.
Do let us know if this helps.
Hi Karan,
Thanks for your message.
So far I tested the following with my new raspberry 3 and grovepi+ 1.2.7
Chainable leds: I used a 4 chain of leds (not 10 yet) and it worked as expected. Congrats, I am a happy person with this esult.
Port reading: I did a first test and it was without errors. However the test was very brief but I will do a more deep test in the near fuure.
I have to do some more testing with my Pi 2 and the old grove board, but I suspect the GrovePi board to be defective. Meybe that was blocking me already from the beginning. I had problems from the early start and needed to make a lot of workarounds for the port reading problem.
I will keep you informed.
Kind regards,
Freddy
Hey Freddy,
Glad to hear that the chainable LED’s are working for you. I think with 10 LED’s you have to be careful with the power supply.
Regarding the older GrovePi, technically there should be no difference in how the hardware is arranged. Most of the changes are only aesthetic. Can you try uploading a new firmware to the GrovePi and see if that helps.
Do let us know how it goes for you when you get a chance to test it in depth.
Hi Karan,
I now had time to do some in depth testing.
I use 4 chainable leds and still have some errors.
I have a program in Python that I run for several days.
When the ‘sleep’ time is 0.5 sec, the leds are frozen in a certain status after a while.
When this period is increased, it seems to work better.
Please advice.
I have another question.
Since the barometer BMP180 is discontinued, can I use the BMP280 instead.
Are there changes in the python script required to do so?
Kind regards,
Freddygrove_chainable_rgb_led._MyTest3.py (2.2 KB)
@cluckers,
Can you run this and tell us which firmware version are you running . When you say they were frozen, what did you have to do to get them working normally.
We have not tested the BMP280 and do not have examples for it yet. However, it looks like there are examples avialable for the sensor here and here. You can give it a shot. You can also try out the high accuracy pressure sensor here, though this one is a little costlier.
Hi Kara,
The firmware version I use is 1.2.7.
When the problem occurs, the only solution is to completely shut down the system, leave it without tension for a while, and restart everything again.
Kind regards,
Freddy
Hi all
I have a similar problem however I am running 20 chainable RGB LEDs. firmware version 1.2.7. If I run a short script such as the test script multiple times ( like 3 times ) in a row, first the LEDs go crazy then they freeze in place. running anything further does change some of them but not the correct ones and not to the correct value. up until then everything works. To fix this I have to reboot as nothing seems to correct them again.
all the best
J
Hi Karan,
Is somebody working on a solution for this?
It’s more than one year now and things are not going better.
Maybe it would be a good idea to have some kind of command to re-initialize the Led’s periodically.
I tested the current init command and executed the command every 10 minutes, but than the error is even more frequently.
Getting a bit frustrated from it.
I have no other solution because it is a great way to monitor the status of things.
I now also only change the colour only when there is a change necessary.
Otherwise I do not update the colours.
Kind regards,
Freddy
Hi somebody…
Any news?
It is definitely still not working.
I am trying with delays and so on but for a strange reason this is also not the solution.
HELP
Freddy
Hi Karan,
Any news?
I did some additional testing.
When the LED chain is connected in the highest digital port (number 7) and all other digital sensors to lower ports, it looks like things are going a bit better.
Does that makes any sense to you.
Please be so kind to at least try to answer this post.
For me it is important to know if I should abandon the chainable LED story or not…
Ragards,
Freddy
Hi, me again…
I discovered another weird thing…
If an RGB display is connected to the system as well and you issue a led colour change just before a change of colour for the display, the LED’s all go into a random state, whatever LED you changed the colour before…
Just trying to help and indicate the different errors I encounter.
Maybe somebody out there is reading this and maybe it is helping to solve a problem.
regards,
Freddy
@cluckers,
I am sorry, I had missed this post . We only have 4 of these LED’s at our end so have been able to test only on them. Are the problems that you encounter dependent on the number of LED’s or has it mostly been random till now.
@cluckers:
Would you be comfortable working with C. I have been working on a library in C which is very rudimentary but works and it is directly controlled by the Pi, so might work better.
Hi Karan,
Good to hear from you again.
I also use 4 leds to test.
Errors are random, but the change to a higher digital port makes it more stable.
The problem is that one needs to test it together with other sensors.
I use switches, temp and relais.
vriendelijke groeten,
Freddy
Hi Karen,
Sorry, I have no C experience…
vriendelijke groeten,
Freddy