lora.nvram_restore() OSError: [Errno 122] EMSGSIZE

[Gijs]

Have a look at the example for nvram here: https://docs.pycom.io/tutorials/networks/lora/nvram/

Though I believe your issue has nothing to do with the nvram, but rather with the message size (either too big or too small). I cannot find exactly which line 'line 47' is in the code you attached, but perhaps you can find it yourself :)

[jcaron]

@Etienne-DAL-PRA is the code above the actual code you are using, especially the data being sent? There are limits on LoRaWAN packets which vary based on region, data rate, and more, but 3 bytes should always be possible, especially in the EU868 region, and even more so at DR5.

Can you try without setting the data rate, or setting it to different values?

One thing which may have an influence is the need to send MAC commands (or more likely, responses), but I think it’s quite difficult to get to a point where it would not even allow for 3 bytes of payload (also, I believe payload has precedence over MAC commands).

Did you change firmware release recently? If so, did you join since then? Not quite sure the format of the LoRaWAN state in NVRAM has remained consistent across versions, it could get the stack in a weird state if not.

[Etienne DAL PRA]

@Gijs Hi, I've already look at the example and it doesn't work too for me.

The line 47 is the line "s.send(uplink_payload).

I don't understand why this error appears, is the message size is saved when the nvram_save method is used ?

@jcaron yes this my actual code to test the nvram_save and nvram_restore methods. I don't think 3 bytes will be out of the LoRaWAN limits.

I will try without setting the data rate.

Yes I changed the firmware this week but I didn't try to use these methods before. I will check in that direction too.

Thank you for your responses :)

[Etienne DAL PRA]

@jcaron I've found ! This problem comes from the fact that I flashed the card in "development" mode instead of "pybytes" and I put the version 1.20.2 r0 and it works well.

[John Baxter]

@Etienne-DAL-PRA Please can you advise the steps you have taken? I am having a very similar problem and I'm really stuck. Thank you :)

[Etienne DAL PRA]

@John-Baxter hi ! Yes of course. I'm sorry for the delay.
I used the Pycom Firmware Updater (you can download it there https://docs.pycom.io/updatefirmware/device/).
You need to close Atom or VS Code (the Pymakr console) before doing the upgrade. After you can do the upgrade with the Pycom Firmware Updater, you just need to select the Port and the type of your board.
Then, I chose as type : Pybytes and as version the lastest : 1.20.2.r4. And selected the options :

• Erase during update
• CONFIG partition
• NVS partition

And clicked on Continue.

I hope this helps you if you are still stuck :)

[John Baxter]

@Etienne-DAL-PRA Thank you very much. This fixed it :)

[Jaco Pretorius]

Good day

I have a similar problem. If try to send the string I get the following error. Any help would be appreciated.

Traceback (most recent call last):
File "<stdin>", line 1, in <module>
OSError: [Errno 122] EMSGSIZE

My code:

import socket
import pycom
import time
from network import Sigfox
from machine import Timer
time.sleep(1)

sigfox = Sigfox(mode=Sigfox.SIGFOX, rcz=Sigfox.RCZ1)
time.sleep(1)
s = socket.socket(socket.AF_SIGFOX, socket.SOCK_RAW)
time.sleep(1)
s.setblocking(True)
time.sleep(1)
s.setsockopt(socket.SOL_SIGFOX, socket.SO_RX, True)
time.sleep(1)

sSend = ""
aSigFox_Bits = [0,0,0,0, 0,0,0,1, 0,0,0,0, 0,0,1,0, 0,0,0,0, 0,0,1,1, 0,0,0,0, 0,1,0,0, 0,0,0,0, 0,1,0,1, 0,0,0,0, 0,1,1,0, 0,0,0,0, 0,1,1,1, 0,0,0,0, 1,0,0,0, 0,0,0,0, 1,0,0,1, 0,0,0,0, 1,0,1,0, 0,0,0,0, 1,0,1,1, 0,0,0,0, 1,1,0,0]
for i in range(0, 24):
  iHexChar = 8 * aSigFox_Bits[i*4] + 4 * aSigFox_Bits[i*4+1] + 2 * aSigFox_Bits[i*4+2] + aSigFox_Bits[i*4+3]
  sSend = sSend + str(hex(iHexChar)[2:])
print(sSend)

s.send(sSend.encode())

[jcaron]

@Jaco-Pretorius I believe this is completely unrelated to the original issue in this thread and is just because your encoding loop is incorrect and results in in a frame which is too long. Print the string and it’s length before sending it, it should be quite obvious.

[robert-hh]

@jcaron The sample string has a length of 24 bytes. Besides that, the loop looks overly complicated. If the input has to be a list of 0/1 values, it could be simplified a little bit to

sSend = bytearray(24)
aSigFox_Bits = [0,0,0,0, 0,0,0,1, 0,0,0,0, 0,0,1,0, 0,0,0,0, 0,0,1,1, 0,0,0,0, 0,1,0,0, 0,0,0,0, 0,1,0,1, 0,0,0,0, 0,1,1,0, 0,0,0,0, 0,1,1,1, 0,0,0,0, 1,0,0,0, 0,0,0,0, 1,0,0,1, 0,0,0,0, 1,0,1,0, 0,0,0,0, 1,0,1,1, 0,0,0,0, 1,1,0,0]
for i in range(0, 24):
  sSend[i] = 8 * aSigFox_Bits[i*4] + 4 * aSigFox_Bits[i*4+1] + 2 * aSigFox_Bits[i*4+2] + aSigFox_Bits[i*4+3]
print(len(sSend), sSend)

If is is a constant string, it can be written as:

sSend = bytes([0b0000, 0b0001, 0b0000, 0b0010, 0b0000, 0b0011, 0b0000, 0b0100, 0b0000, 0b0101, 0b0000, 0b0110, 0b0000, 0b0111, 0b0000, 0b1000, 0b0000, 0b1001, 0b0000, 0b1010, 0b0000, 0b1011, 0b0000, 0b1100])
print(len(sSend), sSend)

[jcaron]

@robert-hh I think the goal is to form a 12-byte message (max length of a Sigfox message). Each group of four bits is a nibble, but the conversion from bits to hex to bytes is incorrect.

Pretty sure there’s a much much simpler way of doing it but I’m not in a mood for Python today…

[robert-hh]

@jcaron OK. Then two nibbles must go into one byte. Like;

sSend = bytearray(12)
aSigFox_Bits = [0,0,0,0, 0,0,0,1, 0,0,0,0, 0,0,1,0, 0,0,0,0, 0,0,1,1, 0,0,0,0, 0,1,0,0, 0,0,0,0, 0,1,0,1, 0,0,0,0, 0,1,1,0, 0,0,0,0, 0,1,1,1, 0,0,0,0, 1,0,0,0, 0,0,0,0, 1,0,0,1, 0,0,0,0, 1,0,1,0, 0,0,0,0, 1,0,1,1, 0,0,0,0, 1,1,0,0]
for i in range(0, 12):
  i8 = i * 8
  byte = 0
  for j in range(8):
        byte = (byte << 1) | aSigFox_Bits[i8 + j] 
  sSend[i] = byte
print(len(sSend), sSend)

sSend = bytes([0b00000001, 0b00000010, 0b00000011, 0b00000100, 0b00000101, 0b00000110, 0b00000111, 0b00001000, 0b00001001, 0b00001010, 0b00001011, 0b00001100])
print(len(sSend), sSend)

[Jaco Pretorius]

@robert-hh Thank you