NB-IoT in Hungary?

[combaindeft]

@paul-thornton Yeah, I know about that, I was one of them that has already logged that issue :-)

As for the The output you saw, is from running the latest development build

Pycom MicroPython 1.20.0.rc0 [v1.9.4-9f0896a] on 2018-12-08; FiPy with ESP32

And this time around both api.wia.io and www.google.se is giving the same result.

LOG: Attaching to LTE network ... OK
LOG: Check LTE signal streanght (RSSI): +CSQ: 25,99OK
LOG: Getting IP address: +CGPADDR: 1,"10.17.191.218"OK

+CGDATA: ("PPP")

OK

LOG: Connecting on LTE network  OK

-----------------------------------------------------------------------------
LOG: Initializing DNS query of domain name(s)
LOG: api.wai.io
('184.109.15.128', 80)
LOG: api.wai.io
('184.109.15.128', 80)
LOG: api.wai.io
('184.109.15.128', 80)
LOG: www.google.se
('184.109.15.128', 80)
LOG: www.google.se
('184.109.15.128', 80)
LOG: www.google.se
('184.109.15.128', 80)
Pycom MicroPython 1.20.0.rc0 [v1.9.4-9f0896a] on 2018-12-08; FiPy with ESP32
Type "help()" for more information.
>>>```

[danielm]

@combaindeft
Are you getting DNS server IP address from the network? You can check with 'AT+CGCONTRDP' command.

From Sequans AT command manual:
The execution command returns the relevant information <bearer_id>,
<apn>, <local_addr and subnet_mask>, <gw_addr>,
<DNS_prim_addr>, <DNS_sec_addr>, <P-CSCF_prim_addr>,
<P-CSCF_sec_addr>, <IM_CN_Signalling_Flag> and
<LIPA_indication> for an active non secondary PDP context with the
context identifier <cid>.

[combaindeft]

@danielm

Hi,

Here is what I'm getting:

>>> send_at_cmd_pretty('AT+CGCONTRDP')

+CGCONTRDP: 1,5,"lpwa.telia.iot.mnc020.mcc238.gprs","10.17.160.100.255.255.255.255","","","","",""

OK

>>>

[combaindeft]

@danielm

Also, having e-mailed with them (Telia) a bit, I do know that the GSSN's ip-address is 217.214.135.1

Is there a way to set the DNS_prim_addr to it?

[danielm]

@combaindeft said in NB-IoT in Hungary?:

Is there a way to set the DNS_prim_addr to it?

There is no such command in the AT command manual. There may be some undocumented command. I am testing in network of Slovak Telekom and DNS servers are not provided by the network here as well.

Another approach may be to write DNS lookup library.

[bmarkus]

Just wanted to know is it whorth to buy any NB-IoT capeble PyCom module for Hungary.ű

Guys, it is great you hijacked my topic, really said to see it. Why don't you open a new thread instead?

[combaindeft]

@danielm

Thanks for the great info ... but I don't think a DNS Lookup library is worth is ... since the NB-IOT network via Telia is UDP only ... ergo "one-way" communication ... so, a device is only allowed to send but never receive :-(

(and it does make sense, since IOT devices are ment to be low-power and not use a lot of broadband ...)

[combaindeft]

@bmarkus

Right now, everything is in development and it all depends how far they have come in Hungary ... maybe call all our Telecom Operators in Hungary and ask if they support NB-IOT?

If you are lucky, they'll say yes - they do ... and at the same moment starts your next headache ... will the help you in telling you how to get things working with their network?

And 3rd headache, does the board you buy support them ...

So far from all the testing, the PyCom FiPy is almost there ... in sweden at least ... I can attach to the network and connected (get an iP) ... but the remaining question now is how to send data over the connection ...

Right now ... attaching seems oK ... as we can continue playing with sending AT-commands to the modem ...

But when we "connect" ... and it goes into setting up a PPP-connection (ergo a "data"-link ... like on your phone when you browse the webz...) ... it doesn't work.

Here I suggest to PyCom to add a usocket.AF_NBIOT option in USocket ... as they've done with SIGFOX and LORA ... to forcefully direct the data through NB-IOT

s_nb = usocket.socket(usocket.AF_NBIOT, usocket.SOCK_DGRAM, usocket.IPPROTO_UDP)

(mainly as we we are testing with LoRa, Sigfox, WiFi and Bluetooth ... you'd like to tell the sockets what connection to use ... and not let the "socket" decide for you ...)

Anywho ... hope it helps you a bit.

And as for hijacking your topic ... sorry a-bout that ... but have already started a topic ... and old topics get berried quite quickly in this active forum :-)

[danielm]

@combaindeft
UDP-only NB-IoT network is bidirectional as well. DNS protocol works over UDP :)

[combaindeft]

@danielm

From my testing so far, on the Network I'm on ... the UDP connection seems only to be one-direction :-)

But I'll stand corrected :-)

[Paul Thornton]

@danielm Just to clarify. Ive asked.There is no undocumented command to set a dns server if not already provided by the network operator. (At the moment)

[danielm]

@paul-thornton
Hi Paul, thanks for clarification. I think it would be helpful if Pycom could implement DNS client which would work independently from NIC's API and which would accept DNS server IP address as an optional parameter.

[bmarkus]

@combaindeft Telekom announced publicly 60% national, 100% Budapest coverage. Question is not about coverage but PyCom usability. I can use e.g. QUECTEL without any problem.

[combaindeft]

@bmarkus said in NB-IoT in Hungary?:

@combaindeft Telekom announced publicly 60% national, 100% Budapest coverage. Question is not about coverage but PyCom usability. I can use e.g. QUECTEL without any problem.

Today I had a break-through and can send data via AT-Commands ...

Though, to make a proper data-connection and use USocket to send data ... that it's up to PyCom to add support for handling their network (had a talk with Telia here in Sweden today regarding their NB-IOT network).

So yeah, question is how fast PyCom can add support for all operators data Networks around the globe.