@RyverSolare "lora.add_channel()" is for LoRaWan, while you are using LoRa-Raw. You can define your own LoRa-some-name protocol, but the gateway will not be a LoRaWan gateway, using mono or multichannel by means of FHSS (Frequency-Hopping Spread Spectrum), etc.

@colateral I believe that the Pycom firmware uses one core for networking and the other to run the actual MicroPython code, or something similar. Not sure how easy it would be to disable one of the cores altogether. There has been discussion about changing the frequency though, there must be a thread somewhere in the forum with instructions IIRC.

@_grunf Did you figure it out?

@jmarcelino Ok, thank you! Best regards

@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!

What is the ETA for the board?

Hi @panik, The LTE modem only support bands 1, 2, 3, 4, 5, 8, 12, 13, 18, 19, 20, 28 you cannot set the frequency arbitrarily. None of those are in - or confined to - ISM spectrum. There is a relatively new standard called LTE-U to operate LTE in unlicensed spectrum (usually coexisting with WiFi at 5Ghz), but we don't support it.

@fsergeys said in Changing the GPS frequency and configuring which NMEA sentences the gps posts.: GALILEO and GALILEO Full satellites Do you know what the difference between the two is? Also I wonder what is the default configuration for the tracking system? I think the application note regardig I2c mentions to perform a dummy write after each command prior to get back to reading see my example here: https://forum.pycom.io/topic/2442/pytrack-and-gps-balloon-mode/3 and the sequence chart in the application note: http://www.quectel.com/UploadImage/Downlad/Quectel_L76-L_I2C_Application_Note_V1.0.pdf <- requires login. and here is the code to perform checksum testing yourself: requires the sentence to be a bytes object. def _checksum(self, sentence): l = sentence[0] for c in sentence[1:]: l = l ^ c return l def _test_checksum(self, sentence): if self._checksum(sentence[1:-3]) == int(sentence[-2:], 16): return True return False

@jmarcelino thanks. I'll wait and try.

@jmarcelino said in Send Lora message to non pycom device: You just need to come with with a common set of values for both modules and in the LoPy case set those when initializing the LoRa class Hi again, sorry for the delay in the update. So below is what I've set my LOPY to: lora = LoRa(mode=LoRa.LORA, region=LoRa.EU868, sf=12, frequency=869850000, bandwidth=LoRa.BW_125KHZ, public=True) s = socket.socket(socket.AF_LORA, socket.SOCK_RAW) Seems fairly standard, but what does the "public" parameter do? On the ERA-LORA side via the companion GUI software I have the following st: Bandplan (frequency): 869.85MHz Bandwidth: 125KHz Channel: 0 Spreading Factor: 12 This seems to be a match on both sides though I still cannot get them to communicate :( Does the LOPY use any encryption by default? Any other defaults I need to be aware of? Thanks, Paul

@robert-hh said in Measure Pulse width of PWM waveform: UART2 or UART3 hey, robert Thank you for reply, We will try UART for the same.

@bmarkus I found out that Thailand is using 920-950Mhz bands while The Thing Network Propose Cambodia to use AS923-925Mhz (AS2) so 915Mhz bands could be used.

@RobTuDelft The comment in the example is wrong. Maximum is 19455. For an input value between 19456 and 19531 you'll get 19531 Hz. Generally, the precision is low at the higher frequencies. So specifying a value of 19000 give 19011 Hz, 19200 -> 19230. So it looks as if the "real" periods are multiples of a small value like 200 ns.

@jmarcelino Ok, I'll try with ABP as well and let you know. If this is the reason, then if i remove and re-set the channels after the join operation, wouldn't be "fixed"? UPDATE: With ABP all seem fine. I also tried again with OTAA. I noticed that in the github code the non-default channels were actually removed after join, whereas in my code this did not happen. So, when I added this code after join OTAA did work fine as well. Another remark: how do we know if we work with 3 or 8 channels? Many thanks @jmarcelino for your help!

Even after repeated attempts, unable to get my node working. I tried Sodaq One and lopy nano gateway which worked fine. So, I'm guessing there is a problem with my other LoPy which I'm trying to use as a node. Thanks everyone for your help.