Posts made by rogierlodewijks

One more question that, I think fits into this thread (as it helps to get started using this module/kit):

So we can send uplinks using UDP via the T-Mobile CDP. Is this the only way to communicate using the BC-95 (nuSIM) module? What about non-ip or coap? (I already read that UDP comms is only possible via the CDP, not directly to any server.)

Downlink payloads are supported, and need to be scheduled on the CDP via the API.

What about “bulk transfers” (i.e. few kiB’s upto ~100kiB up or down), is this in any way possible using this tech? If yes, does the CDP support this?

Hi Guys,

Just chiming in to say my kit is working as well. Pretty cool stuff, thanks for helping out!
Will move on writing an integration with our back-end service and build something

I Have a lot of questions on the BC95 module (specifically this nuSIM version) so expect to be bothered with those on some other forum thread…

Cheers!

@afzal_m said in How to get your nuSIM dev-kit online?:

I will handover my devkit to our devkit-master

Go Eric go!

Any news yet? No pressure, but I’m very curious

Hi Afzal,

Following your guide to get my T-Mobile nuSIM kit online, but run into some issues with the AT+CGDCONT and AT+COPS commands. Also I noticed standard commands like ATE1 and ATI don’t seems to work, but that might be a ‘feature’ of the custom nuSIM firmware(?).

Thanks in advance for your feedback!

Here’s a log of my terminal:

AT+NRB
REBOOTING

Boot: Signed
Security B.. Verified
Protocol A.. Verified
Apps A...... Verified

REBOOT_CAUSE_APPLICATION_AT
Neul
OK
AT+CFUN=0
OK
AT+NCONFIG="AUTOCONNECT","TRUE"
OK
AT+NCONFIG="CR_0354_0338_SCRAMBLING","TRUE"
OK
AT+NCONFIG="CR_0859_SI_AVOID","TRUE"
OK
AT+CGDCONT=0,"IP","cdp.iot.t-mobile.nl"
ERROR
AT+NBAND=8,20
OK
AT+COPS=1,2,"20416"
ERROR
AT+CFUN=1
OK