WiPy 2&3

• U

  Q: ussl usage for https - problem
  • ubiq_01  

  8
  0
  Votes
  8
  Posts
  3699
  Views

  D

  Hello Satish, Please check the MQTT example that I posted in https://forum.pycom.io/topic/352/aws-iot-device-support-for-lopy/5 Cheers, Daniel
• 

  WiPy pin 3V3 not work?
  • livius  

  11
  0
  Votes
  11
  Posts
  3364
  Views

  

  a) WiPy consumes a substantial peak current when sending. That may be for a few ms only each time, but that makes it even harder for a power supply, because the impedance has to be low and the regulation speed fast. b) I prefer to take the 3.3V pin as an output and would always supply it through the Vin pin. Then the internal power regulator ensures a proper supply.
• H

  Interrupt Problem
  • HellDesk  

  3
  0
  Votes
  3
  Posts
  1052
  Views

  H

  Yeah @livius I actually already posted there - thanks. If anyone else is looking, that is where you can find the solution to this issue. @KMcLoud very kindly posted his solution and I'm digging deeper now that this is resolved. Much appreciated.
• K

  Simple Interrupt Problem
  • KMcLoud  

  7
  0
  Votes
  7
  Posts
  1984
  Views

  K

  This works: import micropython from machine import Pin micropython.alloc_emergency_exception_buf(100) int_counter =0 def int_handler(pin_obj): global int_counter int_counter+=1 button=Pin('GP17', mode=Pin.IN, pull=Pin.PULL_UP) button.irq(trigger=Pin.IRQ_RISING|Pin.IRQ_FALLING, handler=int_handler) The key is that the "os" passes the pin object to the callback function as an argument. However, if your callback function isnt expecting any arguments, this causes an exception. Since the exception occurs outside of the main program execution its a little confusing to debug.
• 

  Two questions to pycom. Protect code and delivery of fipy
  • livius  

  3
  0
  Votes
  3
  Posts
  1402
  Views

  

  @daniel great for both answers thank you
• M

  Firmware Update
  • Meide  

  19
  1
  Votes
  19
  Posts
  4680
  Views

  M

  And for those that interest, the connection works also without the TX Jumper
• C

  Documentation for Expansion board 2.0 jumper settings
  • cappy2112  

  2
  0
  Votes
  2
  Posts
  1095
  Views

  

  @iber said in Expansion Board 2.0 - feature selection jumpers: there is a documentation on a github repo. *Edit Found it: https://github.com/wipy/wipy/blob/master/docs/User_manual_exp_board.pdf
• D

  The WiPy 2.0 is "toast" - Here is why:
  • dan1824  

  2
  0
  Votes
  2
  Posts
  928
  Views

  

  Hi @dan1824, We actually started improving our docs last week. You can find a first version of it here. Daniel made a post about it saturday. It's not done yet, but we already put some effort already to make clear which features are there and which are not there (see What's under the hood). We'll keep improving it in the coming period.
• D

  WiPy 2.0> Touch Pin
  • dan1824  

  4
  1
  Votes
  4
  Posts
  1372
  Views

  D

  @dan1824 Thanks for your feedback, which we also appreciate a lot. We are aware of the ambiguities an inconsistencies in the documentation, That's why we started to re-build them with a new format and structure. A preview of the new docs is here. It's not complete or fully accurate yet, but we plan to have it all there by the end of next week, along with clarifications of which features are already available, and which are not. Cheers, Daniel
• D

  WiPy 2.0 workin machine.deepsleep() example with IRQ-usage
  • dan1824  

  5
  0
  Votes
  5
  Posts
  2479
  Views

  L

  Deep sleep is a somewhat nebulous chapter; for one thing, the ESP32 manual doesn't have the power management chapter yet. Similarly, sleep mode is not yet implemented in Pycom's ESP32 port of MicroPython. I believe, when deep sleep actually does work, it cuts power to the RAM so a wakeup is a boot with the deep sleep reset cause, and the pins that can cause it to wake may be only the RTC ones. Most of that's guessing and conjecture. PS. Well, considering that was your thread, I'm not sure why it was expected to work? I vaguely recall somewhere else mentioning sleep will be in place for 1.0, which was planned for sometime in December, but there's a lot of work still to do.
• D

  Connect CCTV Camera to Wipy?
  • dan1824  

  2
  0
  Votes
  2
  Posts
  950
  Views

  No one has replied

• P

  Some one call help for awake Wipy 1 on Pin rising edge
  • pchirouze  

  2
  0
  Votes
  2
  Posts
  890
  Views

  P

  Sorry for everybody, I have finaly found the good syntax pin17.irq(trigger=Pin.IRQ_FALLING, wake=machine.SLEEP) Thats right now
• 

  WiPy 1.0 firmware v1.8.6 release 1.20 x v1.8.2 release 1.30
  • rcolistete  

  4
  0
  Votes
  4
  Posts
  1694
  Views

  

  @livius See the topic with benchmark, where there are links to download the files, so you can test yourself.
• J

  Please help with WiPy 2 pinout
  • jnc  

  2
  0
  Votes
  2
  Posts
  1040
  Views

  

  Hello @jnc, Let me refer you to this topic where you can find the answer you are looking for https://forum.pycom.io/topic/242/expansion-board-pin-numbers-vs-lopy-pin-numbers/4 if you are still confused please let me know. Best, Roberto
• D

  Wipy 2 first firmware upgrade failed
  • dg66  

  3
  0
  Votes
  3
  Posts
  1315
  Views

  D

  Oh ! did not noticied there was a missing jumber on the expansion board (realy missing at unboxing the expansion board). Thx a lot, everything is working fine for now
• M

  Wipy 2.0 and hostapd AP
  • michal  

  2
  0
  Votes
  2
  Posts
  772
  Views

  No one has replied

• R

  WiPy crashes now after update to wipy_0.9.3.b2.bin
  • rockybulwinkle  

  8
  0
  Votes
  8
  Posts
  1967
  Views

  R

  Thanks, that helped.
• 

  Links for code samples about sensors with WiPy2.0
  • livius  

  3
  0
  Votes
  3
  Posts
  1538
  Views

  X

  @livius said in Links for code samples about sensors with WiPy2.0: LCD 16x2 (HD44780) I'm using a PCF8591 I2C extender with a HD44780 compatible display. You can find several code examples and libraries for micropython on github that require minimal changes. HC-SR04 This one requires Timer support to be implemented first (hopefully in tomorrow's firmware release). Never used the DHT* sensors so not sure about their communication protocol.
• J

  Control C usage
  • jcrfonera  

  2
  0
  Votes
  2
  Posts
  879
  Views

  

  HI @jcrfonera, Connect using telnet and try it out. You'll see that it indeed throws an KeyboardInterrupt error and will stop the code. Ctrl+C is not implemented in the pymakr console unfortunately, but that might be added in a future release.
• J

  working frequency for esp32
  • jcrfonera  

  2
  0
  Votes
  2
  Posts
  1315
  Views

  D

  @jcrfonera We are using 80MHz because we are optimizing everything to make it work with the lowest frequency. Later we will make an API available to select the CPU clock between 80, 160 and 240 MHz.