Search found 10 matches
- Fri Feb 26, 2016 10:27 pm
- Forum: WiPy and CC3200 boards
- Topic: Controlling hobby servos
- Replies: 21
- Views: 24801
Re: Controlling hobby servos
Hi Daniel, after upgrading to https://github.com/wipy/wipy/releases/tag/1.2.0 everything works fine (including Timer with the new improvements) but I get : >>> os.uname() (sysname='WiPy', nodename='WiPy', release='1.1.1', version='v1.6-82-g12547ce-dirty on 2016-02-22', machine='WiPy with CC3200') sh...
- Tue Jan 26, 2016 1:11 pm
- Forum: WiPy and CC3200 boards
- Topic: SPI not working
- Replies: 4
- Views: 5523
Re: SPI not working
@danicampora
I suspect an hardware problem on my Wipy module.
I've just ordered a new one and will test again as soon as it arrives.
Pascal
I suspect an hardware problem on my Wipy module.
I've just ordered a new one and will test again as soon as it arrives.
Pascal
- Sat Jan 23, 2016 9:36 pm
- Forum: WiPy and CC3200 boards
- Topic: SPI not working
- Replies: 4
- Views: 5523
Re: SPI not working
Daniel,
mistake : GP30 is MISO (by default) so an input. no activity is just normal...
ignore my remark on this point.
Pascal
mistake : GP30 is MISO (by default) so an input. no activity is just normal...
ignore my remark on this point.
Pascal
- Sat Jan 23, 2016 9:33 pm
- Forum: WiPy and CC3200 boards
- Topic: SPI not working
- Replies: 4
- Views: 5523
Re: SPI not working
Hi Daniel, thank you for the ultra fast answer! Unhappily the issue is not solved. My new code : from machine import SPI from machine import Pin cs = Pin('GP17',mode=Pin.ALT, alt = 7) spi = SPI(0, SPI.MASTER, baudrate=200000, polarity=0, phase=0, firstbit=SPI.MSB, pins=('GP14', 'GP16', 'GP15')) for ...
- Sat Jan 23, 2016 8:54 pm
- Forum: WiPy and CC3200 boards
- Topic: SPI not working
- Replies: 4
- Views: 5523
SPI not working
Hello, trying to connect an SPI device. using GP14, GP15, GP16 as SCLK, MOSI, MISO. from machine import SPI spi = SPI(0, SPI.MASTER, baudrate=2000000, polarity=0, phase=0, firstbit=SPI.MSB) for i in range(3) : mydata = bytearray([1,2,3,4]) spi.write(mydata) time.sleep(2) checked with a scope : MOSI ...
- Sun Dec 20, 2015 9:38 pm
- Forum: WiPy and CC3200 boards
- Topic: Unable to start/stop FTP server
- Replies: 2
- Views: 4177
- Wed Dec 16, 2015 8:51 pm
- Forum: WiPy and CC3200 boards
- Topic: Unable to start/stop FTP server
- Replies: 2
- Views: 4177
Unable to start/stop FTP server
Hi all, I want to stop the FTP server during the execution of my python code.
I tried :
but I get :
TypeError: argument num/types mismatch
Same error with :
Any idea ?
I tried :
Code: Select all
import network
network.server.deinit()
TypeError: argument num/types mismatch
Same error with :
Code: Select all
network.server.isrunning()
- Sat Oct 31, 2015 9:05 pm
- Forum: WiPy and CC3200 boards
- Topic: NTP library for WiPy
- Replies: 9
- Views: 15454
Re: NTP library for WiPy
Hi Andrew,
Absolutely right ! I never took the time to dive into NTP. Now I can say I did !
Hi Dave,
Yes it is a good fix, but the quality of the clock is rather poor on the Wipy and calling the NTP server one more time is probably a good idea
Thanks for the help
Pascal
Absolutely right ! I never took the time to dive into NTP. Now I can say I did !
Hi Dave,
Yes it is a good fix, but the quality of the clock is rather poor on the Wipy and calling the NTP server one more time is probably a good idea
Thanks for the help
Pascal
- Sat Oct 31, 2015 6:33 pm
- Forum: WiPy and CC3200 boards
- Topic: NTP library for WiPy
- Replies: 9
- Views: 15454
Re: NTP library for WiPy
Hi Andrew, I think I found my problem. The call to RTC with empty parameters reinits the clock with a specific date and time. (line rtc = RTC()) The problem comes from the fact that the offset value has been calculated before with a possibly different value of RTC (that is the case by example if you...
- Tue Oct 27, 2015 10:37 pm
- Forum: WiPy and CC3200 boards
- Topic: NTP library for WiPy
- Replies: 9
- Views: 15454
Re: NTP library for WiPy
Hi Andrew, Thanks for this job. Unfortunately it does not work for me. In fact, it does not work the same each time it runs (I get different time.localtime() after each try). Sometimes, the time is quite near of the real time. Sometimes quite far ex: (2015, 10, 27, 22, 9, 44, 1, 300) (2015, 1, 1, 0,...