@shishir said in Lopy4 indoor range: On Cayenne, chose LoRa-> The Things Network->Cayenna LLP That was the missing link. Thanks alot

@siejak simple use e.g.: try: s.send(data) except: connectToRouter()

@nilam Just to be pedantic, I simplified hexdump a bit. This is old code, collected when I started with Python. FILTER=''.join([(len(repr(chr(x)))==3) and chr(x) or '.' for x in range(256)]) def hexdump(src, length=16): N=0; result='' while src: # loop through string s,src = src[:length],src[length:] hexa = ' '.join(["%02X"%x for x in s]) s = ''.join([FILTER[_] for _ in s]) result += "%04X %-*s %s\n" % (N, length*3, hexa, s) N += length return result I have my doubts whether I did all of that myself at that time, especially the FILTER= .. expression.

@livius I made a version in which you can control the join behaviour. It is just a handful of code lines. You'll find it here: https://github.com/robert-hh/pycom-micropython-sigfox/tree/otaa I added an optional parameter to join. Edit: While testing it came again to my mind to me that you can achieve the same thing with the standard SW: step1: do an otaa join step2: take the parameters from the web console, use them as ABP parameters and use ABP join then with just the single frequency in the list of channels. If you then save the state to nvs_ram, you do not have to call join again. The keys will be restored by nvs_restore(), which you must call anyhow to set the counters.

@wstallwood It sounds like in your application OTA updates would be the easiest. With firmwares older than 1.7.2.b1 you can use the generated appimg.bin to do a OTA update, after that you just need to use the regular firmware bin file for OTA. Please checkout this example: https://docs.pycom.io/chapter/tutorials/all/ota.html

@robert-hh It seems to be awake again, whatever caused it to look like that for me.

@fajriansyah I do not know if some "minimal" client exists for micropython. But is it required? Better run some listen socket on your server. And then your Lopy will send messages to this socket and it connect to jour database and store there data. It can be e.g. windows service apllication, webserver application e.g. on IIS, Apache + php ....

@robert-hh Thanks. I did the os.mkfs('/flash') and then ran Pymate on my phone to re-establish a WiFi connection and reinitialize the chip (repopulating with main.py and boot.py) that I now see in ftp.

@robert-hh Robert, you were completely right. Removed the references to the pysense and everything runs fine. I should have known ... Sorry. Thanks again!

@jonasde For verification, you can use a different and dump terminal software like Putty (Windows), screen (mac, linux) or picocom (Linux). Just make sure that any kind of handshake is disabled. For fil etranfer you can use an ftp client like filezilla or fireftp.

@ahelllycan I think we would need to see code, or general overview of your process. At the moment we are guessing. But @jcaron is right. You should have a call back on message receive and you choose when to send messages based on other criteria. The rest of the time you will be sleeping or waiting.

@jcaron Hi Jcaron, Thanks for your explaination. We'll make te intervals longer so that we don't breach the regulations. I understand what your saying, but could you describe how you calcluate the collision rate? The strange thing is, that almost every time it is a single node who is not recieved well by the gateway. Not always two nodes at the same time. They are indeed close to each other, but we're now testing it with one node, to see how that works. We'll add a random interval. I'll post if this changes solved our problem.

@robert-hh thank you, I used pin.value(x) and it worked, I want to simulate an oscillation using to pins, first I will put the first pin to 1 and the second pin to 0, after a time I will interchange the values, I don´t know if this is the right way, and I don´t know which lopy pins can be better for this purpose.

@jcaron It's powered off of my desktop Windows 10 PC. It's most likely a timing issue in the FW. My guess would be that during the import a read value is getting corrupted. I know there is no syntax error in the code. the same code can run for a week with a deepsleep reboot every 30 seconds.

@seb OK, I think you are right that it is a power supply issue. I've tried the same cable directly with a USB power supply and haven't seen the issue happen again. So it might be for some reason that the Macbook USB port (or adapter) cannot supply enough power. Will try it with a LiPo connected.

Nice! Thanks for sharing!

@jmarcelino said in US915 OTAA - Cannot communicate with packet forwarder: LoRaWAN network server Hi @jmarcelino. Thanks for your help. I'm using the brocaar's one network server https://www.loraserver.io/ I have copied below the docker-compose config file content: version: "2" services: app: build: . expose: - "8090" ports: - "8090:8090" volumes: - .:/app depends_on: - gatewaybridge - loraserver - appserver - postgres - mosquitto - redis postgres: image: library/postgres:10.2 volumes: - ./db/pgdata:/pgdata ports: - "54322:5432" environment: - POSTGRES_PASSWORD=loraserver - POSTGRES_USER=loraserver - POSTGRES_DB=loraserver - PGDATA=/pgdata command: -p 5432 elasticsearch: image: elasticsearch:2.4 container_name: elasticsearch environment: - cluster.name=docker-cluster - bootstrap.memory_lock=true - "ES_JAVA_OPTS=-Xms512m -Xmx512m" ulimits: memlock: soft: -1 hard: -1 mem_limit: 1g volumes: - esdata1:/usr/share/elasticsearch/data ports: - 9200:9200 # # STARTS BROCAAR SERVERS # loraserver: image: loraserver/loraserver environment: - DB_AUTOMIGRATE=true - LOG_NODE_FRAMES=true - NET_ID=010203 - BAND=US_902_928 - REDIS_URL=redis://redis:6379 - GW_MQTT_SERVER=tcp://mosquitto:1883 - GW_SERVER_JWT_SECRET=verysecret - POSTGRES_DSN=postgres://loraserver_ns:loraserver_ns@postgresql_ns/loraserver_ns?sslmode=disable - JS_SERVER=http://appserver:8003 appserver: image: loraserver/lora-app-server ports: - 8080:8080 environment: - DB_AUTOMIGRATE=true - REDIS_URL=redis://redis:6379 - POSTGRES_DSN=postgres://loraserver_as:loraserver_as@postgresql_as/loraserver_as?sslmode=disable - MQTT_SERVER=tcp://mosquitto:1883 - JWT_SECRET=verysecret - HTTP_TLS_CERT=/etc/lora-app-server/certs/http.pem - HTTP_TLS_KEY=/etc/lora-app-server/certs/http-key.pem - AS_PUBLIC_SERVER=appserver:8001 gatewaybridge: ports: - 1700:1700/udp image: loraserver/lora-gateway-bridge environment: - MQTT_SERVER=tcp://mosquitto:1883 postgresql_ns: image: postgres:9.6-alpine ports: - 5432 environment: - POSTGRES_PASSWORD=loraserver_ns - POSTGRES_USER=loraserver_ns - POSTGRES_DB=loraserver_ns postgresql_as: image: postgres:9.6-alpine ports: - 5432 environment: - POSTGRES_PASSWORD=loraserver_as - POSTGRES_USER=loraserver_as - POSTGRES_DB=loraserver_as redis: ports: - 6379 image: redis:4-alpine mosquitto: ports: - 1883:1883 image: eclipse-mosquitto volumes: esdata1: driver: local Then, once the docker servers are running I config the lorawan platform through the web admin ui like this: [image: 1521381818589-screenshot-from-2018-03-18-11-00-47-resized.png] Device profile [image: 1521381870928-screenshot-from-2018-03-18-11-04-07-resized.png] Service profile [image: 1521381909551-screenshot-from-2018-03-18-11-05-00-resized.png] Gateway configuration [image: 1521381946945-screenshot-from-2018-03-18-11-05-28-resized.png] Not sure if that's enough @jmarcelino . Let me know if you need some extra data. Thanks!

Thank you. :)