@gldoug I've likewise been disappointed at the lack of information on connecting to Canadian cell networks. I'm a project manager looking at purchasing a FiPy for evaluation purposes. This would be our first cellular IOT project. I'm in Calgary, Alberta and looking to deploy for industrial use in British Columbia. By "sort out the requirements", which requirements are you speaking of? I presume you are talking about communicating with the carrier, is this correct? And how did you contact them? Did you need to purchase a SIM card? If so, from who? Cheers

@seb it looks like the pytrack button wakes the board only if you enable the accel wake up. Since I disabled the accel wake up the button does not wake up anymore. Can anyone can confirm this ?

@jardar Telenor is NB-IoT only we can only work with them on certification when our NB-IoT support is in place. The current estimate is to have a first version of NB-IoT by end of the month.

@jmarcelino Ok....thanks :)

@livius Regards first question: i used the code here: https://docs.pycom.io/chapter/firmwareapi/pycom/network/lte/cat-m1.html... But I did not have any results...The country is Italy and I have the tim sim.. BR

@timh (and anyone else trying to reset) I'm using nbiot have managed to attach and connect to the vodafone network but seem to be able to get the module in a state that it won't accept any at commands frequently - just returns empty strings to all attempts to talk to it or reset it? Is there any way to avoid a machine.reset()? lte.send_at_cmd('AT+CSQ') '' lte.send_at_cmd('AT^RESET') '' lte.send_at_cmd('AT^RESET') '' lte.send_at_cmd('AT+CFUN=0') '' lte.send_at_cmd('AT+CPIN?') '' machine.reset() ets Jun 8 2016 00:22:57 rst:0x7 (TG0WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT) configsip: 0, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:1 load:0x3fff8028,len:8 load:0x3fff8030,len:1728 load:0x4009fa00,len:0 load:0x4009fa00,len:14584 entry 0x400a059c +CSQ: 99,99+CESQ: 99,99,255,255,255,255 <<- modem talking again False getting an nbiot connection attach attempt: 0 OK+CEREG: 5,"2332","024C8C21",7+CEREG: 0OKOKOKOKOK

@seb Everything work fine, after sync again! Thank you very much

Hi, @daniel is currently working on this feature, I cannot provide an exact timeline at this stage.

Hi Did you find out about this? I where also able to connect and send a message to the AWS IoT platform. Then I got a similer error where it continiously report "Socket receive error: -80", but no "Socket send error [Errno 104] ECONNRESET" message.

@Mohsen-Paryavi did you have any luck getting this to work? I'm interest in doing the same, using the Gpy as a LTE Cat-m1 hotspot. Allowing a phone to wifi-call beyond LTE coverage.

@combaindeft B) is clear, since the 3.3 regulator is on the FiPy device. Without that, no power at the 3.3V pin. Due to A) with the rock solid supply through a battery it is hard to accept, that it's a firmware issue, at least of the FiPy. Still, the PyTrack board can be the culprit. Did you try to run the FiPy without the PyTrack board, like on a breadboard with a separate USB/serial interface? Shorting 3.3 and GND should be avoided. P.S.: It's a pity that Pycom does not publish schematics.

@seb Thanks a lot for quick response!

@eric-waai Yes, I know this promise. I already registered, but it' s not there yet. Sequans may not have provided the firmware yet, and Pycom did not start with the device replacement yet.

Hello, Thanks for reporting this issue. We will investigate it. Cheers, Daniel

@jmarcelino That fixed the problem! I did not have a jumper on the RX pins. By demo application I mean that when I plug in the board the green LED flashes, followed by the blue LED every 4 seconds. Thanks a lot for your help!

Those pins are connected to the ESP32 but they are not available on the pin header, they are connected internally on the module. TX = GPIO23 RTS = GPIO18 I will get these added to the pinout diagrams

Sorry to say but those UART pins are not mapped onto test points or external pins on the GPy. They only connect to the ESP32.

Thks jmar, have just save me burning hours.. Cheers dude, pizza's & beers on me!

The library does say it will work with Micropython so reusing some of the code regarding OBDII protocol should be less difficult. However the library is designed for the ELM327 device. Unless you use the device, there will be effort into making the code work with your specific communication method, for example directly using the Pycom CAN interface.