Expansion Board

• I

  pyscan + gpy + pir sensor "No presence"
  • Israel  

  3
  0
  Votes
  3
  Posts
  197
  Views

  I

  Here is the image: https://ibb.co/YL3svzB I connected it like this. It seemed to work now but the problem is the PIR sensor works once every 10 second. Which is definitely not what I want. I want it to sense non-stop . I have removed #config hold_time_sec = 10 #flags last_trigger = -10 from the program (https://docs.pycom.io/tutorials/all/pir.html) yet it doesn't sense constantly. I am wondering is it how the sensor works or is it because of my program? How should I adjust the program so the sensor works all the time, it that is the case? Thank you
• T

  Pyscan datasheet is completely wrong
  bug pyscan specs • • theshade  

  7
  4
  Votes
  7
  Posts
  769
  Views

  T

  Thank you @paul-thornton, I just saw the addition to the web page with the mechanicals. I'll start drawing my board ;)
• S

  PyScan GPS and LoRa over TTN
  • svonbentzel  

  2
  0
  Votes
  2
  Posts
  212
  Views

  S

  I use the example file for LoraOTAA and a Nano Gateway. for i in range (200): pkt = b'PKT #' + bytes([i]) print('Sending:', pkt) s.send(pkt) time.sleep(4) rx, port = s.recvfrom(256) if rx: print('Received: {}, on port: {}'.format(rx, port)) time.sleep(6)```
• T

  Pysense new + Mac os x 10.14.3 ?
  pysense • • technoman  

  10
  0
  Votes
  10
  Posts
  780
  Views

  T

  @catalin Is it possible the pins of the external io header on the pysense are reversed in the online datasheet ? Pins 3 and 4 are reversed ? or the names are confusing ? For sure: Pin 4(ext io header) is coming from the voltage regulator.(5pins - pin5) ----- is called 3V3_Pymodule online. Pin 3(ext io header) is coming from FiPy 3V3 output and goes to the sensors (power). ----- is called 3V3_Sensors online. What is the purpose of control pin 2 PWR_EN (ext io header) ? connected by two resistors to pin GPIO24 I believe. Found some topics in the forum, but no clear answer and/or I'm looking at the wrong topics/datasheet. ( I always start with pycom.io to search for information ) I ask this questions because before buying other boards with that PIC chip, I want to understand the working and be sure not having the same problems again. I still can't imagine that all power (3V-5V) for the mounted module is coming from that PIC16lf1459 ( pin RC2 ). Thanx.
• G

  Restore RTC value after Pysense go_to_sleep
  pysense rtc rtc memory • • gabrielapb  

  2
  0
  Votes
  2
  Posts
  403
  Views

  J

  @gabrielapb You could try the following: save the current timestamp to NVS before going to sleep on wake-up: retrieve the saved timestamp from NVS retrieve the "remaining sleep" from the Pysense using pysense.get_sleep_remaining current timestamp is approximately saved + sleep interval - remaining Note this won't get you a very precise time (as it doesn't take into account boot time, and I'm not sure of the accuracy of the Pysense clock), and the offset to the real time will increase with the number of sleep periods, but it's helpful to have at least of rough idea of the time until you can get the actual time through other means. The alternative is to use the module's deep sleep rather than the Pysense's deep sleep, but that may not be possible depending on your actual use case.
• M

  pyscan can not read the nfc tag
  pyscan data nfc • • mia1913  

  2
  0
  Votes
  2
  Posts
  325
  Views

  J

  @mia1913 don’t know the details of the interface / library, but at a low level, 7 and 10-byte UUIDs are actually transmitted in several round trips. For a 7-byte UUID, only 3 bytes of the UUID are returned, and the other byte is a special value which means “there’s more”. You then do another request which returns the remaining 4 bytes. No idea how this is/should be handled on the Pyscan, though.
• N

  Pytrack V1.0 upgrade?
  pytrack firmwarupgrade • • Nicholas  

  5
  0
  Votes
  5
  Posts
  462
  Views

  N

  @paul-thornton Thanks to both, the upgrade went flawless, and it seems to be much easier doing it from within linux. It gave me a scare though, in that not only I could not make my (VC) pymakr to connect to it, but it crashed the computer a few times. That, until I deleted the directory .vscode from the working folder. Next I have to look into the Lopy4 upgrade (current code 1.18.2 r1)
• C

  Pysense bricked? Pin voltages wrong (0.2V instead of 3.3V)
  pysense battery power pins voltage • • catfeeder  

  1
  0
  Votes
  1
  Posts
  276
  Views

  No one has replied

• W

  Best power source for using 5V sensors
  expansion board i2c battery expansionboard levelshifter • • weingami  

  7
  0
  Votes
  7
  Posts
  772
  Views

  M

  @weingami Note that I2C level shifting is particularly easy as it uses an open drain-pullup signaling scheme. Shifting can simply be done with two FETs: https://electronics.stackexchange.com/questions/255607/i2c-level-shifting-mosfet
• F

  Pytrack + GPy. Where to connect sensors?
  gpy pytrack sensors pins • • fedonman  

  2
  0
  Votes
  2
  Posts
  315
  Views

  S

  @fedonman Depends on the sensors really. What bus (i2C, SPI, etc) or other port you need. Other factors are the power supply required and any other such factors. My practice is to extend the bus/es from the sockets Expansion/Pytrack board to a protoboard, so I am able to connect more than one device, power supply, level shifters, pull up/down resistors, capacitors etc if required. Makes it easier to work on and follows on with making a custom PCB later on..
• T

  Pysense module error
  wipy pysense error modules si7006a2 • • Tr234__  

  3
  0
  Votes
  3
  Posts
  327
  Views

  P

  Hey. Could you try reflashing the latest firmware. Including using the checkbox to wipe flash. And reupload and try the code again. Thanks
• T

  pytrack external IO header clarifications
  lopy4 pytrack battery externa gpio • • tttadam  

  9
  0
  Votes
  9
  Posts
  1330
  Views

  J

  @tvetter1976 If you use Pytrack/Pysense-controlled sleep, the PIC will power down completely the FiPy (it's not sleeping, it's completely off), stop USB, etc, and go to sleep. On a Pytrack you can choose to power down the GPS as well. Don't remember about the other sensors on the board. 3V3_Pymodule will be shut down. 3V3_Sensors can be kept on, though I don't remember if it's always on or if there's an option to shut it down as well. If you use machine.deepsleep, the FiPy will go to sleep, but I believe the Pytrack/Pysense will continue to work as usual, with everything powered. You probably need to take a few steps to reduce its power draw. Don't think there's anything in the libraries for that, you'll probably have to talk to the PIC and/or sensors directly, and I'm not sure there's a way to make the PIC go to sleep without shutting down the FiPy (though I don't know how much the PIC itself draws).
• G

  power supply (Lopy4+Exp.Board v.3)
  lopy4 expansion board power down • • Giorgio  

  5
  0
  Votes
  5
  Posts
  676
  Views

  G

  @paul-thornton ... and in the boot.py file I have this code: # boot.py -- run on boot-up import os from machine import UART uart = UART(0, 115200) os.dupterm(uart) #disable the wifi radio from network import WLAN wlan=WLAN() wlan.deinit() #disable the bluetotth radio from network import Bluetooth blt=Bluetooth() blt.deinit()
• P

  Minimal Hardware to program Lopy4 with USB
  expansion board usb ftdi • • ProtonX  

  3
  0
  Votes
  3
  Posts
  563
  Views

  

  @protonx I made myself a base board too for the Pycom modules. A Kicad sketch is here: https://github.com/robert-hh/Pycom-baseboard It uses pre-built modules for USB/Serial and SD card. I did not want to deal with SMD parts, and space did not matter. It also has the espressif logic for activating the bootloader, and jumpers for the connection to Reset, Tx, Rx and P2. Not that this costs less than an Pycom expansion board, but it makes fewer troubles when using (no PIC, standard drivers, ..)
• D

  Pytrack only receive empty nmea messages
  pytrack gps empty messages • • daraujo  

  7
  0
  Votes
  7
  Posts
  697
  Views

  D

  Going back to the 1.18.0.r1 and reseting the GPS did not help. The firmware updater (1.15.2.b1) installs the 1.18.1.r10 version of the firmware and I'm unable to find the 1.20.rc4 version of the firmware.
• A

  Expansion board 3 firmware update Zadig issues
  expansion board setup zadig drivers • • andyc  

  4
  0
  Votes
  4
  Posts
  1094
  Views

  P

  I've had Zadig be a bit fiddly in terms of getting the timing right. Ive not seen it take that long just to build a catalog. certainly not on decent hardware. On my laptop: i7 6700k, generic sdd. it was basically instant. are you seeing high cpu/io usage during those few seconds? (Admittedly it'll be hard to diagnose given the few seconds of time constraint..)
• M

  Expansion board 3.0 battery power not enough juice?
  expansionboard • • macbum  

  18
  1
  Votes
  18
  Posts
  3697
  Views

  R

  @wolli01 Yes, I can remove the cable when the Lopy is charge by Lipo after starting. When USB connected, I remove the cable but it's not necessary. I updated Lopy with the new firmware and no change. It's work only with the jumper cable connected when the expension board and lopy start. Maybe on other people have an idea ?
• C

  Why can't the schematics for the expansion boards be released?
  gpy pysense schematics • • curtis.hendrix  

  3
  2
  Votes
  3
  Posts
  616
  Views

  P

  An effort to bring all documentation inline is ongoing at the moment and things should be clearer going forward. We are aware of a few conflicting pieces of information that need clearing up. Ill pass along the feedback about schematics being made available to the public.
• 

  Expanion board v3.0r and SD card
  expansion board sd card • • luca.gamma  

  4
  0
  Votes
  4
  Posts
  398
  Views

  P

  @luca-gamma Perfect. Glad you got it sorted :)
• J

  Pytrack power consumption
  lopy pytrack power expansion • • james.matthews  

  4
  0
  Votes
  4
  Posts
  628
  Views

  J

  @james-matthews Depends what you mean by "idle". In Pytrack-assisted deep sleep it should be somewhere in the range of 10-20 µA. Once you wake up the ESP32 and/or radios whatever the Pytrack uses is drowned in the consumption of those. Note that in my experience, keeping the accelerometer active for wake-on-fall/tap/movement already brings power draw to several hundred µA rather than a few dozen as expected (but that was on the Pysense, and I haven't much investigated the cause for the issue since). I expect the GPS to be a lot more power-hungry, though there are probably standby modes and the like.