FiPy

• F

  lte cat m-1 stuck at WAIT_RSSI
  • furkan  

  10
  0
  Votes
  10
  Posts
  114
  Views

  R

  So, Was there a solution? I have the same problem, with bouncing from Syncing to Scanning and the CSQ 99,99 . Thanks.
• E

  Deepsleep bug fipy
  • Erick Falcon  

  15
  0
  Votes
  15
  Posts
  170
  Views

  

  @peterp I just updated another FiPy 1.2 to Pycom MicroPython 1.20.2.r3 [v1.11-044dfea] on 2020-12-23; FiPy with ESP32 I also ticked the boxes format and clear config + NVRAM. So the device is now clear. Some more background: >>> import pycom >>> print(pycom.heartbeat_on_boot()) False >>> print(pycom.lte_modem_en_on_boot()) False >>> print(pycom.pybytes_on_boot()) False >>> print(pycom.smart_config_on_boot()) False >>> print(pycom.wdt_on_boot()) False >>> print(pycom.wifi_on_boot()) False >>> When booting, I measure a current of about 60mA. See my setup: When going to deepsleep, this drops down to 30mA. I think this is way too high. With a LoPy4 or WiPy this drops to about 0.00A which means I cannot measure it with this setup (= okay). With a GPy with the setup above after fw-update + clear deepsleep() gives me about 0.00-0.01A
• A

  FiPy with PyTrack2.0
  • Andrew Long  

  2
  0
  Votes
  2
  Posts
  21
  Views

  A

  I've solved my own problem. Thought I might as well record the solution. You have to do an upload, not just a run!
• C

  Pyscan NFC Reading Data Authentication Problem
  • cgjem24  

  3
  0
  Votes
  3
  Posts
  49
  Views

  M

  Please can you share your code?
• S

  Issues uMQTT for connection to azure IoTHub
  • StijnK  

  1
  0
  Votes
  1
  Posts
  23
  Views

  No one has replied

• K

  Cannot Connect to FiPy with Atom or VS Code
  • Karl Thomsen  

  6
  0
  Votes
  6
  Posts
  71
  Views

  G

  Hi, Sorry for my late reply, I was refering to RX0, or P0. We use RX0 and TX0 to communicate the firmware and micropython code to the PIC, which we use as a USB-Serial converter (and some more things) Now P0 should be connected through to the PIC pin RB7, (if you orient the board so you can read the writing, it is the second pin from the left on the device marked PICxxx) directly so I'm not expecting any issues there (unless there is a bad solder connection, can you perhaps check that?) Though there is also micropython running on the Fipy, so we were once able to get firmware on the device, meaning it should just work.. Can you contact me at support@pycom.io so we can discuss further options? Gijs
• B

  read_battery_voltage() Voltage value to Battery Level
  • barryjump  

  6
  1
  Votes
  6
  Posts
  99
  Views

  B

  @claus and @kjm excellent tips guys thank you. I'm going to do both, first with the quick and dirty: battery_voltage = read_battery_voltage() roughbatt = (battery_voltage - 3.25)*100 print(roughbatt) >> 92.00001 Whilst also recording raw timestamped voltage from full to empty (last transmission) a few times and basically just dividing that scale and tweaking above.
• T

  LTE Modem interference
  fipy lte modem • • tomlausberg  

  2
  0
  Votes
  2
  Posts
  60
  Views

  G

  Hi, From what I understand, the Fipy's LTE modem no longer responds to you in the Pysense V2 (That is what cannot determine modem state! means). You mention using different fipys and pysenses etc. Do you have multiple Fipys experiencing this issue? Only on Pysense 2.0 X, or also on Pysense 1? Are you using additional accessories on the Pysense through the expansionpins? Can you try the following for me on the Fipy that does not work. Completely wipe the Fipy flash (in the pycom firmware update tool, advanced section clear NVS, CONFIG and erase flash check marks) and update to the latest firmware 1.20.2.r1. Let me know Gijs
• T

  BLE Operation already in progress
  • Tgasser  

  2
  0
  Votes
  2
  Posts
  76
  Views

  K

  @Tgasser did you ever figure this one out?
• 

  Has anyone got the FiPy working with Twilio (T-Mobile) sim?
  • meshnerd  

  11
  0
  Votes
  11
  Posts
  127
  Views

  B

  For what it's worth, I've tried MANY times to connect my FiPy to Twilio (both their NBIoT specific sims and their standard iot sims). No luck. Spent hours back and forth with Twilio support and they ultimately gave up trying because they said the modem should work, but is not officially certified by TMobile. https://www.t-mobile.com/business/iot/device-certification
• A

  What SIM to use?
  • Andrew Long  

  1
  0
  Votes
  1
  Posts
  26
  Views

  No one has replied

• M

  FiPy - Can I force force LTE-M ?
  • miketuk  

  2
  0
  Votes
  2
  Posts
  40
  Views

  M

  Having read a bit more I believe I am already using LTE-M. The CEREG command shows the value of 7, being the value of the access technology in use which I understand to be LTE-M (E-UTRAN). +CEREG: 2,5,"0xxx","07FBxxxx",7
• F

  Accelerometer wake up
  • Flavio Frattini  

  2
  0
  Votes
  2
  Posts
  35
  Views

  G

  Hi, For the Pysense 2 and Pytrack 2 it appears there is a bug that will be fixed soon! For the Pysense 1 it should work just fine Gijs
• B

  Debugging code in FiPy | Except print statements
  • bitvijays  

  4
  0
  Votes
  4
  Posts
  55
  Views

  S

  The easiest way I've found was using Putty and a TTL-Adapter like that: Just connect the TTL-Adapter with Jumper Wires to the Pins P0 and P1 of your board and select the right Com Port with Putty and set the right baudrate in Putty. Don't forget to connect the Adapter to the ground of the Pycom Board and select 3.3V on the adapter with the bridge!
• B

  Reliable transfer using UART
  • bitvijays  

  4
  0
  Votes
  4
  Posts
  43
  Views

  

  @bitvijays You can use any port for RTS and CTS which is not otherwise used. On FiPy, P5 to P7, P15, P17-P20 are used by the various modems. P4, P8 and P23 are used for the SD card, P12 for the WiFi Antenna switch. CTS is an input and so P13, P14 or P16 can be used for it.
• B

  FiPy | ubinascii | base64 decode
  • bitvijays  

  2
  0
  Votes
  2
  Posts
  46
  Views

  J

  @bitvijays can you also print the base64 text before it is decoded? It seems to be the base64 text must have been missing a character, which then resulted in the the garbled output. If you look at the output, you’ll see it repeats every 15 characters, like the original text. I haven’t checked if that actually matches the binary day shifted by a few bits, but it’s most likely. UARTs can miss characters, especially at higher speeds. You need to add some way to ensure data is correct (a checksum or CRC), and either ignore bad data if that’s appropriate for your workflow, or add a way to retransmit bad data.
• S

  FiPy crashing using WiFi
  • ssummers  

  9
  0
  Votes
  9
  Posts
  94
  Views

  S

  @Xykon @Gijs, I have put those commands into my code and my system still crashes. Here is the last crash report it did. =============================================================== ==================== ESP32 CORE DUMP START ==================== ================== CURRENT THREAD REGISTERS =================== pc 0x40163f84 0x40163f84 <KISS_Find_channel_direct+768> lbeg 0x400933c0 1074344896 lend 0x400933ee 1074344942 lcount 0xffffffff 4294967295 sar 0x10 16 ps 0x60d20 396576 threadptr <unavailable> br <unavailable> scompare1 <unavailable> acclo <unavailable> acchi <unavailable> m0 <unavailable> m1 <unavailable> m2 <unavailable> m3 <unavailable> expstate <unavailable> f64r_lo <unavailable> f64r_hi <unavailable> f64s <unavailable> fcr <unavailable> fsr <unavailable> a0 0x4018a15c 1075355996 a1 0x3ffbaee0 1073458912 a2 0xb 11 a3 0x3f9400c0 1066664128 a4 0x0 0 a5 0x3fbc23c0 1069294528 a6 0xfffffff4 -12 a7 0x14 20 a8 0x8018402e -2145894354 a9 0x3ffbaec0 1073458880 a10 0x3f9400c0 1066664128 a11 0x0 0 a12 0x0 0 a13 0x0 0 a14 0x3ffeef64 1073672036 a15 0x4 4 ==================== CURRENT THREAD STACK ===================== #0 0x40163f84 in KISS_Find_channel_direct () #1 0x4018a15c in sys_check_timeouts () at /Users/ehlers/pycom/pycom-esp-idf/components/lwip/lwip/src/core/timeouts.c:354 #2 sys_timeouts_mbox_fetch (mbox=0x3ffd1980 <mbox>, msg=0x3ffbaf30) at /Users/ehlers/pycom/pycom-esp-idf/components/lwip/lwip/src/core/timeouts.c:433 #3 0x40182aab in tcpip_thread (arg=<optimized out>) at /Users/ehlers/pycom/pycom-esp-idf/components/lwip/lwip/src/api/tcpip.c:109 ======================== THREADS INFO ========================= Id Target Id Frame * 1 <main task> 0x40163f84 in KISS_Find_channel_direct () 2 process 1 err_to_errno (err=0 '\\000') at /Users/ehlers/pycom/pycom-esp-idf/components/lwip/lwip/src/api/err.c:71 3 process 2 0x402209a6 in esp_pm_impl_waiti () at /Users/ehlers/pycom/pycom-esp-idf/components/esp32/pm_esp32.c:492 4 process 3 0x402209a6 in esp_pm_impl_waiti () at /Users/ehlers/pycom/pycom-esp-idf/components/esp32/pm_esp32.c:492 5 process 4 0x40096b4a in vTaskDelay (xTicksToDelay=<optimized out>) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/tasks.c:1484 6 process 5 0x40096b4a in vTaskDelay (xTicksToDelay=<optimized out>) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/tasks.c:1484 7 process 6 0x40096b4a in vTaskDelay (xTicksToDelay=<optimized out>) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/tasks.c:1484 8 process 7 0x40096b4a in vTaskDelay (xTicksToDelay=<optimized out>) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/tasks.c:1484 9 process 8 0x40095d50 in xQueueGenericReceive (xQueue=0x3ffdfd98, pvBuffer=0x3ffe62e0, xTicksToWait=6000, xJustPeeking=0) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/queue.c:1592 10 process 9 0x40096b4a in vTaskDelay (xTicksToDelay=<optimized out>) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/tasks.c:1484 11 process 10 0x40097d31 in prvProcessTimerOrBlockTask (xListWasEmpty=1, xNextExpireTime=<optimized out>) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/timers.c:589 12 process 11 0x4008162c in esp_crosscore_int_send_yield (core_id=1) at /Users/ehlers/pycom/pycom-esp-idf/components/esp32/crosscore_int.c:112 13 process 12 0x40095d50 in xQueueGenericReceive (xQueue=0x3ffdce88, pvBuffer=0x3ffe23a0, xTicksToWait=4294967295, xJustPeeking=0) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/queue.c:1592 14 process 13 0x40095d50 in xQueueGenericReceive (xQueue=0x3ffe3e78, pvBuffer=0x3ffd52a4, xTicksToWait=4294967295, xJustPeeking=0) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/queue.c:1592 15 process 14 0x40095d50 in xQueueGenericReceive (xQueue=0x3ffb7bd8, pvBuffer=0x0, xTicksToWait=4294967295, xJustPeeking=0) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/queue.c:1592 16 process 15 0x40095d50 in xQueueGenericReceive (xQueue=0x3ffbd460, pvBuffer=0x3ffdac50, xTicksToWait=4294967295, xJustPeeking=0) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/queue.c:1592 17 process 16 0x4000bff0 in ?? () 18 process 17 0x40095d50 in xQueueGenericReceive (xQueue=0x3ffb760c, pvBuffer=0x0, xTicksToWait=4294967295, xJustPeeking=0) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/queue.c:1592 19 process 18 0x40095d50 in xQueueGenericReceive (xQueue=0x3ffc4040 <s_timer_semaphore_memory>, pvBuffer=0x0, xTicksToWait=4294967295, xJustPeeking=0) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/queue.c:1592 20 process 19 0x40095d50 in xQueueGenericReceive (xQueue=0x3ffc95c8 <mp_state_ctx+436>, pvBuffer=0x0, xTicksToWait=4294967295, xJustPeeking=0) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/queue.c:1592 21 process 20 0x40095d50 in xQueueGenericReceive (xQueue=0x3ffc95c8 <mp_state_ctx+436>, pvBuffer=0x0, xTicksToWait=4294967295, xJustPeeking=0) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/queue.c:1592 22 process 21 0x40095d50 in xQueueGenericReceive (xQueue=0x3ffc95c8 <mp_state_ctx+436>, pvBuffer=0x0, xTicksToWait=4294967295, xJustPeeking=0) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/queue.c:1592 23 process 22 0x4008162c in esp_crosscore_int_send_yield (core_id=1) at /Users/ehlers/pycom/pycom-esp-idf/components/esp32/crosscore_int.c:112 24 process 23 0x40095d50 in xQueueGenericReceive (xQueue=0x3ffc95c8 <mp_state_ctx+436>, pvBuffer=0x0, xTicksToWait=4294967295, xJustPeeking=0) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/queue.c:1592 25 process 24 0x40095d50 in xQueueGenericReceive (xQueue=0x3ffc95c8 <mp_state_ctx+436>, pvBuffer=0x0, xTicksToWait=4294967295, xJustPeeking=0) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/queue.c:1592 26 process 25 0x40095d50 in xQueueGenericReceive (xQueue=0x3ffc95c8 <mp_state_ctx+436>, pvBuffer=0x0, xTicksToWait=4294967295, xJustPeeking=0) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/queue.c:1592 27 process 26 0x40095d50 in xQueueGenericReceive (xQueue=0x3ffd54b8, pvBuffer=0x3ffd68b0, xTicksToWait=4294967295, xJustPeeking=0) at /Users/ehlers/pycom/pycom-esp-idf/components/freertos/queue.c:1592 28 process 27 0x4000bff0 in ?? () ======================= ALL MEMORY REGIONS ======================== Name Address Size Attrs .rtc.text 0x400c0000 0x64 R XA .rtc.data 0x50000000 0x81c RW A .rtc_noinit 0x5000081c 0x0 RW .rtc.force_slow 0x5000081c 0x0 RW .iram0.vectors 0x40080000 0x400 R XA .iram0.text 0x40080400 0x1886c R XA .dram0.data 0x3ffbdb60 0x4960 RW A .noinit 0x3ffc24c0 0x0 RW .flash.rodata 0x3f400020 0x5e864 RW A .flash.text 0x400d0018 0x153c00 R XA .coredump.tasks.data 0x3ffb9fb4 0x16c RW .coredump.tasks.data 0x3ffbae20 0x1a4 RW .coredump.tasks.data 0x3fff2638 0x16c RW .coredump.tasks.data 0x3fff4a20 0x584 RW .coredump.tasks.data 0x3ffbbeb4 0x16c RW .coredump.tasks.data 0x3ffbbd10 0x19c RW .coredump.tasks.data 0x3ffbb940 0x16c RW .coredump.tasks.data 0x3ffbb7a0 0x198 RW .coredump.tasks.data 0x3ffdfb04 0x16c RW .coredump.tasks.data 0x3ffd49b0 0x170 RW .coredump.tasks.data 0x3ffb4d38 0x16c RW .coredump.tasks.data 0x3ffb4b40 0x1f0 RW .coredump.tasks.data 0x3ffdcd18 0x16c RW .coredump.tasks.data 0x3ffdcbb0 0x160 RW .coredump.tasks.data 0x3ffc45ec 0x16c RW .coredump.tasks.data 0x3ffd9870 0x894 RW .coredump.tasks.data 0x3ffe556c 0x16c RW .coredump.tasks.data 0x3ffe61e0 0x8f8 RW .coredump.tasks.data 0x3ffb5e74 0x16c RW .coredump.tasks.data 0x3ffd3d10 0x20c RW .coredump.tasks.data 0x3ffbcb20 0x16c RW .coredump.tasks.data 0x3ffbc9c0 0x158 RW .coredump.tasks.data 0x3ffb5aac 0x16c RW .coredump.tasks.data 0x3ffb58f0 0x1b4 RW .coredump.tasks.data 0x3ffde570 0x16c RW .coredump.tasks.data 0x3ffe2240 0x218 RW .coredump.tasks.data 0x3ffd533c 0x16c RW .coredump.tasks.data 0x3ffd5170 0x1c4 RW .coredump.tasks.data 0x3ffb7c30 0x16c RW .coredump.tasks.data 0x3ffb9cb0 0x188 RW .coredump.tasks.data 0x3ffbb0a4 0x16c RW .coredump.tasks.data 0x3ffdab50 0x1b8 RW .coredump.tasks.data 0x3ffddfe4 0x16c RW .coredump.tasks.data 0x3ffdde40 0x19c RW .coredump.tasks.data 0x3ffb7a68 0x16c RW .coredump.tasks.data 0x3ffb78e0 0x180 RW .coredump.tasks.data 0x3ffb727c 0x16c RW .coredump.tasks.data 0x3ffb70e0 0x194 RW .coredump.tasks.data 0x3ffe95c8 0x16c RW .coredump.tasks.data 0x3ffea6e0 0x454 RW .coredump.tasks.data 0x3ffec0b0 0x16c RW .coredump.tasks.data 0x3ffed1c0 0x45c RW .coredump.tasks.data 0x3ffe8054 0x16c RW .coredump.tasks.data 0x3ffe9170 0x450 RW .coredump.tasks.data 0x3ffeab3c 0x16c RW .coredump.tasks.data 0x3ffebc30 0x478 RW .coredump.tasks.data 0x3ffe6ae0 0x16c RW .coredump.tasks.data 0x3ffe7bf0 0x45c RW .coredump.tasks.data 0x3fff4fac 0x16c RW .coredump.tasks.data 0x3fff6d50 0x3c8 RW .coredump.tasks.data 0x3ffed624 0x16c RW .coredump.tasks.data 0x3ffee740 0x450 RW .coredump.tasks.data 0x3ffd6954 0x16c RW .coredump.tasks.data 0x3ffd6780 0x1cc RW .coredump.tasks.data 0x3ffbb2c4 0x16c RW .coredump.tasks.data 0x3ffdbb70 0x180 RW ===================== ESP32 CORE DUMP END ===================== =============================================================== Done! After this crash, it recovered and ran for about an hour before it crashed again but this time it just got hung up trying to write out the core dump. This is the last thing i got from it. Guru Meditation Error: Core 1 panic'ed (InstrFetchProhibited). Exception was unhandled. Core 1 register dump: PC : 0xffffffff PS : 0x00060c30 A0 : 0x400f801c A1 : 0x3fff6e00 A2 : 0x3fff6e60 A3 : 0x3f970420 A4 : 0x00000003 A5 : 0x00000001 A6 : 0x00000000 A7 : 0x3ffb4cb0 A8 : 0xffffffff A9 : 0x3f40e200 A10 : 0x3fff6e60 A11 : 0x3f45babb A12 : 0x00000001 A13 : 0x00000000 A14 : 0x00000000 A15 : 0x00000000 SAR : 0x0000001e EXCCAUSE: 0x00000014 EXCVADDR: 0xfffffffc LBEG : 0x40093b64 LEND : 0x40093b6f LCOUNT : 0x00000000 ELF file SHA256: ```
• B

  Attach Rejected
  • BartRemans  

  1
  0
  Votes
  1
  Posts
  30
  Views

  No one has replied

• S

  This topic is deleted!
  • sreisenb14  

  1
  0
  Votes
  1
  Posts
  7
  Views

  No one has replied

• C

  FiPy Hangs after Deepsleep - LED stays on
  • Cees_Meijer  

  7
  0
  Votes
  7
  Posts
  71
  Views

  C

  @Gijs : This is the essence of my program: import time from machine import Pin # Read a value from the NVS def get_value(key='',default=0, min =0, max =0): try: val = pycom.nvs_get(key) except: #print("Error while reading from internal storage ["+key+"]") val = default if min != max: if val < min: val=min if val > max: val = max return val def TxDriverPower(on_off=True): if on_off == ON: print("Tx ON") rx_driver_disable.value(1) else: print("Tx OFF") rx_driver_disable.value(0) try: time.sleep(0.5) print("Wake up ["+ str(machine.wake_reason()[0]) + "] - Reset [" +str(machine.reset_cause()) +"]") location_ID= get_value('ID',0) NBIOT = get_value('NBIOT',1, 0, 1) tx_driver_enable = Pin('P22', mode=Pin.OUT) rx_driver_disable = Pin('P21', mode=Pin.OUT) TxDriverPower(ON) ## Switch ON the MAX3227 RS232 Driver chip #IF IT CRASHES, IT NEVER GETS BEYOND THIS POINT # # READ A SENSOR, SEND DATA THROUGH LTE ETC. # print("TEST: Go to DEEPSLEEP ! 300 seconds") machine.deepsleep(( 300 )*1000) # End of Main loop except Exception: # Any uncaught exception will trigger a reset print("Error in program:"+ str(sys.exc_info()[0]) + str(sys.exc_info()[1]) ) time.sleep(1) machine.reset() Of course there is much more going on, but if it crashes it is always shortly after the waking from deepsleep. When the FiPy is connected to the MAX3227 (which is enabled in the TxDriverPower(ON) function) it crashes about once every 10-50 measurement cycles. With the FiPy just mounted in the development board (nothing connected) it crashed after about two days. After disabling the heartbeat, I had 4 systems running for 3 days now without a problem.