FiPy

• E

  <from network import LTE> on FiPy
  lte • • electronic  

  2
  0
  Votes
  2
  Posts
  590
  Views

  

  @electronic I cannot see the revision in your screen snapshot. But as first action you should update the FiPy. The modules network and LTE as part of that are embedded in the firmware. There are no files like network.py or LTE.py.
• T

  FIPY: Unhandled exception in thread started by <bound_method>
  fipy bugs mqtt • • tushar44  

  2
  0
  Votes
  2
  Posts
  687
  Views

  T

  Could you guy provide resolution to above error please ?
• 

  Lorawan nano gw out of sync between gateway and node. We need to restart them until the connection is successful
  lopy fipy lorawan nano gw sync syncing failed • • rubencg195  

  2
  0
  Votes
  2
  Posts
  611
  Views

  

  @rubencg195 The pull/push ack messaage show the communication via Internet to the TTN server. Independent of that, the LoRa device is always listening, except when it is sending itself. But that would only happen after an uplink message has been send and it was told by the server so deliver a downlink message. It might only happen, that if there are many nodes around sending, then the gateway may have started to listen to another message. A few notes. always use the software from the git repository. Do not copy it form the documentation. Use the latest firmware version with the software from the git repository. The nanogateway is listening on a single channel only. If you do not configure the node accordingly, the node will send on different channels. The examples for abp_node and otaa_node shoudl cater for that. Besides that, I have a comibinatin of a LoPy as nano-gateway and FiPy as nodes running, and they never seem to miss a packet.
• D

  [Solved]:FiPy socket.connect command
  fipy post socket connect • • DDA  

  4
  0
  Votes
  4
  Posts
  1604
  Views

  

  Hi @dda socket.connect doesn't take a domain name, you need to resolve it first into a tuple like this - (family, type, proto, canonname, sockaddr) - which you can obtain from socket.getaddrinfo() In your case doing: s.connect(socket.getaddrinfo(addr, port)[0][-1]) should do what you want. There currently isn't a way to obtain your assigned IP address.
• C

  Restrict TLS to V1.2 only
  fipy ssl tls ussl • • chiratoss  

  1
  0
  Votes
  1
  Posts
  524
  Views

  No one has replied

• D

  [Solved]: FiPy CAT M1 connection??
  lte sim connection prob connect issues verizon • • DDA  

  3
  3
  Votes
  3
  Posts
  1266
  Views

  D

  @jmarcelino Thank you for all your help. We had provided Verizon the ICCID and IMEI 10 days ago at the time of provisioning request, but for some reason the IMEI was mixed up....and lost in translation. It was rectified over a troubleshooting ticket with Verizon.
• T

  Problems updating FiPy
  fipy firmware upgrade • • thetechlink  

  4
  0
  Votes
  4
  Posts
  1028
  Views

  T

  That worked perfectly. Thanks, Zac
• B

  This topic is deleted!
  • bjsi9  

  1
  0
  Votes
  1
  Posts
  1
  Views

  No one has replied

• D

  FiPy getting hot
  fipy accelerometer hot • • Dylan  

  5
  0
  Votes
  5
  Posts
  1025
  Views

  D

  @jmarcelino Yeah, all up to date to the latest firmware. We are working them pretty hard, I guess they are reaching somewhere into the 45+ degrees C
• T

  All radios on by default
  fipy power saving radio energy • • thomand1000  

  16
  0
  Votes
  16
  Posts
  2628
  Views

  T

  @jmarcelino I've tested this now (removed lte = LTE() and lte.deinit() ) and the peak is still there. The device goes into deep sleep, but like before the current rises quickly to about 200 mA for a couple of seconds before it goes into deep sleep. I also find it strange that it doesn't happen the first time the device goes into deep sleep, but all consecutive runs. The first time now, since I don't deinit() LTE the current is at about 200 mA and drops down to deep sleep. Then when waking up it is around 60-70 mA when measuring and then peaks to 200 right before deep sleep.
• D

  [Solved]Firmware upgrade tool for the Sequans Monarch SQN3330
  fipy fipy firmware • • DDA  

  17
  0
  Votes
  17
  Posts
  3709
  Views

  D

  @jmarcelino And on retrying the firmware upgrade again, this time I am getting a different error once and back to the same AT+SMSWBOOT failed error <<< Welcome to the SQN3330 firmware updater >>> Entering recovery mode Resetting. Starting STP (DO NOT DISCONNECT POWER!!!) Traceback (most recent call last): File "main.py", line 2, in <module> File "/flash/lib/sqnsupgrade.py", line 114, in run NameError: local variable referenced before assignment MicroPython v1.8.6-849-83e2f7f on 2018-03-19; FiPy with ESP32 Type "help()" for more information. >>> <<< Welcome to the SQN3330 firmware updater >>> Entering recovery mode Traceback (most recent call last): File "main.py", line 2, in <module> File "/flash/lib/sqnsupgrade.py", line 98, in run OSError: AT+SMSWBOOT=3,0 failed! MicroPython v1.8.6-849-83e2f7f on 2018-03-19; FiPy with ESP32 Type "help()" for more information. >>> I have not done any changes to my code or file since the last error: OSError: AT+SMSWBOOT=3,0 failed!
• D

  lora.join never completes on OTAA example
  fipy lorawan otaa • • don  

  5
  0
  Votes
  5
  Posts
  1603
  Views

  D

  @robert-hh I got my FiPy nodes working with both The Things Network and Comcast MachineQ. To get it to work, I removed the code that modifies the channels before the connection https://github.com/pycom/pycom-libraries/blob/master/examples/lorawan-nano-gateway/otaa_node_US915.py#L23-L29
• T

  FiPy deep sleep high current
  fipy current deepsleep fipy • • thomand1000  

  2
  0
  Votes
  2
  Posts
  806
  Views

  No one has replied

• S

  FiPy sigfox antenna issue
  fipy sigfox antenna • • sanatox  

  10
  0
  Votes
  10
  Posts
  1963
  Views

  S

  @jmarcelino even in outdoors (completely flat field) the reads are erractic. Could you confirm me that the class of the tranceiver in FiPy is 0U??
• C

  DeepSleep Library for FiPy
  fipy gpy deep sleep • • cssmacs01  

  2
  0
  Votes
  2
  Posts
  775
  Views

  J

  @cssmacs01 just use the native machine.deepsleep and related functions: https://docs.pycom.io/chapter/firmwareapi/pycom/machine/#machinedeepsleeptimems The deep sleep shield and other workarounds are only needed for some of the modules, the FiPy is not one of them.
• K

  LTE-M on 800MHz?
  lte-m fipy firmware • • kersing  

  3
  0
  Votes
  3
  Posts
  882
  Views

  M

  Hi @jmarcelino , I'm interested since you're specifically asking about supporting KPN. I'm trying to get LTE-M to work on a KPN network, but am unable to do so. Just after the attach() call I can execute AT+COPS=?, and after a long time (30s?) it'll show KPN. However, directly after it'll give a +CEREG: 4 (= unknown (e.g. out of E-UTRAN coverage)). After that it's unable to find any networks when using AT+COPS=?. If you managed to get KPN to work, I'd love to hear what AT commands you used.
• M

  Using photoresistor with 10kohm resistance
  sensors electronics lightsensor photoresistor • • Matthew  

  2
  0
  Votes
  2
  Posts
  624
  Views

  

  @matthew look at attenuation https://docs.pycom.io/chapter/firmwareapi/pycom/machine/ADC.html#adcchannel--pin-attnadcattn0db try ADC.ATTN_11DB
• N

  Sending data to server using MQTT
  fipy mqtt server mosquitto • • Nazz  

  10
  0
  Votes
  10
  Posts
  2108
  Views

  N

  @timh Ok, i have connected the fipy to our wifi network & it is connected successfully, and also checked the ip address address and ping fipy is working.
• I

  Fipy LoRa range
  fipy lora range • • imasd  

  7
  0
  Votes
  7
  Posts
  1256
  Views

  

  @imasd I was noisy an so I drove over to the HLK place. And indeed, at that spot there is a good sensitive antenna on the top of a 5 story building. The antenna looked like the TaoGlas Barracuda, pretty long. And other short wave antennas. So the person seems to know what she/he is doing.
• G

  Sigfox RC4 Freezing after 1 msg
  fipy sigfox send data freeze • • gsimenel  

  5
  0
  Votes
  5
  Posts
  1083
  Views

  G

  @jmarcelino said in Sigfox RC4 Freezing after 1 msg: time.sleep(20) Works like a charm. Thanks a lot. The documentation is a bit misguiding here, it says : "there must a minimum of a 20s delay after resetting to the default macro-channel. Our API takes care of this [...] for i in range(1, 100): # send something s.send('Hello ' + str(i)) There will be a 20 second delay after every 2 packets" In fact, there should be a delay added between 2 packets. Maybe a suggestion for modification of the doc. Anyway, thanks a lot for correcting me ! All the best.