Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - rudydevolder

Pages: 1 [2]
Thank you, you guys are awesome. Thanks for the good service and quick replies. I am impressed with the scripting language,  the editor, autocompletion and autoformatting makes it a superfast tool.
I know programming and debugging is far from easy, you're also depending on other tools with limitations and bugs you often bump in to.
Keep up the good work  ;D

My 3th module bricked now.  :'(
After I ran the program successfully in debug mode I just wanted to upload, immediately after my mcModule was bricked, I didn't modify any code.

I hope soon the new version from the OTA update to reset the script will come out, so I can test further, because now I'm totally stuck.

I was experimenting with my SPI to WS2801 LED software. Working pretty well at first, only the first LED was flickering but I found this is a common problem with the length of the cable or the power supply to the Led's and I only tried with different speeds of the SPI-bus, recompiling and uploading again and again, than it happened.

Hi, I will surely order the dev-board,  I like. But even than I need to put male headers on my mcModule to fit the dev-board with female headers, right?
Also, I want to make a small compact adapter board with a bigger header. I hope though somebody else will make 😉
I want to order at Digikey very soon. So to be compatible with the dev-board I want to be sure what fits. Can you inform me please?

mc-Module / Re: SPI problems
« on: August 05, 2016, 05:36:14 am »
It works  ;) ;D  after swapping the MOSI and MISO line !

There must be an error in the documentation it says: in chapter 12.3
The Create method creates an object that describe the path to a chip by specifying Speed, Mode, SCLK, MOSI, MISO and SC.
But it's, Speed, Mode, SCLCK, MISO, MOSI, CS

I don't know why I got a signal on the input but I guess it's just because nothing was connected, so I thought I was really displaying the info from the MOSI line while it was the MISO connection.

I'm so happy to know that SPI is done by hardware and not bitbanged! Love it! Tomorrow I will start to experiment with the WS2801 LED's ! Yippeee

Thanks mr. mc Abe. And thanks mc Things for the hardware SPI, much better!

So Headers with a spacing of 0.050" (1.27mm) and 8 pins will do I think. :)

mc-Module / Re: SPI problems
« on: August 04, 2016, 05:22:37 am »
I just tried your suggestion mr mc-Abe, but no difference. Tried modus 0 till 4 I can see differences in the polarity of the clock, also switched the MOSI with the CLK line on my logic analyser. But after studying some examples on the internet and making a working example on the SPI on my Feather Huzzah, I can only conclude that the signal is totally off. The only resembling with a correct pattern is that clock is symmetric and the CS line is working but than in my example and on the internet I see mostly bursts of the clock-signal for each byte, and also the typical pattern transmitting the bytes 0, 1, 2, 3, 4 I did in both test are totally off. I give you the working test on my Feather Huzzah in attachment. You can see clearly how the information is correctly interpreted by the analyser and how the clock and Mosi line behaves in time.

[ Guests cannot view attachments ]

Can somebody give me a reference or the spacing?
I want to order male and female headers and maybe some kind of breakout-board so I can easily change and connect my module. :D

Hmm, I can't find the code any-more and I don't want to brick another module before I can unbrick my 2 modules first. But I think I know what my mistake was.:
Instead of :
Dim data As ListOfByte = New ListOfByte
I forgot the New statement and did:
Dim data As ListOfByte = ListOfByte  :P

After that I did:

I found out about my mistake by running in the debugger, he complaint that I had a null pointer variable or something like that. :o
My compiler didn't complain and so my module became bricked. So I think it's good practice to debug always first.  ???

mc-Module / Re: SPI problems
« on: August 03, 2016, 11:37:19 pm »
Tried your code, except I used other pins because I soldered the wires already but same result. :'(
I used following Pins: dev = Spi.Create(1000000, 0, Pin.Pin6, Pin.Pin5, Pin.Pin4, Pin.Pin3)
I 've put the output of my logic analyser in attachment.

I wonder if the McModule doesn't has hardware SPI because it's using bitbanging now. I know because you can define any pins to do SPI.
I want to steer a set of WS2801 Leds and I know bitbanging has generally issues because the throughput isn't that stable and continuous to command so many LED's at once.

[ Guests cannot view attachments ]

mc-Module / [SOLVED] SPI problems
« on: August 03, 2016, 01:56:27 am »
First of all it took me a while to figure out I had to place Spi.Create in the Shared Boot Event() instead of in Sub New()
At least to get some signal out, I don't know why but when I place Spi.create in Sub new() nothing happens on the spi-bus with Transfer.
But placed spi.create in the Shared Boot Event I can see the clock-signal and the CS working but the data is always xFF whatever I try to send and whatever speed or mode I use.
I can clearly see the amount of bytes I've send with the Transfer() command but my logic analyser shows every byte as 0xFF, indeed when I try to connect my WS2801 Leds the only thing I get out of it is plain white and no colors.

Red LED flashes every 5 seconds.
Beacon updates: I cannot even see it in devices.  :-[
I assume the module is resetting (hence red led flashes every 5 seconds), but I can't connect to try to reload the program/script.
All firmware and software are the latest versions. I found another topic almost the same that said to install firmware 0.7 v361, I already had this installed, so I tried to upgrade again.
The upgrade works, but the problem remains.  >:(
I read there will be an option to erase the script in the new OTA-update software. I hope this version will be available soon::)
- Last update: Bricked a second module, found the problem: I used Shared Event Boot() only did some Dim's in it and a for next loop with a Type-Casting inside.

Pages: 1 [2]