May 25, 2024, 01:59:39 AM

Recent posts

#1
STMP1 / Re: Olimex STMP1 LIME - Error ...
Last post by Gaël - May 24, 2024, 05:16:59 PM
> Using the modified SOM image without the AXP209 support on the LIME2 board would will lead to problems. The boards are different.

Indeed I notice a lot of problems with the SOM image but I was able to see that the startup problem disappeared.

> I can ask our Linux developers to make image for the STMP LIME2 board without AXP209 support (similar to the image we made for the STMP SOM board), however can you describe what interfaces and connectors of the LIME board do you use in your setup?

I never use the HDMI and the LiPo battery connector.
I always use the ethernet interface and MicroSD card connector.
MicroSD cards will be replaced by Flash modules soon.
I often use USB port (for Modbus with RS485 or RS232 converter).
I use CAN bus sometimes.
#2
STMP1 / Re: Olimex STMP1 LIME - Error ...
Last post by LubOlimex - May 24, 2024, 11:45:19 AM
The quick power cycle issue is expected behavior. I can replicate it on every board 100% of the time myself. It can't be fixed completely. There are few workarounds like using a battery or another source of power or disabling AXP209.

Using the modified SOM image without the AXP209 support on the LIME2 board would will lead to problems. The boards are different.

I can ask our Linux developers to make image for the STMP LIME2 board without AXP209 support (similar to the image we made for the STMP SOM board), however can you describe what interfaces and connectors of the LIME board do you use in your setup? Some things will not work without the AXP209 support. I believe the HDMI will not work among others.
#3
UEXT / Re: MOD-IO2 relay opening/clos...
Last post by LubOlimex - May 24, 2024, 08:08:03 AM
We haven't measured it but some minimal delay is expected until the command is recognized by the PIC that issues the trigger. Best idea is to test empirically with small delay and increasing if necessary.
#4
UEXT / MOD-IO2 relay opening/closing ...
Last post by ilario - May 23, 2024, 07:30:46 PM
Is there an estimation of how much is the expected time (milliseconds?) between sending the I2C command for opening/closing the relays and the actual opening/closing?

I am using the relays as part of a measurement system, and I got the doubt I should wait some (how much?) time between changing the relay status via I2C and actually starting a measurement.

Thanks!
#5
ESP32 / Re: ESP32-Gateway - cannot run...
Last post by ddog - May 22, 2024, 04:19:48 PM
I am new to Olimex. I am experiencing exactly the same issue. I have a Rev G board. Followed instruction as per Olimex Website.

Receive same error and switched to POE board. Problem solved.

Is there a resolution to this?

Regards,
D
#6
AM3352 / Re: Touchscreen compatibility ...
Last post by grewdraft - May 22, 2024, 06:19:24 AM
Quote from: Christopher23 on May 17, 2024, 07:22:53 AMA good choice for a small touchscreen that is compatible with the AM3359-SOM-EVB-IND is the 4.3-inch LCD with resistive touchscreen from Waveshare. This monitor has a resolution of 480x272 and comes with a USB touch control board, making it easy to connect to the AM3359-SOM-EVB-IND via USB port.

Doesn't sound bad. Can you provide some more information about durability or price?
#7
STMP1 / Olimex STMP1 LIME - Error star...
Last post by Gaël - May 21, 2024, 03:04:58 PM
Hi Olimex!

I have random boot error at starting up with SMTP1 LIME.

On micro power cuts, some boards don't restart.
On 20 STMP157-OLinuXino-LIME2H-EXT (Rev_B) boards in production approximately 5 boards remain frozen after thunderstorm (its are distributed in several places so its do not suffer exactly the same power cuts).

I never have this problem when I reboot a board with a "shutdown -r now" (or "shutdown -r 00:00").

I did some tests and after some power cuts, the board stay frozen on :

U-Boot SPL 2021.04+olimex-1-20240312.134658 (Mar 12 2024 - 13:48:01 +0000)
Model: STM32MP1 OLinuXino-LIME
Init AXP209 PMIC
VDD Core set to: 1350 mv

When the board is frozen, the reset button don't help, the error returns.
A quick power cut doesn't help either.
For the error to disappear, the board need to be unplugged several seconds.
Quick power cuts seems to cause the problem every time.

NB1 : I tried with 1 A and 2 A power supply.

NB2 : I can't use LiPo battery to protect boards against micro power cuts because LiPo are not safe enough in the hot environments where boards are used (wood boiler).

NB3 : I did some tests with the https://ftp.olimex.com/TEMP/SOM-NO-AXP209/STM32MP1-OLinuXino-SOM-bullseye-minimal-20240328-133932.img.7z and I can't reproduce the problem with this image even with quick power cuts.
#8
ESP32 / Re: ESP-POE having problems wi...
Last post by djpeterlewis - May 18, 2024, 08:52:38 AM
Quote from: LubOlimex on May 17, 2024, 01:32:53 PMI think it is some influence between grounds or ground loops. It seems to me it is power related.

How do you power the ESP32-POE? Is it powered from the same source as the LED strip? If not - did you measure if there is voltage difference between the two grounds? Can you give me a diagram or sketch or schematic on how the hardware connection and power supplies and grounds are connected?

Yes I power it from the same power supply with a 5v BUC converter and a 1000uf capacitor near the ESP-POE
#9
ESP32 / Re: ESP-POE having problems wi...
Last post by LubOlimex - May 17, 2024, 04:12:36 PM
If the hardware is perfect then it is probably some issue with the software maybe timings or delays or network throughput, hard to say without details, maybe if some customer has experience with this can help further, but we haven't used neither of those software tools.

My advice is to also post in the communities around ArtNet and WLED, they seem pretty active. I believe they would know more. ESP32-POE is basically ESP32-WROVER + LAN8710A (specifics are that it uses power pin GPIO12 and gets clock from GPIO17) any general info about ESP32 and Ethernet in those communities should apply.

Also maybe try different ArtNet implementations like: https://github.com/hpwit/artnetesp32v2 or https://github.com/hideakitai/ArtNet
#10
ESP32 / Re: ESP-POE having problems wi...
Last post by djpeterlewis - May 17, 2024, 02:40:02 PM
Quote from: LubOlimex on May 17, 2024, 01:08:09 PMAlso this seems like quite often encountered problem for WLED users. Did you check for other users of WLED that reported similar problem like:

https://www.reddit.com/r/WLED/comments/1985svh/wled_esp32_colors_flashing/

https://www.reddit.com/r/WLED/comments/r5jiux/wled_esp32_ws2811_flicker/

https://wled.discourse.group/t/led-strips-flickering-esp32/7756

https://www.reddit.com/r/WLED/comments/16qnuqq/why_there_is_flickering/

https://www.reddit.com/r/WLED/comments/sr6f0h/led_strip_flashing_at_random/

https://www.reddit.com/r/WLED/comments/10ib6hf/random_flickering_issues_with_ws2811/

https://www.reddit.com/r/WLED/comments/139vddw/flickering_and_pulsing_issues_with_ws2812_leds/

https://wled.discourse.group/t/random-flickering/1569

https://wled.discourse.group/t/help-diagnosing-flickering/4046

All of these are either related to a ground or ground loop or a Level shifter not been in circuit.

They are also connecting the board to the LED and using the internal patterns of WLED.
No one of them is doing it through ARTNET Ethernet.

My board connected to my Pixels are working perfectly using internal patterns as they are and no flicker or flash. It only has a problem with Artnet through Ethernet. I have narrowed it down to that.

This is why I wanted to compare the same data path to something similar so the the same code is used by another board to determine if it was the Code or the board. I think my logic on this is good.

Again, there is NO problem from the board to the Pixels when working on the internal patterns or ARTNET through the Wifi Connection. I have run this for 8 hours with not one flicker/flash

If it was the FASTLED lib used by WLED , then it would appear in both internal or Wifi ARTNET modes. The fact it only occurs when using |Ethernet and ARTNET or E1.31 (Also tried that).