Pytrack and Pysense Libraries Release 1.0.0

[bucknall]

@Camot I'm investigating this today and will likely merge @papasmurph's code when I get a chance to review the changes

[Pajarraco]

Maybe its a fool question, but when I try to download the new version 1.0.0 here: https://docs.pycom.io/pycom_esp32/pycom_esp32/toolsandfeatures.html#updating-pysense-and-pytrack-firmware

The download file has the name pytrack/pysense_0.0.2.dfu and not 1.0.0.dfu or something like that.

By the way, I just got working the accelerometer in both pytrack and pysenses, but the humidity, temperature, or glonass sensors don't work :(. May i wait some days more or is something that I have done wrong?

Edit: well, seems that i misunderstood the concept of the version of the DFU and the version of the Pytrack/Pysense libraries...
Futhermore, in the case of the Pysense, i forgot to print the values...Thanks to @Camot I could obtain some values but indeed, they are a bit unstable. About the Pytrack,I cannot get the coords. I modified the read function in order to print what it reads and well, it doesn't appear the word GNGLL so it is stuck in an infinite loop. Any ideas?

[livius]

@Pajarraco
Where do you have pytrack inside building? On it work for me.

[Pajarraco]

@livius I was running next to a window and it didnt work for me. Now I have just peeped the Pytrack outside with one hand and running the script and I could obtain the coords outside and inside. A little strange but well, it works :)

[gertjanvanhethof]

@papasmurph @jmarcelino Yes, I pressed the button and did a sudo call.
Atom pymakr plugin is working fine so I'am able to communicate with the board. What could be wrong?

[papasmurph]

@gertjanvanhethof Pressed the button and then inserted USB? Just checking :).

[gertjanvanhethof]

@papasmurph Yes, pressed button on the pysense board and then inserting the USB.
No problem to ask. You never now.
Could it be a problem because I'am using linux from in virtualbox.
As said Atom is working fine so port is working. But probably it takes more time to setup the serial connection through USB in that case, so causing the problem?
Make that sense?

[Pajarraco]

@gertjanvanhethof Are you releasing the buttom 1 s once you plug in the USB wire? Maybe you can try instead of dfu-util, dfu-util-stable, and try to add --device (the device id when it cannot be opened). I think another option to see if it detects the Dfu devices is to show a list with the option -l

[jmarcelino]

@gertjanvanhethof
Maybe virtualbox doesn't connect the DFU device automatically to Linux? The board appears as two different USB devices depending on if it's in DFU mode or not, not sure what Virtualbox does with that

[robert-hh]

@gertjanvanhethof The USB-support in virtual machine is mediocre, to be polite. Simple devices like a memory stick work most of the time, complicated ones like smartphones, Pyboard, ... almost never. Better grab an old computer and install linux there. Even a 10 year old will give you good performance with an window manager like XFCE. Try for instance Xubuntu or Mint Xfce.

[gertjanvanhethof]

@robert-hh @jmarcelino @Pajarraco I switched to a system without virtualbox and problem solved. Thanks for your help!

[johncaipa]

Anyone know how to get the battery voltage in the code from these boards?

[Camot]

@johncaipa

from pysense import Pysense

py = Pysense()

volt_float = py.read_battery_voltage()

[mqlopes]

@Camot Hello. I have both a Pysense and a Pytrack. I'm trying to read the battery voltage using "py.read_battery_voltage()", but I keep receiving the same values when the boards are connected to USB (with the batteries attached). For Pysense: 0.1203943 and for Pytrack 0.06017921. Thanks for your help.

[Camot]

@mqlopes

I am not sure I understand your point. Why do you expect a changing battery voltage when you board is USB powered? Unplug USB and you see the voltage decreasing slowly.

[papasmurph]

@mqlopes When USB is connected the voltage is stable 3.3 Volts, while the battery is being charged. What you are asking about would require hooking into the battery itself, which is not the case.

[mqlopes]

@Camot Tks for your advice.

[mqlopes]

@papasmurph Ok, I see. Thanks for your support.

[Jiemde]

Hi @papasmurph
What I understand is that it's the 3.3 volts who is tested with this function not the voltage of the battery ? Am I right ?
Jiemde

[papasmurph]

@Jiemde As far as I understand it's the driving voltage, so if connected to USB it's measuring the stable 3.3 Volt from the power supply, that then also charges the battery.