New firmware release v1.13.0.b1 (Sigfox and LoRa coexistency on the LoPy4)

[naveen]

I tried with another USB cable which I used before and it worked! But the other problem is still there, fipy is not sending message to sigfox anymore. Why?

[daniel]

@naveen please go to the Sigfox back-end portal, click on your device (the FiPy in question) and, find the option to "Disengage the sequence number" and click on it. The try sending messages again. The failed update might have messed up the NVM of the device causing a a corruption of the sequence numbers.

[Xykon]

@xykon said:

UPDATE: During internal testing I discovered a bug where, when you try to update/register more than one Sigfox device for the first time using the restart button, the download seems to take forever when updating the second device. I will upload a bugfix for this as soon as possible.

A bugfix for this is now available as a beta release for [LINK NO LONGER AVAILABLE]

[naveen]

@daniel As you suggested, I clicked on the "Disengage the sequence number" option for the registered FiPy device in the SigFox backend but the FiPy still does not send message.
How can I know if the SigFox chip is okay and working? Is there any way to debug whether the messages are being sent?

[daniel]

Hello Naveen,

The only way to know if the device is transmitting is with a Spectrum Analyzer, but I don't think you could have damaged the radio. Please read the Sigfox ID and PAC from the device and tell me what you get:

from network import Sigfox
import socket
import binascii

sigfox = Sigfox(mode=Sigfox.SIGFOX, rcz=Sigfox.RCZ3)

print(binascii.hexlify(sigfox.id()))

print(binascii.hexlify(sigfox.pac()))

Cheers,
Daniel

[naveen]

'@daniel I got this output:

[daniel]

@naveen seems correct. Are you able to revert the firmware back to the previous release? As far as we can test Sigfox is still working OK with this version, but maybe in your case there's a problem. It would be great if you can revert to the 1.12.0.b1 release and test again. Thanks.

Cheers,
Daniel

[pymiom]

@daniel do you have any ideas about the reboots of the fipy? I still have yet to downgrade, but need the Sigfox functionally and concerned it may not be in the version I downgrade to.

Cheers!

[daniel]

@pymiom 1.12.0.b1 also has Sigfox. Have you tried a different USB cable? There are a lot of weird issues which are caused by faulty cables...

[naveen]

@denial How can I revert back to 1.12.0.b1 ? I guess the updater always installs the latest one.

[livius]

@naveen
https://forum.pycom.io/post/3190

[naveen]

Thanks @livius, just downgraded to 1.12.0.b1 using the same link you provided. @daniel it is still same, no message is going to sigfox backend.
Can be it antenna issue?

[naveen]

Also, in the device information at Sigfox backend "Radio Configurations" seems wrong. ( I am in Japan):

Modem manufacturer: PYCOM_device_maker
Modem name: SiPy-14
Modem version: S I P Y 1.0 R
Radio Configurations: RC1

[naveen]

@daniel @Xykon I also updated to the latest version but sigfox is not working. Do you have any idea what could be the reason? Is it bricked?