Recent posts

#1

UEXT / Re: Changing I2C address of MO...

Last post by ilario - Today at 11:55:06 AM

You need to power down the board, close jumper PROG, power up the board then issue the change address command, then power down the board, then open the jumper PROG and finally power and check new address.

Thanks for the clear instructions!

Are you sure it is on I2C port 1? It can be I2C 0 or 2?

Yes, using i2cset I can open and close the relay using port 1 (which is UEXT).

Interestingly, I can open and close the relay regardless if the PROG was closed or not (changing the state of PROG jumper, then powering up the MOD-IO2 and then running the i2cset command).

I replicated all of this on two MOD-IO2 boards.

Sure you can try modio2tool, there is explanation on how to compile and use:
https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/UEXT%20MODULES/MOD-IO2/linux-access-tool

Ok!
I tried to use the precompiled one and it gave an unexpected error:

Code Select Expand

# chmod a+x ./modio2tool
# ./modio2tool
bash: ./modio2tool: No such file or directory
but then I realized that it was because it was the 32 bit executable and I am on A64-Olinuxino so it is a aarch64 platform so I compiled it with "make" and now it works

Before trying with modio2tool, I checked it source, and noticed that it was using an undocumented 0xF0 data address, and that this address was used also in the firmware in the OLIMEX.h file:

Code Select Expand

#define SET_ADDRESS    0xF0
So I tried to add the data address 0xF0 to the i2cset command, and it worked

unplug power
close PROG jumper
plug power
i2cset 1 0x21 0xF0 0x22
unplug power
open PROG jumper
plug power
and now the MOD-IO2 has address 0x22

I double checked that if the PROG jumper is open it does not work, and it does not, as expected.

So I would suggest the following changes in the documentation:

In MOD-IO2 user manual revision E:

page 13, section 2.4.2 replace

Code Select Expand

i2cset 2 0x21 0xHH
with

Code Select Expand

i2cset 2 0x21 0xF0 0xHH
page 19, section 5.6.1 remove the whole section. From my tests it does not look like the PROG jumper has that described function.

In the readme of the firmware version 4.3:

page 11, section 4.10 correct as above including 0xF0.

Thanks!

#2

ESP32 / Re: ESP32-WROOM-32E-N8 - LoRa8...

Last post by LubOlimex - Today at 10:53:01 AM

If you are using Olimex LoRa868 - you need to check your software for the state of PA_BOOST. Did you disable PA_BOOST mode in the library? Again check here:

https://forum.mcci.io/t/olimex-mod-lora868/264/2

#3

UEXT / Re: Changing I2C address of MO...

Last post by LubOlimex - Today at 08:21:05 AM

You need to power down the board, close jumper PROG, power up the board then issue the change address command, then power down the board, then open the jumper PROG and finally power and check new address. Are you sure it is on I2C port 1? It can be I2C 0 or 2?

Sure you can try modio2tool, there is explanation on how to compile and use:

https://github.com/OLIMEX/OLINUXINO/tree/master/SOFTWARE/UEXT%20MODULES/MOD-IO2/linux-access-tool

#4

ARDUINO / Re: Olimex BC66 Registration k...

Last post by celemtine - Today at 06:55:26 AM

Hi,

I have an Olimex BC66 Dev Kit.
Sim: Vodafone Italy NB-IOT that operates on band 20. MCC: 22210

I try to attach the bc66 to network using the following commands.

Code Select Expand

AT+QSCLK=0
ATE1
AT+CSCON=1
AT+QBAND=1,20
AT+CFUN=0
AT+QCGDEFCONT="IP","m2m.vodafone.it"
AT+QRST=1
AT+QSCLK=0
ATE1
AT+CSCON=1

but I get the following results:

Code Select Expand

F1: 0000 0000

V0: 0000 0000 [0001]

00: 0006 000C

01: 0000 0000

U0: 0000 0001 [0000]

T0: 0000 00B4

Leaving the BROM



RDY

+CFUN: 1

+CPIN: READY

+CEREG: 2,,,,,0,0
AT+QSCLK=0

OK
ATE1

OK
AT+CSCON=1

OK

+CSCON: 1

+CSCON: 0

+CSCON: 1

+CEREG: 3,,,,,0,15

+CSCON: 0

+CSCON: 1

+CSCON: 0

+CEREG: 3,,,,,0,14

+CSCON: 1

+CSCON: 0

+CSCON: 1

+CSCON: 0
 
+CSCON: 1

+CSCON: 0

+CSCON: 1

+CEREG: 3,,,,,0,15

+CSCON: 0

+CSCON: 1

+CSCON: 0

+CEREG: 3,,,,,0,14

As you can see the registration keep getting denied ( stat value: 3).

I've tried any possible thing on earth and made sure that the SIM was OK by calling  the operator, which confirmed to me that everything was alright.

Any possible idea or tip? I will try to flash the A11 firmware on the dev kit but Quectel told me that this would not solve the problem. Any tip is appreciated

Edit: the APN is "m2m.vodafone.it" which is correct

You mentioned that the APN is set to "m2m.vodafone.it," which seems correct. However, double-check the APN settings to ensure they are configured correctly.Make sure that the area where you're testing the device has adequate NB-IoT coverage provided by Vodafone Italy on band 20 (800 MHz).

Try manual network selection: Use the AT+COPS command to manually select the Vodafone Italy network. This can sometimes help with registration issues.

Check device firmware: Ensure that your Olimex BC66 Dev Kit has the latest firmware installed. If not, consider updating it to see if that resolves the issue.

#5

ESP32 / Re: ESP32-WROOM-32E-N8 - LoRa8...

Last post by Steff - May 14, 2024, 08:52:58 PM

OK that's great. After taking it all apart and rebuilding the whole setup, i now can read the registers with this
https://github.com/StuartsProjects/SX12XX-LoRa/tree/master/examples/SX127x_examples/Basics/2_Register_Test

And the MCCI LMIC 4.1.1  does not crash on the ESP32

But I do not see a Join-Request. Not on Thingpark, not on TTN.
The APPEUI, DEVEUI and APPKEY are correct. I've tested this with a LilyGo Lora32 1.6. This works.

The MCCI debug output is this

Code Select Expand

RXMODE_RSSI
691735: EV_JOINING
691741: engineUpdate, opmode=0x4
802330: engineUpdate, opmode=0x4
802349: EV_TXSTART
802429: TXMODE, freq=868500000, len=23, SF=7, BW=125, CR=4/5, IH=0
1118044: setupRx1 txrxFlags 00 --> 01
start single rx: now-rxtime: 4
1118678: RXMODE_SINGLE, freq=868500000, SF=7, BW=125, CR=4/5, IH=0
rxtimeout: entry: 1119204 rxtime: 1118669 entry-rxtime: 535 now-entry: 5 rxtime-txend: 312375
1180544: setupRx2 txrxFlags 0x1 --> 02
start single rx: now-rxtime: 5
1181178: RXMODE_SINGLE, freq=869525000, SF=12, BW=125, CR=4/5, IH=0
rxtimeout: entry: 1195530 rxtime: 1181169 entry-rxtime: 14361 now-entry: 5 rxtime-txend: 374875
1195559: processRx2Jacc txrxFlags 0x2 --> 00
1196212: EV_JOIN_TXCOMPLETE: no JoinAccept
So if some one has an idea, please let me know. If i should open a new thread, let me know.

I've spent so many hours on this, i'm probably overlooking a detail.

#6

UEXT / Changing I2C address of MOD-IO...

Last post by ilario - May 14, 2024, 07:12:59 PM

Dear all,
I recently (approx 6 months ago) bought a few MOD-IO2.
Using only one, I can use the relay just fine
But I did not manage to change their I2C address so that I can use more than one.

Currently I have 4 of them connected in a line to a A64-OLinuXino-2Ge8G-IND.

Reading the documentation, seems that closing the PROG jumper has two functions:

• from user's manual revision E section 5.6.1 "When closed this jumper allows addressing a single MOD-IO2 (the one with the closed jumper) over all others stacked to it – since initially all connected MOD-IO2 boards have the same address."
• from user's manual revision E section 2.4.2 "Changing I2C device address [...] i2cset 2 0x21 0xHH [...] Note that PROG jumper must be closed to be able to change the address."

But for me it had neither of the two functions (or maybe I misunderstood).
Most importantly, I could not change the I2C address using the

Code Select Expand

i2cset 1 0x21 0x22 command (I tried booting the MOD-IO2 with the jumper set, setting it afterwards and then launching the command, power cycling the MOD-IO2, and it is still at 0x21 regardless of what I do).

In the manual I saw that the address can also be changed with modio2tool, should I use that instead?

Thanks!

#7

ESP32 / Re: ESP32 poe noise

Last post by korneo - May 14, 2024, 06:40:58 PM

image

The above image was measured on the 3.3V line(as close to the wrovere chip as possible) using a Lecroy ZS1000 active probe while the Poe2 board was powered using the Poe comming from a hp 1820(J9982A) switch.

I suspect the noise is comming from the TX4138 buck converter, however the reason why i do not know.

similair noise is measured on a olimex esp32 poe iso board, however it is not as significant as this one.

#8

ESP32 / Re: ESP32 poe noise

Last post by LubOlimex - May 14, 2024, 04:23:15 PM

By the way attaching oscilloscope to ESP32-POE2 powered by PoE is risky, ESP32-POE2 is not isolated and it is ground loop risk.

#9

STMP1 / Re: Olimex STMP1 SOM - Error s...

Last post by LubOlimex - May 14, 2024, 01:16:00 PM

Wait did you wrote that you have STMP LIME boards? The image and this forum thread is for STMP SOM boards, sorry my bad. It is normal to have errors since the image is suitable for only SOM boards.

We haven't noticed similar problems with LIME boards. Yours can be different problem.

#10

ESP32 / Re: ESP-POE having problems wi...

Last post by djpeterlewis - May 13, 2024, 11:21:47 PM

Maybe try with GPIO32 or GPIO33

I tried GPIO32 with the same result. A random flash , sometimes all 100 pixels and other times just a few, always White . WS2815B. I timed it to see if they were equally timed , but they are not