WEEKLY UPDATE W/C 7th Nov

[jonirons]

@jonirons Here's my guess:

A bunch of really talented developers (I mean that) were told by some corporate freaks "have we got a deal for you!"

The developers said - "It's not ready yet"

The corporate freaks said "It's got to go now now now"

The developers said - "It's not ready yet"

The corporate freaks said "marketing have got the glossy brochures, we've got the cool web-site, we've got the online payment channel - g0 go go - Developers WORK HARDER"

Something like that?

[Fred]

@jonirons it's good to see you got it right from the beginning: HERE'S MY GUESS.

[jonirons]

@Fred ;) in the absence of information that's all I can do!

[Fred]

@jonirons fair enough :) My bad. We appreciate you guys have put a lot of trust into Pycom. Unfortunately hardware design can suffer these delays as you developers will know only too well. I will come back a little later with a more comprehensive update for the week. Thanks

[jonirons]

@Fred PyCom needs to immediately stop selling this as a product that is "enterprise grade" and has the following features: https://www.pycom.io/solutions/py-boards/wipy2/

and realistically say "Our plan is to have the following features:" https://www.pycom.io/solutions/py-boards/wipy2/

You also need to put those of us who've been conned into buying them in contact with your (as previously stated) really good developers. All the stuff I expect to already work on WiPy 2 already works on WiPy 1 - it took me about 15 minutes to port a weekends buggering about to WiPy 1 and it all just worked.

GIVE US A ROADMAP

The WiPy2 and the rest of the multi-channel devices have enormous potential with talented developers who can make it work. Tell us "Here's how it will play out". I will follow it, and re-engage, but at the moment you're wasting my time!

PyCom needs to re-think its communication strategy!

[Fred]

@jonirons nobody is conning anybody! Feel free to return the product and we will refund including postage. Email me on fred@pycom.io Thanks Fred

[jonirons]

The enormous potential comment still stands. I still want this to be great, and your development team have already done this before. I would prefer a ROADMAP.

If you let me know that I'm happy to change my mind-set to a Kickstarter kind of deal. Otherwise I will likely take up your offer and send it back (and all the follow on)

Like I said - rethink the communication strategy, and stop selling this as a finished product. This is not yet yet worthy of a beta software release.

May of the documented features are not available (not buggy, just simply NOT THERE).
The "fully featured IDE that connects automatically to your Pycom" PyMakr has yet to talk to any WiPy (1 or 2) for more than a few seconds before giving an error that can't be got rid of without using "Activity Monitor".

We know software development is difficult and time consuming. TELL US WHERE YOU"RE AT.

[daniel]

@jonirons what features that are documented in: https://docs.pycom.io/wipy2/ are not available in the software? Or do you mean documented in the spec sheet? Thanks.

Cheers,
Daniel

[jonirons]

@daniel - Both

following the links from https://docs.pycom.io/wipy2/ -> click on Library Reference -> Pycom boards specific features -> try importing pycom module

From the spec sheet, try googling WiPy2 RTC - get result https://docs.pycom.io/wipy2/library/machine.RTC.html - no machine.RTC module. (admittedly I see it isn't linked directly from the above module)

In addition, and as documented previously No success getting PyMakr ide connecting to any board at all for more that a few seconds, whether factory clean, configured or via USB. Although Telnet, Screen and FTP are working fine.

[daniel]

@jonirons OK, you are right about the RTC: https://docs.pycom.io/wipy2/library/machine.RTC.html somehow it filtered into the generated docs. But the pycom module is available, since the first release of the firmware.

[jonirons]

Getting up a level, it would be great to have a road map so we can see when some of the staples like rtc, watch dog feeding, timer interrupts are expected (maybe these are there and I just haven't found the doco)

[Ralph]

@jonirons said in WEEKLY UPDATE W/C 7th Nov:

The "fully featured IDE that connects automatically to your Pycom" PyMakr has yet to talk to any WiPy (1 or 2) for more than a few seconds before giving an error that can't be got rid of without using "Activity Monitor".

Can you make a forum post with the details of this error and after what actions you are getting it? Maybe we can help you resolve it.

[jonirons]

From my forum post 16 days ago:
"Confirm I'm having the same problem with Pymakr and wipy1.
Have set up boot.py to connect to my wlan
Can connect to board using telnet.
Can update using FTP

Can't connect using Pymakr

I get a popup error dialog with the message:
Warning:
QStackedWidget::setCurrentWidget: widget 0x7fe1ccddc0d0 not contained in stack

Behind the error popup is:
Connecting to a Pycom device...
Error while communicating with the Pycom device! (click to attempt to reconnect)

I'm not sure what to click, but if you go to preferences -> Pycom Device -> Ok
I get the Error while communicating message again."

[jonirons]

I'm still getting the same problem with wipy1 and with wipy2

[jonirons]

@Ralph still having the issue described below (QStackedWidget::setCurrentWidget: widget 0x7feac359e370 not contained in stack) with 0.9.4.b1 and latest PyMakr release.

Any help for me?

[Ralph]

Hi @jonirons,
Sorry about not responding to this issue 16 days ago, it got forgotten between all the other posts. I just responded to your message in that topic.