• Expansion board v3.1, µSD pinout

    3
    0 Votes
    3 Posts
    157 Views
    F
    I manage to write on µSD using SD-MMC folowing libs: #include "esp_vfs_fat.h" #include "driver/sdmmc_host.h" #include "driver/sdmmc_defs.h" #include "sdmmc_cmd.h" using only internal pull-up gpio_set_pull_mode(GPIO_NUM_2, GPIO_PULLUP_ONLY); gpio_set_pull_mode(GPIO_NUM_14, GPIO_PULLUP_ONLY); gpio_set_pull_mode(GPIO_NUM_15, GPIO_PULLUP_ONLY); gpio_set_pull_mode(GPIO_NUM_4, GPIO_PULLUP_ONLY); gpio_set_pull_mode(GPIO_NUM_12, GPIO_PULLUP_ONLY); gpio_set_pull_mode(GPIO_NUM_13, GPIO_PULLUP_ONLY);
  • Using Pytrack and and Pysense with a single LoPy board

    3
    0 Votes
    3 Posts
    136 Views
    K
    @jcaron Thanks for the info. I looked around quite a bit before posting this question because I figured it must have been addressed already, but I could not find anything, so thank you for your reply. I was wondering about connecting external sensors or combining a Pysense with external GPS so thanks for pointing out those possibilities. I'll look into those options.
  • understanding accelerometer wake example

    accelerometer
    11
    1
    0 Votes
    11 Posts
    264 Views
    J
    @NicolaC The PORTC configuration will be changed during the go_to_sleep call. You should just add an argument false to that call to disable the GPS (the argument is optional and defaults to true).
  • Pytrack deepsleep wakeup on pin problems

    2
    0 Votes
    2 Posts
    204 Views
    J
    @Peter-Ehses The whole Pytrack/Pysense wake-on-pin is a bit of a mess in my experience, but you can make it work. The trick is to cut (or somehow isolate) P9 on the *Py module. Otherwise you'll get all sorts of weird behaviour because P9 is (indirectly) pulled low during Pytrack/Pysense-controlled deep sleep. The right order for the calls on a Pysense is (or was, the last time I played with that): py.setup_sleep(SLEEP) py.setup_int_pin_wake_up(not p) py.go_to_sleep() (here p is the current state of the pin, so it dictates whether we want to wake up on falling or rising edge) Don't quite remember where the setup_int_wake_up call fits (didn't use it in my case), but most likely after the setup_sleep. See previous discussions on this topic: https://forum.pycom.io/topic/2829/pysense-external-wakeup-pin-p9-is-pulled-low-when-in-deepsleep https://forum.pycom.io/topic/1673/pysense-pinout-wake-on-pin
  • Pytrack i2c causes system to freeze

    6
    0 Votes
    6 Posts
    267 Views
    P
    @crumble Thanks, it seems to be more stable with the new firmware. Pybytes is a whole new rabbit hole of problems though. I might try @andreas firmware later. It would be really nice to have more documentation from pycom regarding the versions and differences, as well as all functions of their various libraries while we're at it.
  • pytrack get charging cable connected

    2
    0 Votes
    2 Posts
    145 Views
    J
    @Peter-Ehses The charging voltage is always higher than the voltage of a discharging battery. Just measure it in both cases to determine an appropriate threshold (probably around 4.2V IIRC).
  • 0 Votes
    2 Posts
    335 Views
    robert-hhR
    @RichardBH The Pycom development modules are supplied by the Vin Pin. The 3.3V Pin of the modules is the output of the internal regulator. AFAIK, this is an LM3281 device with an absolute maximum input voltage of 6V. Between the Battery plug and the Vin pin is the charge chip and some switching circuitry. They should not cause a major voltage drop. So: If you are absolutely sure that the battery voltage is never above 6V, you could connect it. But typically, the voltage of a fully charged/fresh battery is above its nominal voltage. Like: 6V Lead battery, full charged 7.2V, 1.5 V Alkaline: fresh ~1.6V, ... So you will need some means to limit or lower the input voltage.
  • Mapping of G pins and P pin on Exp. Board v3

    wipy3.0 expansion board pinout
    13
    0 Votes
    13 Posts
    1k Views
    robert-hhR
    @mci For coding the content of the pins.csv file is effective, because that file is used for mapping the Pxx and Gxx numbers to the GPIO port numbers,
  • Problems Getting FiPy and Expansion 3.1 working

    10
    0 Votes
    10 Posts
    626 Views
    A
    @robert-hh said in Problems Getting FiPy and Expansion 3.1 working: @andreas keeps a web page with 1.20.1r1 firmware images w/o pybytes. We are even doing builds with Pybytes these days, see https://packages.hiveeyes.org/hiveeyes/foss/pycom/pybytes/. @robert-hh said in Problems Getting FiPy and Expansion 3.1 working: This new pybytes version does not match the documentation any more, in that is does not create the AP by default, and it cannot be interrupted with Ctrl-C. They should run more stable by mitigating different issues and CTRL-C should also work again.
  • VIN and GND to charge battery?

    expansion board wipy 2.0 battery charge power
    5
    0 Votes
    5 Posts
    2k Views
    T
    I had simmilar issue using VIN. I can't believe Pycom doesn't provide any schematic for these expansion boards, or atleast proper descriptions on how they can be used. I was also under the impression that VIN can be used as an input, instead of using the USB. There are NO WARNINGS anywhere that you should not be using VIN as an input, while using a battery as a backup. Luckily my house didn't burn down as I soon enough figured out that VIN and the Battery + seem to be linked together... I'm new to Pycom's hardware - and thus far really disappointed in the lack of usefull (and up to date) documentation
  • Disabling external sensor while in deep sleep on Expansion Board 3.1

    6
    0 Votes
    6 Posts
    238 Views
    robert-hhR
    @ZachH Most GPIO Pins can drive up to 40 mA, but then the output level drops to ~2.6V. Using an transistor is the better choice.
  • Pyscan V0.7 - Pinout question

    2
    1
    1 Votes
    2 Posts
    206 Views
    John BairdJ
    For the record, I'm happily feeding +5v into the pin labelled VIN -5V and everything works fine. Very disappointing that even when pointed out, such a fundamental error remains uncorrected for six months.
  • I2C lines through Pytrack headers drawing current.

    8
    0 Votes
    8 Posts
    576 Views
    J
    @joelmarini I hadn't seen this discussion back then... What type of deep sleep are you using? The "native" machine.deepsleep or the Pytrack-controlled deep_sleep (go_to_sleep)? Did you find a solution for your problem?
  • Pytrack not working.

    6
    0 Votes
    6 Posts
    394 Views
    robert-hhR
    @sandris That looks like a hardware problem on the pytrack. For power saving, it can switch off the power to the Vin pin. So this switching logic seems to fail. There is a package with imprints of J13 and 1731G close to the battery connector, which seems to switch the power. But I do not know what part number it is. B.t.w.: A stable 3.4 V supply is sufficient to run a Pycom development module, so I assume it will drop further.
  • Pytrack & Pysense Battery Voltage Measurement

    1
    0 Votes
    1 Posts
    219 Views
    No one has replied
  • Expantion3 Drivers Link Broken

    expansion board drivers broken link
    7
    0 Votes
    7 Posts
    510 Views
    R
    @catalin Thank you. :o)
  • Expansion board 3.1

    8
    0 Votes
    8 Posts
    756 Views
    K
    According to the documentation it's P14 but doesn't seem to work. It will be P10 but I'm already using that for I2C
  • Expansion Board 3.1 not going into DFU-mode

    expansion board zadig
    4
    0 Votes
    4 Posts
    387 Views
    robert-hhR
    @MJ1 If it shows up as COM port, then you can use it for your Pycom device.
  • This topic is deleted!

    3
    0 Votes
    3 Posts
    32 Views
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    37 Views
    No one has replied

Pycom on Twitter