Delay in sending AT command

[Lars van Velzen]

Hello,

I'm trying to register to the LTE-M network of T-Mobile. Although this does not work I'am unable to review the AT commands since these are printed with some errors. It might be because of the standard delay but the command on the Pycom documentation is not workiing. The retrun i get from lte.send_at_cmd('AT+COPS=?') is:

+COPS: (2,"20416","20416","20416",7)(1,"NL KPN","NL KPN","20408",7)(1,"vodafone NL","voda NL","20404",7),,(0,1,2,3,4),(0,1,2)

I already tried lte.send_at_cmd('AT+COPS=?', [delay=1000]) this results in an invalid syntax.

Is there a way to adjust the command to be able to see the entire message?

Thanks,

Lars

[livius]

@Lars-van-Velzen

brackets [] tell that something is optional to specify.
when you decide to specify it you must put it without brackets

lte.send_at_cmd('AT+COPS=?', delay=1000) 

[Lars van Velzen]

Hello,

Thanks for the reaction.

I tried the line but it is not working.

Any more suggestions?

Thanks!

[livius]

@Lars-van-Velzen

i see that in recent firmware it is solved differently. Do not specify delay at all.
@Gijs docs should be fixed i think

[Lars van Velzen]

Is there an other soltion to view the entire command?

[Gijs]

The supposed 'delay' is (and always was) implemented as a timeout. The keyword argument was changed from 'delay' to 'timeout' some time ago to better reflect the functionality.
The AT commands are sent immediately after the function call.

I will change the docs to reflect the correct naming

[jcaron]

@Gijs Don't forget to keep a history of the change in the documentation. E.g. "Before version X, the timeout argument was named delay". There are still plenty of people using lots of different versions for a number of reasons...

[Lars van Velzen]

@Gijs Thanks this solved the problem!