• Pysense location services support [specification details]

    pysense galileo qzss
    3
    0 Votes
    3 Posts
    1k Views
    B
    @jcaron Thanks! That was something I thought, but I wanted to be sure. Peter
  • Pytrack I2C Error when polling button_pressed()

    bugs pytrack i2c bus error
    1
    0 Votes
    1 Posts
    830 Views
    No one has replied
  • Where are the schematics of the expansion boards?

    pysense pytrack schematics
    3
    2 Votes
    3 Posts
    2k Views
    R
    @jcaron The pysense and pytrack are nice samples of how to use the xxPy modules. IMHO It would benefit pycom if they publish the schematics. It will serve as inspiration for new pycom based products. Now it is a source of frustration and wasted hours of figuring out how it is all interconnected. Also the datasheets are far from complete. We have a low power device that can be put in deep sleep (uA) but on the other hand (some versions) need a power supply of over 500mA. Documentation needs some care. It looks like they are growing (to) fast as a company with (to) many products to support at this moment. I'm a bit reluctant to put the modules in a real product at this moment. Are there pycom oem module based products on the market yet?
  • 0 Votes
    3 Posts
    1k Views
    robert-hhR
    @lollisoft M3 matches the expansion board. Looking at the pitctures in the docs, PySense and PyTrack seem to have 2mm mounting holes.
  • Mac OS USB device disappears

    osx usb atom
    9
    0 Votes
    9 Posts
    4k Views
    T
    @jmarcelino $ ioreg -p IOUSB +-o Root <class IORegistryEntry, id 0x100000100, retain 15> +-o Root Hub Simulation Simulation@14000000 <class AppleUSBRootHubDevice, id 0x10000034b, registered, matched, active, busy 0 (0 ms), retain 10> +-o Bluetooth USB Host Controller@14300000 <class AppleUSBDevice, id 0x1000003f2, registered, matched, active, busy 0 (1 ms), retain 21> +-o FT230X Basic UART@14100000 <class AppleUSBDevice, id 0x1000005dd, registered, matched, active, busy 0 (15 ms), retain 14> This is the output when the wipy is connected, and right now it's working fine. I'll run the command again if the problem re-occurs. Thanks, Bernhard
  • Pytrack wake from deep sleep pin interrupt

    Moved pytrack interrupt deepsleep
    3
    0 Votes
    3 Posts
    2k Views
    joeriJ
    Is there an update on the availability of the interrupts? I would like to use to it in my next project.
  • Pysense with non-rechargeable batteries

    pysense battery charging
    1
    0 Votes
    1 Posts
    982 Views
    No one has replied
  • 0 Votes
    6 Posts
    2k Views
    T
    @bucknall : @chrisi runned into one of your documentation errors: https://docs.pycom.io/pycom_esp32/pycom_esp32/tutorial/includes/pytrack-examples.html#axis-accelerometer you might adapt the example as mentioned above.
  • 0 Votes
    1 Posts
    775 Views
    No one has replied
  • 5V Pin or VIN only ?

    expansion board voltage pin
    5
    0 Votes
    5 Posts
    3k Views
    B
    Just tried to power my sensor as you said and it is indeed working, are there any risks of doing so ?
  • SD Card Interface: SPI or SDIO?

    spi sdcard library
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • I2C PINOUT QUESTION

    wipy 2.0 i2c expansionboard
    6
    0 Votes
    6 Posts
    2k Views
    M
    @jmarcelino Thanks - that worked a treat (pull ups on P9/10 seem to be enabled by default which made life easier)
  • Hardware improvement suggestions

    Moved hardware suggestions
    5
    3 Votes
    5 Posts
    2k Views
    robert-hhR
    @mo-seph said in Hardware improvement suggestions: In addition to what other said: having the analogue reference voltage available would be really helpful, especially as it is a strange one (1.1v). Yes, for application where a reference voltage is required it would be good to have it, even if that will create new trouble. But .. I did not find an esp32 pin in the specs. more ground pins would also be good Yes, solid GND posts on either side a jumper for firmware boot mode on the expansion board would surely be useful - Yes, or better a switch. That would sort out some confusion. the boxes/bags that they come in should really take a lopy and an expansion board, as that's how they mostly get used In the box I got both a lopy and the expansion fixes. so no complaint.
  • expansion board 2.1a

    lopy expansionboard
    7
    0 Votes
    7 Posts
    3k Views
    J
    hi all, thx for all the responses, i've got the exp. board (in combination with the lopy) working. the vcp driver did the trick :) thx :) :)
  • Expansion board (WiPy/LoPy) and WiPy mismatch

    wipy expansionboard
    4
    0 Votes
    4 Posts
    2k Views
    M
    seems that is exactly what happened, the description on amazon said the expansion would fit either version, I honestly didnt know I was ordering the old version of the WiPy it didnt have a version number on the description. I rma'd the 1.3 board and ordered a 2.0 board. They should put better description on Amazon for both items to avoid this stuff. https://www.amazon.com/Pycom-C1002-WiPy/dp/B01HFAKK5C/ref=sr_1_1?ie=UTF8&qid=1489281512&sr=8-1&keywords=WiPy
  • 3D model ExpansionBoard V2

    expansionboard
    1
    4 Votes
    1 Posts
    1k Views
    No one has replied
  • 0 Votes
    5 Posts
    2k Views
    L
    Thanks to Livius. That worked!
  • Battery Charger on the Expansion Board v2

    Moved
    6
    0 Votes
    6 Posts
    3k Views
    B
    @dalecousins thanks so much for this - its a confirmation for me. Last night I tried to charge the battery through another mechnism and found the same thing - once I connected it back up again it was fine. Apparently (I found this out in another post) they havent implemented the deep sleep function in the firmware / API and therefore when I connected up my solar, the battery was draining a LOT faster than I originally expected and the solar couldnt recharge the battery fast enough, and therefore the battery drained too low. Also, FYI, deint the WIFI doesnt actually power it down and therefore will drain the battery quickly too. My solution is now on hold until these things are sorted out.

Pycom on Twitter