Jim discovered that some of the gece's are sensitive to noise while they're in addressing mode before the controller starts sending data. His solution was a pull down resistor on the data pins to hold them low until the prop started sending data. I've never seen this problem on my GECEs when I hd them. And it seems like the problem didn't start happening until this year and only on 682 boards. So I'm not sure if it's a manufacturing variation in the newer GECE pixels or something on the 682 or its newer firmware. Bottom line is that GECEs need to be power cycled with the controller, and the data needs to be silent until the data is valid. Also the off rest time required to reset them can be very significant at times, I've seen up to 30 seconds. Grounding the data pin during power cycle seemed to shorten that reset time.
--Jon Chuchla--
Sent from my iPhone using Tapatalk
I shut everything down and performed a cold start on all the boards and the pixels.
Funny thing .. the 6804 and the Parallax with the ENC28J60 came right up and in perfect sync ... The Wiznet (running the older SD code(?) is the one that has the issues getting back in the grove ..
I guess until I can rework my work space and get everything powered correctly so I can reset each board with its pixels independently I might as well hold up.
Bob
On a side note, I have been posting on the parallax forum regarding speeding up spin code. One of the forum members graciously provided his enc28j60 driver, where he had already unrolled a lot of the code (and made some other improvements). He claims his changes to the driver doubled the throughput. I'm currently testing his driver; I'll post the updated spin files in the next day or two after my initial testing is complete.
Here's a link to the posts on the parallax forum:
http://forums.parallax.com/showthread.php/160356-Spin-speed-up/page2
Here's the latest code with the updated enc28j60 driver:
I also reduced the timing on the GECE code from 10us to 7us, this "should" allow for a refresh rate of about 47hz with a string length of 36. I tested this code with xlights (20hz) and didn't see any issues with flickering/jitter, so now hopefully Bob can check with LOR set with .025 timing (40hz refresh rate). I don't really expect it to keep up, but it will be interesting to see what the results are. There are still a few more areas in the code I can still optimize if needed.
On a side note, I received my w5100 arduino Ethernet shields and have been playing with the e680 code. At first I couldn't get it to work, and it turns out I didn't have it wired correctly. According to the seedstudio wiki:
http://www.seeedstudio.com/wiki/Ethernet_Shield_V1.0
I connected the following pins on the shield to the corresponding pins on the quickstart.
D11 - Used for SPI MOSI
D12 - Used for SPI MISO
D13 - Used for SPI SCK
Well, it turns out MOSI,MISO, and SCK aren't connected to these pins on the shield. They are connected to the ICSP header. Here's a wiring diagram I found:
http://www.epyon.be/2013/07/06/using-the-teensy-3-0-with-the-arduino-ethernet-shield/
brown wire - Used for SPI MOSI
yellow wire - Used for SPI MISO
green wire - Used for SPI SCK
After I made these changes, it worked like a champ. Maybe someone with more arduino experience can explain why the D11,D12, and D13 pins were called out to be used with SPI when in fact there's no actual connection to these pins on the shield?
Is your shield the standard arduino ethernet shield or some other variant? I think I recall the seeed shields being somewhat different than the standard ones.
--Jon Chuchla--
Sent from my iPhone using Tapatalk
jchuchla wrote:Is your shield the standard arduino ethernet shield or some other variant? I think I recall the seeed shields being somewhat different than the standard ones.--Jon Chuchla--
Sent from my iPhone using Tapatalk
It is different in that there's no SD card slot. However, I believe it uses the same arduino library as the standard shield.
I wonder if that has been my problem with the arduino shield? I have one of the 3rd party versions with the SD card. Moot point now though. I have a Wiznet 812 and an 820 along with the enc28j60. I'm supposed to have 3 more of the ENC boards but they are on a slow boat from China. They shipped Feb 9th and still haven't made it. Between Chinese New Year and the problems at the west coast port...they may be another month getting here.....lessons learned....
I know that they also have a w5200 shield. And I think itead has the w5500 version as well.
I have heard of people using the seeed shield with the komby stuff and h inc problems. It may be as simple as a pinout mismatch.
--Jon Chuchla--
Sent from my iPhone using Tapatalk
jchuchla wrote:I know that they also have a w5200 shield. And I think itead has the w5500 version as well.
I have heard of people using the seeed shield with the komby stuff and h inc problems. It may be as simple as a pinout mismatch.--Jon Chuchla--
Sent from my iPhone using Tapatalk
I have the seeed w5200 shield on the way. According to the schematic, it has the same pinout as their w5100 shield.
The 5200 version definately needs a different driver. The register addresses are different.
--Jon Chuchla--
Sent from my iPhone using Tapatalk
