Gpy wont attach to LTE but Fipy does

[jcaron]

@newmicropython What network are you trying to connect it? Do you know which band(s) it uses?

The 1.0 hardware versions had limited band support, see https://forum.pycom.io/topic/4869/band-support-for-gpy-and-fipy for details. If you need support for bands not supported by 1.0, you can send it to Pycom for upgrade.

Where did you buy the boards from?

[robert-hh]

@newmicropython As far as I can tell, removing the jumpers would only be required for FiPy. But according to your first post your trouble is with a GPy.

[jcaron]

@robert-hh The issue is that @diepducle "hijacked" the thread with a separate question. The initial question is indeed about not being able to attach using the GPy 1.0 while the 1.2 FiPy works. The discussion about uploading the code, expansion board, jumpers etc. is unrelated... :-(

[newmicropython]

@jcaron said in Gpy wont attach to LTE but Fipy does:

@newmicropython What network are you trying to connect it? Do you know which band(s) it uses?

The 1.0 hardware versions had limited band support, see https://forum.pycom.io/topic/4869/band-support-for-gpy-and-fipy for details. If you need support for bands not supported by 1.0, you can send it to Pycom for upgrade.

Where did you buy the boards from?

Im trying to connect to Telus in Canada i have a few trial sims. I am using band 28 for all tests which from the docs is supported in all versions of gpy. I bought the gpys from Mouser so if i cant get them to connect this week i will just return them.

I was just wondering if there was something i missed in any firmware or code that my fipy connects and works great but gpy wont attach. they were both sitting on my desk using the same sim cards. i have 3 sims and tried them all in each device. the fipy connected with each sim card so i know its not the sim cards. I used the same antennas, expansion boards,code for both.

[jcaron]

@newmicropython Are you sure you are using band 28? The information I find says either bands 2, 4, 12 or bands 2, 4, 7, 12, 13, 17, 29.

As different bands may be available in different locations (based on cell tower equipment, distance from tower, and obstacles between the tower and you), it's quite possible you could actually only connect using bands that are not support by the 1.0 hardware (e.g. bands 2, 7, 17, 29).

[newmicropython]

@jcaron
i can try another band out.
but my script below with the fipy was on band 28.

if we specify the band would it connect to another band if it was not available?

[robert-hh]

@newmicropython From the code that is hard to tell. In the code, first the command AT!=""clearscanconfig" is issued. Then the band parameter leads to the command AT!="RRC:addscanband=xx" to be sent to the modem. If you specify a band, this command is sent for just that band. if you omit the band=xx parameter, then trhe addscanband command is sent for the bands 3, 4, 12, 13, 20,28, and for newer modem firmware for bands 5 and 8.

[diepducle]

@gt1 Yes, my FiPy is V1.0.

I already solved this problem by upgrading the modem firmware. As you can see the result as follow:

[diepducle]

@newmicropython Hi, thank you for your support. I've already fixed my problem by upgrading the modem firmware.

Now I am using your code to connect to LTE network but I got stuck at "attaching step", as you can see in the picture below.

I am trying to connect to Telstra in Australia and I think the band 28 is accurate but I dont know what is "apn"? Could you please help me with this line of code: "lte.attach(band=28,apn="telstra.m2m")"?. Many thanks.

[jcaron]

@diepducle It would be great if you asked your own questions in a separate thread rather than mixing your questions with OP's initial question, it makes things quite difficult to follow for everybody.

[diepducle]

@jcaron I am so sorry about that. It is my first time to use the forum. I will create a new thread. Thank you for reminding me.

[Youssef Elwakil]

Bumping this if anyone knows how to fix I have updated to the latest firmware as well