Only way I could fix it was to roll back to Atom ver 1.38.2 Then untick 'Automatically Update' in your Core Settings.

@bmarkus I'm using Thingpark actility network server with regional settings of Eu868 europe regional settings.

@morrison Also LoPy4 Pinout Diagram should be helpful.

@robert-hh (sysname='LoPy4', nodename='LoPy4', release='1.18.2.r7', version='v1.8.6-849-df9f237 on 2019-05-14', machine='LoPy4 with ESP32', lorawan='1.0.2', sigfox='1.0.1')

@jcaron There is no problem with uplink channel. But i'm facing problem with downlink which is coming at channel 869.525 Mhz witjh SF12 and class A and im not able to receive at node. By the way gateway is cnfigured for all its available channels it's 16 channel gateway in which it consists of 3 uplink and 1 downlink european channel configured.

@prashanth please edit your post and add ``` alone on a line before and after your code so it is properly formatted. Or use one of the “code” buttons in the editing toolbar. What network are you using? What gateway? Can you show your gateway logs (including channel/frequency and SF/data rate)?

@jcaron Many thanks. I don’t know that. That was the problem ... This in combination with powering over usb results in a circuit shorten...

@Emmanuel-Florent Are you sure? The link still leads to https://github.com/pycom/pycom-documentation/blob/master/pytrackpysense/installation/pycom.inf [image: 1562846086436-link.png] [image: 1562845726210-404.png]

If you are saving the session information to nvram then you can use the lora.nvram_erase() to remove them, then you'll need to do a join to be able to send more data. Andrew

@robert-hh Thank you, that worked well! W01 is running with new firmware and that obviously also solved the SD card problem. It is now being mounted peacefully. I am very happy now :)

Maybe there is an issue with your board that's why some error messaging are displaying or there could be a hardware failure,get it checked from some expert technician.

I have encountered similar problems with a Wipy connecting to MQTT broker. Connection was perfect at my home office in a rural setting, however, not so good when tested at a bay in an industrial area. The signal was good at -40 but neighbours were transmitting on same channel with hidden SSID. The noise floor exceeded my signal. A spectrum analyzer would be helpful or even an app on your mobile could help track the problem down. You may only need to change the channel on your router. In my case not a Wipy problem.

@jcaron well I need the accel, because it's a "wake on shake" use-case. Everything you mentioned is already tested. Of course I tested by powering the device via the JST and not the USB port. Same results. Also I tried exchanging the FiPy by a LoPy4. Also the same. But then I switched the Pysense by another and all of a sudden it worked. Looks like a hardware fault. Nevertheless thanks for your suggestions!