2017-04-02 (Su) Pi0 Laser Tag PiTagErrUs

Plenty of work was done but there was not a lot of progress. Nearly the whole day was spent trying to get drivers to correctly talk to the boards. At first, the most logical boards in the Arduino IDE were selected but they would not allow themselves to be programmed or even recognized by the computer. Finally, the Arduino website was consulted and the drivers were found.

After the drivers were installed there were still issues. In the Windows Device Manager (devmgmt.msc) the boards appeared as “Arduino Micro” so that was selected in Arduino IDE. This didn’t work. Two boards had already been assembled and they would not receive programming so a third was selected which didn’t have any components connected. In other Arduino models, primarily those with a 328P controller, connecting to the data pins will result in an inability to receive programming. It didn’t help in this case because the 32U4 controller doesn’t expose data pins used to talk to the computer.

Drivers from Sparkfun, which the selected boards are clones of, were also tried but without success.

The final resolution was to select the Arduino Leonardo, which uses the same controller. This was not seen as a viable option since before all the attempts to do this resulted in the board disconnecting during programming, reestablishing on a different com port, then coming back to the first com port after programming. Ultimately though, this is what worked. So, beware of this when ordering unofficial Arduino boards.

Programming was finally established and a simple LED flashing sketch was uploaded. RGB LED control will be important to the tagger so it was pleasing to see the pins working as expected.

Programmed Arduino Pro Micro


The rest of the posts for this project have been arranged by date

First time here?

Completed projects from year 1 
Completed projects from year 2
Completed projects from year 3

Disclaimer for http://24hourengineer.blogspot.com/ and 24hourengineer.com
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information in this blog, or linked by this blog, are not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on a post.
This blog, including pictures and text, is copyright to Brian McEvoy.

2017-04-01 (Sa)