Important update regarding LTE modem updates

[IOAg]

Not sure when you guys will have an ETA on this issue, yet do you mind providing us an alternate download link for the firmware...

[Ben]

@xykon Any ETA on when the firmware update will be available again? Currently I have a stalled project where I require CAT-M1 availability.

[Jiemde]

@xykon I'm also waiting the firmware update for an NB-iot project, is it possible to have at least news of the progress of the solving issues.

[dan]

Hi everyone,

We are finalising the update process and will be releasing the instructions next week. We spent the past few weeks working on this issue and making sure the update will fix the problems.

Thank you for waiting, check back next week for more details!

[arneme]

@dan Will NB-IoT support for Huawei eNodeB based networks be part of the update? If not, what is the roadmap for that?

[tuftec]

Ok.

The update using the new firmware 1.18.1r1 appears to work. At least the update part anyway.
Thanks

Peter.

[IOAg]

@tuftec I did not see any announcement for the patch. Is that safe to install? Have changed been loaded in github?.
Thanks.
Philippe

[robert-hh]

@ioag The patch was published yesterday, and the github repository was updated. The new version is 1.18.1.r1.
As a statistical irrelevant info: I have build the image from the repository and updated two FiPy's.

[IOAg]

@robert-hh I did succeed in upgrading a couple of fipys. Thanks for your help.

[tuftec]

I also managed to update ok. But this is my first attempt to get NB-IoT working.
I get a message back from the modem indicating that it does not understand the zsp0:npc command.

Anyone else seen this? What does it mean?

Peter.

[dan]

@arneme Huawei eNodeB is supported, but the network operators could have specific protocol requirements.

[dan]

We have released an update (v1.18.1.r1) with updated scripts for modem upgrade. You can find the forum post here with more info.

For the bricked modems, we are still working on the process. We'll make a post here on the forum when it's published.

[apallo]

@tuftec yep, same thing- Command zsp0::npc unknown

[peterv]

@dan Could we get someone to update https://docs.pycom.io/tutorials/lte/nb-iot? As noted by others, the AT!="zsp0:npc 1" command seems to fail now, yet it's still in the documentation. Do we need to replace it with something else?

[tuftec]

Does anyone know what this command actually does? Is it necessary? Where do I find a full reference to all the available commands? I do not like developing product based on assumptions.
These LTE issues have been dragging on for a long time now. Relying on spasmodic responses to forum posts is a very inefficient way for customers to impliment fixes and diminishes confidence in the product quality. Is there a better way to communicate with the Pycom Support team than through this forum.

Peter.

[Xykon]

For the issue with Command zsp0::npc unknown

Please try and replace the following two lines:

lte.send_at_cmd('AT!="addscanfreq band=20 dl-earfcn=6300"')
lte.send_at_cmd('AT!="zsp0:npc 1"')

with these:

lte.send_at_cmd('AT!="addscanband band=20"')
lte.send_at_cmd('AT!="disablelog 1"')

I'm still trying to verify this on my end so any comment on this is welcome.

Additionally I will re-release the old NB1-35351 version as soon as possible.

[Xykon]

@xykon NB-1 version 35351 is now available at https://software.pycom.io/downloads/sequans2.html

The updater.elf file is identical in every firmware package.

[tuftec]

@xykon Thanks for the response.
However I am still confused.

I am working with Vodafone in Australia.
They currently use band 8
So can I now use the following:
lte.send_at_cmd('AT!="addscanband band=8"')
lte.send_at_cmd('AT!="disablelog 1"')

Your specifications indicate that band 8 is supported.

I have been advised by Vodafone that I should not need to actually set the band or channel
"The device should automatically pick the correct band and channel if it is compatible and you generally should not be setting these."

What is the significance of NB1-35351? I have installed NB1-37781. Is this now incorrect?

Having access to some proper documentation would make this process a lot easier.

Please provide clear instructions on how to get this product working with NB-IOT.

Peter.

[danielm]

@Xykon
Are there any Release notes available for NB-1 version 35351?

[tuftec]

@Xykon I have tried the changed commands as you have suggested and still nothing.

I do not see any transmissions in the band 8 uplink frequency area (880 - 915MHz) when using my RF spectrum analyser.

Please provide full details of the AT command sequence required to get this going.

Peter.