Getting started with PyGos and Pylife

[Vincèn PUJOL]

@Pete-Allen-0 said in Getting started with PyGos and Pylife:

Welcome to the PyLife section of the forum. This is a space for discussion and help about using PyGos with the Pylife app.
The first place to go to get started with PyGos is our documentation:
https://docs.pycom.io/pylife/

This should cover everything to get you up and running, and please say if there are things that aren't clear.

For those of you who like to plug things in and try them out before reading and documentation: it is important to do a firmware upgrade as soon as you turn the PyGo on.

If you are on Android, please make sure you are using the most recent version of the app.

Thanks for all your useless points sorry to say :( Docs I got time to read it before receiving device, firmware update has been done and so far has been only thing I have been able to do with the device :(, Android app up-to-date as it has been downloaded from play store just 2 days ago....
So far I'm unable to wake up device, and unable to use it for anything, it doesn't report anything in mobile app, unable to setup Lora frequency !! For me it's clearly a not finished product with unusable firmware ! How can you ship and sell such products without big warning on your website of the shitty state of firmware and app to use it (sorry to be rude but it's exactly state of it as I can see it on my own unit and reading forum...)
Last most important point: do you plan and when to release a working firmware for at least features announced on your website ? or should I return it straight for refund ?

[Axel Roest]

@Brian-Wyld
In the Netherlands I had to pay € 40,44, which is a steep increase in price indeed.

Thoroughly unsatisfied about that, and to add insult to injury, the devices do not work either!

[Axel Roest]

How to determine the difference between the PyGo 1 and PyGo 2?

The app explicitely lists them separately, but I cannot see from the outside which one is the version 1 or 2. And the app doesn't work of course, as it cannot add the devices (because they already exists), nor update the firmware (because it can't find them).

Such is (py)life!
It's mid August; two months after release, and Pycom still has not fixed their software, leaving thousands of people with broken devices, and NO WORD from pycom, which is even worse.

[robert-hh]

@Axel-Roest If you have the cradle, connect it to a USB serial terminal. When the device boot, it shows it's type in the boot message.

[hjoe]

@robert-hh
unfortunately we have two "Getting started with PyGos and Pylife", one at /Home/PyGo the other one at /Home/Pylife. But are two needed as long as neither Pylife nor PyGos are working.
Robert, I got a gradle, but was not able to update the firmware as described in the other forum.
As long as only frustrated users are talking to each other without comments from Pycom, its more or less useless.

[robert-hh]

@hjoe Yes, the state is chaotic, and Pycom i silent. Very frustrating for users like us. When you connect the cradle to a USB serial terminal at 115200 baud, do you get any boot up messages, of a Python REPL prompt?

[exa]

This post is deleted!

[hjoe]

This post is deleted!

[Gritty moonshaw]

I expect they are too busy dealing with the impending sh*t show that will be their helium miner to care about the Poo-Go now.

[robert-hh]

@Gritty-moonshaw Yes, it looks like the helium miner is a similar success story. Also, no response about that topic. I'm wondering what's up with the company.

[Keptenkurk]

@robert-hh It is my feeling that the company never recovered from CTO Daniel Campora changing jobs in august 2018 .

[robert-hh]

@Keptenkurk It seems that they lost their software mastermind. Daniel made the MicroPython port first for Wipy1 and then for the development boards of PyCom. There are still excellent people at PyCom, but it looks like there is no one keeping a consistent direction. And the people turnover seems pretty fast. Especially the poor people being responsible for customer service and the forum. Not good for building up knowledge.

[livius]

@robert-hh said in Getting started with PyGos and Pylife:

Not good for building up knowledge.

Yes, and not good for building a trust which is probably even more important.

[Vincèn PUJOL]

Well here and I suggest at everyone that is able to do it to contact its bank to decline the credit card operation as Pycom is not answering here neither at emails adressed at support, their website is seriously broken which is not really a good sign also.... and quite bored of these companies that don't give a shit about customers and their products (when you are payed by investors instead of being on real market with competitors it doesn't help for sure to do good products and PyCom is a great example of it from what I have seen and read around...

[Brian Wyld]

@robert-hh
Received my cradle, and summoned up the energy to plug it in...

Screen shows the charging graphics (big battery symbol with 1 bar flashing), but doesn't yet do anything else (no tap response, hasn't made it above 1 bar so far).

At 115200 baud I get a REPL prompt (after hitting return a few times).
I reboot with machine.reset() and checked the wifi setup:

>>> machine.reset()
machine.reset()
Pylife start
4 Set interrupt: Double Tap,
b'\x124\xc0\xde\x1a\xb5\x124\xc0\xde\x1a\xb5\xca\x1a\x11\x0f'
RTC: (1970, 1, 1, 0, 0, 8, 765473, None)
Coex register schm btdm cb faild
BLE name: PyGo 11006
Pycom MicroPython 1.20.4.r4 [v1.11-258cda230] on 2022-06-13; PyGo1 with ESP32
Pybytes Version: 1.6.1
Pymesh Version: 1.4.0
Type "help()" for more information.
>>> import pycom;pycom.wifi_ssid_sta();pycom.wifi_pwd_sta();pycom.wifi_ssid_ap();pycom.wifi_pwd_ap();pycom.wifi_on_boot();pycom.wifi_mode_on_boot()
import pycom;pycom.wifi_ssid_sta();pycom.wifi_pwd_sta();pycom.wifi_ssid_ap();pycom.wifi_pwd_ap();pycom.wifi_on_boot();pycom.wifi_mode_on_boot()
'PyCom_AP_Firmware_Update'
'www.pycom.io'
False
1

I set the wifi ap to come on at boot in STA and AP mode, and rebooted

>>> import pycom;import network;pycom.wifi_on_boot(True);pycom.wifi_mode_on_boot(network.WLAN.STA_AP)
>>> import machine;machine.reset()

Now the AP is visible from my PC, I can connect to it, and ftp to 192.168.4.1 as usual (micro/python login).

Via the ftp I can upload a new main.py:

# main.py -- put your code here!
print("Hello this is my pygo")

and when I reset it gets run as expected

Pylife start
4 Set interrupt: Double Tap,
b'\x124\xc0\xde\x1a\xb5\x124\xc0\xde\x1a\xb5\xca\x1a\x11\x0f'
RTC: (1970, 1, 1, 0, 0, 8, 765473, None)
Coex register schm btdm cb faild
BLE name: PyGo 11006
Hello this is my pygo
Pycom MicroPython 1.20.4.r4 [v1.11-258cda230] on 2022-06-13; PyGo1 with ESP32
Pybytes Version: 1.6.1
Pymesh Version: 1.4.0
Type "help()" for more information.
>>> 

So far so vanilla pycom...

Should be ok to run whatever you want then from the main.py; but would need some info on the libs/pinouts to drive the screen/accelero and other specific hw, and probably on what happens with the power management thing - I saw a log about 'low power, sleeping for 30s' and also a 'Switching off GPS power!'...

I note its starting with pybytes enabled, so I guess next step could be to register/activate it in pybytes as per the usual pybytes instructions...

[Brian Wyld]

@Brian-Wyld
More testing :
after an overnigth charge in the cradle, it shows 3 bars (out of 4 possible?). Warm to the touch but not hot like the inductive charging.

Telnet access to REPL is maintained after removal from the cradle, but after a certain time (5 mins?) it seems to go to sleep (as no external power input I suppose)

>>>
>>> 79547 Set interrupt: Double Tap,
Connection closed by foreign host.

No tapping sequence I can find to wake it up (or to do anything when its awake also).

It woke up again (AP reappears, can telnet) but no info as to why...

[andrethemac]

@arikb Same here. I backed for a Pygo1 and Pygo2. I got the devices. But without documentation there basicly useless. For example. Yes, you can send a message to the device but aside from the enveloppe symbol there is nothing to see. GPS never gets updated. devices reboots every couple of minutes. (all on the latest firmware).
So Pycom, please give us the documentation so we can start developping stuff with it.
The specs look great, please let this not gather dust.
Andre

[jcaron]

@andrethemac they have already stated there would be no developer documentation, despite the promises in the Kickstarter campaign. No word from them since…

[Vincèn PUJOL]

@jcaron said in Getting started with PyGos and Pylife:

@andrethemac they have already stated there would be no developer documentation, despite the promises in the Kickstarter campaign. No word from them since…

In that case I think only solution possible is Class Action against Pycom and maximum of publicity of their behaviour on blogs of people that have one no ?

[Axel Roest]

@robert-hh
Thank you very much!

115200 baud?