Forum Replies Created
-
Posts
-
I apologize– tech support force of habit on where to find the device manager. I only meant to ask if you could see it in the device manager after installing the driver.
You say that it showed up on the device manager “on several occasions.” Do you mean to say that it only intermittently appears there? (I’m trying to figure out if there is any obvious hardware problem.)A couple of things for you to try:– Try other USB ports on your computer, if available. (We have heard of several cases where specific ports work better than others– and some cases where only USB 2.0 ports work, and others where only USB 3.0 ports work.)– If you are using a USB hub, try connecting directly to your computer.– Check to see if you have any other software running that may be trying to access the USB ports.– Check to see if you have any malware protection software that may be preventing you from accessing the USB ports.Please let me know what you find.If you get the “Unable to find an Eggbot” error message, you should try
one more time, as it can require two tries after being unplugged.The UBWDriverInstaller v 1.0 should be fine for your computer.You may also want to look at your device manager to see if the Eggbot
(listed as EiBotBoard — Ei being german for Egg) shows up there under
USB devices.
If you don’t know how to get to the device manager, you can find help
here: http://kb.iu.edu/data/agln.htmlNo need to surrender. It sounds like you have a damaged IC. Turning one around backwards and applying power will definitely break it. Do you have a replacement on hand?
Okay, please file me under “puzzled.” I may be able to try and damage a panel here for comparison, to see if I can find any possible explanation.
One the dim quadrant: I suggest that you try *gently, with the power off* replacing the IC in that quadrant with a different one, to see if that helps.I am not otherwise familiar with the issue, but found this discussion online, that might be helpful:
http://forum.processing.org/two/discussion/2716/windows-8-video-capture-issue/p1
Yes, it is quite possible to change the video source to take video from a file. I think that a few people have already done this, but I do not have example code for it at this time.
This is due to a change in the video library since we last updated the Peggy 2 library.Find the line that says:video = new Capture(this, 320, 240, 15); //Last number is frames per second
And, after that line, add the following:video.start();On the dim quadrant: Double check all of your resistor values in that quadrant.
On the mystery quadrant: that is a surprising result.
The ten LEDs in that half-quadrant are connected in series.
So, if one LED were damaged such that it gave no connection (or it was in backwards), I would expect all five to light up when you connect an extra LED across the pins of that one location. You would not be able to light an LED at any of the other locations.
And on the other hand, if one LED had a short circuit (for example, if its two pins were soldered together), I would expect the other four to normally be lit up, but brighter than usual.
Do you still have the same behavior now that you’ve replaced that LED– as in, will the other four locations still light up an LED? And, do you have access to a multimeter?
There may be more than one independent issue; the lack of response *may* not be related to to the five not lighting up.
The first step is to check the 5 LEDs that are not lighting up to see what the issue is. Check to see, for example, if any of the LEDs is backwards by looking for the flat sides of the collars. Check to see if any of those LEDs is not properly soldered. If that all looks fine, then one of the LEDs may have been damaged. Use a fresh LED, and place its two pins across the pins of each of those 5 LED locations, to see if it will light up a little bit.Please let me know what you find, and I’ll try to help you out from there. :)Fantastic– glad to hear it!
Unless I’m being daft, everything that you have described seems correct to me. (And, thank you for describing the situation so clearly!)
However, the “initialization failed” error is a blanket error which basically means that there’s no good connection. It could be hardware (wiring, ISP connector installed on the wrong side of the board, bad solder joint somewhere, solder bridge, etc) or it could be software. To help eliminate things, you might try using one of our standard makefiles.Download the code example and makefile here:Edit the file to change programmer type, by commenting out line 6 and uncommenting line 7.Then, at the command line, compile with “make all” and then upload the program with “make install”. The full avrdude command that it calls should be as follows:avrdude -p m164p -c usbtiny -P usb -v -e -B 4 -U lfuse:w:0xC2:m -U hfuse:w:0xD9:m -U efuse:w:0xFD:m -U flash:w:octolively.hex
One of the things to note there is that you do (I think) have to explicitly tell it to look on the USB port, with that “-P usb” above. :)I believe that standard functions that are *specific* to the Meggy Jr RGB are documented in the programming guide. But, there are also custom functions defined within many of the other examples, and there are also all of the functions listed in the Arduino documentation ( http://arduino.cc/en/Reference/HomePage ) to draw from. If you’ve found others, or have a specific question about any given function, I’d be happy to help.
Okay– sounds a little complicated, but I’m glad that you have it working. :)
