Expansion Board

• R

  What is the voltage of the battery that connects to the extension board?
  • RodrigoMunoz  

  2
  0
  Votes
  2
  Posts
  20
  Views

  

  @RodrigoMunoz Single cell, nominal voltage 3.7V. At least 1000mAh is recommended. Take care of the polarity of the plug.
• J

  How to wakeup pytrack2 after calling sensor_power(False)
  • jbthompson  

  2
  0
  Votes
  2
  Posts
  27
  Views

  G

  Hi callingpytrack.sensor_power(False) should only disable the sensors (Accelerometer, the Pyport and GPS), you should be able to call pytrack.sensor_power(True) to re-enable the power to those sensors. The coprocessor (which controls the power switching) should not power down
• J

  Pygate & Wifi connection issues
  • Jithin Isaac  

  2
  0
  Votes
  2
  Posts
  18
  Views

  G

  You're correct there's no failsafe implemented in the pygate example. You could for example issue a machine.reset() if connecting takes too long, or if the connection is dropped (though you'll have to write your own checking method to verify the connection is still up)
• B

  Pyscan Using GPIO pins or expansion board pins (BUT)
  lopy4 pyscan gpio nfc • • Borja Blasco  

  2
  0
  Votes
  2
  Posts
  36
  Views

  

  @Borja-Blasco Generally it is possible to use the Pins of the camera connector. They are connected to the said Pxx pins. Be aware, that P13-P18 are input-only. Using them as output fails.
• J

  Powering Pytrack + Gpy without USB - How to connect?
  gpy pytrack battery power vin • • jpgamboa  

  5
  0
  Votes
  5
  Posts
  65
  Views

  J

  Just to give feedback, I've had the Pytrack + Gpy powered via the VUSB_AUX for a few hours and all is working fine. Thank you for all the help!
• S

  Tutorial for WiPy 3.0 and Pysense in Pycom.io , IndexError: list index out of range
  • sung-pil kim 0  

  4
  0
  Votes
  4
  Posts
  33
  Views

  M

  @sung-pil-kim-0 No worries. Thanks for using Pycom products. I am here to answer any questions you have. Matthew
• N

  Geofencing with Pytrack
  • newkit  

  25
  0
  Votes
  25
  Posts
  207
  Views

  N

  @jcaron that seems to have fixed it. Initial results look positive, will do some more testing in the next days. Thank you so much for sorting this out!
• A

  Expose Pygate events with the forwarder payload
  pygate event • • Alexey Novikov  

  6
  1
  Votes
  6
  Posts
  63
  Views

  A

  @Gijs I managed to get the event payload to the higher level, thanks for the hint! I can see the whole diagram sent which is built by the packet forwarder, ie the full PUSH_DATA packet as per Semtech specs. Basically, I can do this now: elif (evt & machine.PYGATE_LORA_EVT): print('LoRa Event') print(arg, end='\n') print('\n') and get normal Python byte string with PUSH_DATA packet in arg
• G

  Using the expansion board 3.0 to read external battery voltage
  • Graham Blackwell  

  6
  0
  Votes
  6
  Posts
  66
  Views

  

  @Graham-Blackwell P13 to P18 are indeed the ADC input pins. As long as you do not set an attenuation, the range is 0.03 - 1V. For setting the attenutaion, used attn keyword argument on the adc.channel call. See: https://docs.pycom.io/firmwareapi/pycom/machine/adc/#class-adc--analog-to-digital-conversion With ADC.ATTN_11DB the range is 0.1 - 3.3V. The best linearity is achieved with ADC.ATTN_6DB, which has a range of 0.07 - 2V. Irrespective of the attenuation setting, the safe input range is 0-3.3V. However beyond the range of the ADC input the reading will be 4096. To reduce noise, add a small low impedance capacitor between the adc input and GND. 10nF is sufficient. Still the readings are noisy. You may decide to take an average over a set of readings.
• 

  Error in the PyScan Pinout document
  • robert-hh  

  21
  0
  Votes
  21
  Posts
  47
  Views

  G

  @robert-hh You are correct, Im not sure yet how they messed it up, but it seems to be a mirrorring issue. From what I see, the connector is labeled from the top view, but the square pad is definitely connected to GND, instead of PWR_EN I'll make sure it gets fixed, thanks!
• G

  pyscan paper ink
  • gael cobert  

  23
  0
  Votes
  23
  Posts
  74
  Views

  

  @gael-cobert RST is required. Did you check that you connected the flat cable between HAT and display the right way around? Checking the board it seems that the Pinout paper is wrong. The PIN where the white cabel is connected to is actually P10. left to it is P4, right to it P2. The rows in the Pinout are swapped.
• P

  PYScan shield: which RFID/NFC chip is used
  pyscan shield • • patrick  

  3
  0
  Votes
  3
  Posts
  1021
  Views

  M

  NXP MFRC63002HN
• R

  This topic is deleted!
  • rpalma  

  1
  0
  Votes
  1
  Posts
  2
  Views

  No one has replied

• L

  UART over Pyscan pins
  sipy uart pyscan • • Louis Henn  

  5
  0
  Votes
  5
  Posts
  33
  Views

  L

  @robert-hh took some debugging, but I did manage to make it work like you said. Thanks a lot!
• H

  Using py.setup_int_pin_wake_up(True)
  • hdemeillon  

  9
  0
  Votes
  9
  Posts
  75
  Views

  M

  I just realized that I could get actually get a much finer readout that I originally thought. Running the Pytrack with just the 10K resistor on the latest firmware is yeilding me 8.5uA. Give the error of my power supply on the readout listed here , that would put the power draw in line with the expected 20uA. So it seems like the draw is actually negligible here.
• A

  Pytrack Turning off the gps receiver.
  • AM  

  15
  0
  Votes
  15
  Posts
  116
  Views

  A

  @Gijs @robert-hh I got the Pytrck 2.0 . I test with the standby, sensor_power Functions. also with def gps_state(self, gps=True): # enable or disable back-up power to the GPS receiver if gps: self.set_bits_in_memory(PORTC_ADDR, 1 << 7) else: self.mask_bits_in_memory(PORTC_ADDR, ~(1 << 7)) It disable and then automatically restart the receiver. Sending data: {"lon_d": xxxxx, "lat_d": xxxxx, "battery": 4.766989, "temperature": 0, "humidity": 0} CoAP POST message ID: 27515 ID: 26235 Code: 69 Type: 2 Token: b'' ReceivedMsg: b'test' b'test' test GPS OFF CoAP GET message ID: 27771 Caugh exception: I2C bus error Sending data: {"lon_d": null, "lat_d": null, "battery": 4.756954, "temperature": 0, "humidity": 0} CoAP POST message ID: 28027 CoAP GET message ID: 28283 Sending data: {"lon_d": 10.37374, "lat_d": xxxx, "battery": xxxxx, "temperature": 0, "humidity": 0} CoAP POST message ID: 28539 Is there a way to disable it and it stays disabled until I enable it again.
• K

  Pysense v2 connector cable+socket for pyport to connect external sensors
  • keja  

  12
  0
  Votes
  12
  Posts
  119
  Views

  

  @jackalope thanks for the updated link! That is a nice find. Much cheaper as well :)
• J

  Pysense/pytrack 2X wake on pin issues
  • jackalope  

  3
  0
  Votes
  3
  Posts
  25
  Views

  J

  Ok sounds good. If the two issues are related I'll watch that github issue and use the machine sleep in the meantime till that gets sorted. Thanks, Chris
• P

  Does PyScan have temperature sensor?
  • Paul Hopkins  

  3
  0
  Votes
  3
  Posts
  26
  Views

  P

  @Gijs said in Does PyScan have temperature sensor?: , you are corr Ok. Thanks for confirming. Its a pain I wasted my money on the pyscan, I thought it was all-singing-all-dancing. I have ordered a pysense2.0X now from Farnell as RS were out of stock. Thanks, Paul
• 

  Can't get PyTrack to work due to firmware issue
  • macfreek  

  3
  0
  Votes
  3
  Posts
  61
  Views

  J

  Hello I have a similar issue, I'm trying to update the firmware of my Pytrack v1.1 but I get an error. Here is the output when I run the DFU-util tool $ dfu-util -D pytrack_0.0.8.dfu dfu-util 0.10 Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2020 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ Match vendor ID from file: 04d8 Match product ID from file: f014 Opening DFU capable USB device... ID 04d8:f014 Run-time device DFU version 0100 Claiming USB DFU Runtime Interface... dfu-util: Cannot claim interface 0: LIBUSB_ERROR_NOT_FOUND I'm working on Mac OS 10.15.7, but as this errors only occurs on Mac OS I'll try to update my Pytrack using a Windows system as recommended