« Last post by mklrobo on January 20, 2016, 06:48:51 AM »
Yes, I have had a similar problem. I can not convert to the elf file, which is needed for final
download. Even then, you may not be able to download via your USB, because you may need
a "virtual" USB software driver.(available in the tutorials). I eventually bought a separate hardware programmer, which studio 4 recognizes, but still did not have the elf file.
Getting closer to the answer, though.................
« Last post by Ahdem99 on January 19, 2016, 06:49:28 PM »
Hey guys, im working on my first robot, so i`m new to robotics, also new to programming, so, when i make my project with Project Designer, i get to the point where i need to convert the code that PD made, into .hex. I do it using AVR Studio 4. As it says in the tutorial, i go to build, then Rebuild all, but it always ends up with an error :
make: *** No rule to make target `../../../All', needed by `VR_Axon2_demo.elf'. Stop.
Build failed with 1 errors and 0 warnings...
So, i got stuck by this, and i cant really do anything. I did it several times, and i always get this error. I`m using WindowsXP, and i think that the problem is naming the files, and i don`t know where i did wrong.
Please help meee!
« Last post by mklrobo on January 17, 2016, 05:30:38 PM »
« Last post by Shadowcry on January 16, 2016, 04:00:34 PM »
NEW YORK, Dec. 22, 2015 /PRNewswire-iReach/ -- FAA unwraps drone rules for the holidays. Fearing as many as a million new drones might land under Christmas trees this year.FAA has announced a new regulation on drones. The Obama administration announced that all units weighing between 0.55 pounds and 50 pounds must be registered by February 19th, 2016. Anyone against this rule and caught flying will face still penalties and be even in jail for years.
DJI's latest drone- Phantom 3 has faced an crisis because it's overweight. FAA has bitterly confounded DJI's ambition. The cold winner for DJI is coming. Currently DJI has held 60% market share in the U.S. FAA adds up to a one - two punch that would stagger DJI.
FAA's new regulation will be effective on Dec. 21st and almost covers all the consumer drone on the market. All the drones weighing between 0.55 lbs and 50 lbs must be registered on FAA's official website. It's a nightmare for most of the drones like DJI. FAA offers unique registration number to approved submitters and those drone owners are required to paste or paint their own numbers on their drone.
FAA has the 0.55 pounds regulation because administration thought it's the bottleneck that drone companies would not breakthrough. To make a drone weighting under 226g is nearly possible.
But Onagofly surprised us with advanced drone technology from China. The Intelligent Onagofly drone is not only featured by its sophisticated performance moreover Onagofly has lowered its weight to the crazy 140g-nearly 0.3 lbs.
In this case FAA's newest regulation become invalid to Onagofly at the first moment it's coming out.
Onagofly is the most popular drone crowdfunding project since the day it launched on Indiegogo:https://www.indiegogo.com/projects/onagofly-the-smart-nano-drone--2
Offical Website: www.onagofly.com
Media Contact: Sam Tsu, Onagofly, 86-755-83284880, [email protected]
News distributed by PR Newswire iReach: https://ireach.prnewswire.com
Photo - http://photos.prnewswire.com/prnh/20151221/317547
« Last post by Shadowcry on January 16, 2016, 03:56:56 PM »
« Last post by Josh97 on January 12, 2016, 12:48:30 PM »
"""ROBOTIX 2016 | KSHITIJ | IIT KHARAGPUR
Technology Robotix Society
presents ROBOTIX 2016, its annual technological extravaganza, to be
held during 21st - 24th January, 2016 as a part of Kshitij, the annual
Techno-Management Fest of IIT Kharagpur.
Official website - www.robotix.in
To participate register at www.ktj.in
SUMMIT- To build a manually controlled robot capable of climbing stairs whilst picking, storing and placing objects on its way. www.robotix.in/event/summit/
WAREHOUSE- To build a gesture controlled semi-autonomous robot that is
capable of storing blocks on multi-layered platforms according to their
RFID tags. www.robotix.in/event/warehouse/
SHERLOCK- To build an autonomous robot that can follow compass headings
to go from start to finish via minimum waypoints using IR receiver to
receive arena and waypoint information. www.robotix.in/event/sherlock/
S.H.E.L.D.O.N.- To build an Image Processing robot capable of detecting
characters, using an overhead camera and traversing them such that the
equation generated by the traversal fulfills a certain condition. www.robotix.in/event/sheldon/
DROID BLITZ- To build a remote controlled electric-powered robot that
can be used to complete broken pathways and transfer packages by running
on land as well as water. www.robotix.in/event/droidblitz/
PS: There is no abstract submission for the above mentioned events.
Visit our website, www.robotix.in
for details of our events, tutorials and other general resources on
robotics and to stay updated on developments. If you have any query just
post them on discussion forum of respective event!"""
« Last post by peek-a-boo on January 11, 2016, 01:28:54 PM »
I'm thinking of building self balancing robot. (Thinking of using encoders to measure the distance covered)
My first question is, should I go for servo motor or Brushless DC motor?
The robot should be able to traverse on smooth surface, carpeted surface and surface inclined at 10 degrees angle.
How do I calculate the required rpm and torque of the motor?
« Last post by fxgovers on January 10, 2016, 01:07:32 PM »
OK, I found a solution. I went into the bootloader source code - the size of the code to be downloaded into the Axon 2 was arbitrarly set at 10,000. I reset it to 64,000 and everything is working fine. I'll have to keep an eye on the build size, but my code is now working fine.
« Last post by FIFO on January 09, 2016, 03:51:04 PM »
When the robot powers up, the robot will by default drive in reverse. I have been trying to load a small program that would write to an I/O port that would cause the robot to stop, however, so far I have been unsuccessful.
The first things I thought of when I could not get the robot to work was that the programmer might not be functioning correctly. I then removed the I/O chip and attached LEDs to the address/data buss, address latch pin, and the write pin and confirmed that the programmer was functioning properly.
The 8085 CPU has a 16 bit address and a 8 bit data bus that is internally multiplexed with the lower 8 bits of the address bus. The two most significant bits of the address bus are decoded to select one of three 8155 I/O and RAM chips. The next problem I suspected was that the decoder was not wired properly, and that the 8155 chip that I was trying to write to, was not being enabled. After examining the decoder, I noticed that I had wired it incorrectly (it turns out that the mistake was due to a typo in the book). I then corrected the mistake and tried to reprogram the robot. I also confirmed that the motor drivers, that the 8155 interfaces with, were functional.
The robot was still running in reverse, so I then suspected that the code I was loading into the robot was incorrect. After reading the data sheet for the 8155 and reading the book more closely, I realized that the code was indeed wrong, so I fixed the code and reprogrammed the robot.
The robot was still running backwards, so I wondered if the code was not being executed because the non-maskable external interrupt, TRAP, was being triggered, and causing the CPU to jump to the ISR. I then measured the voltage on the TRAP pin, and confirmed that it was not causing an interrupt.
I then suspected that voltage rail was below the minimum level for the 8085 and the 8155s. I checked the data sheets and found that while the voltage was a bit low, it was well within the 10% tolerance required by the chips.
The next thing that I thought might be the problem was that I did not have any decoupling caps on the 8085 and the 8155s. I then added 0.1uF decoupling caps to those chips, but still the robot drove in reverse.
I am running out of theories as to what the problem might be caused by, however I still have one idea. I purchased the 8085 CPU new, however the 8155's were used. Their leads are clipped short, and there are traces of solder left on them. I am now wondering if the 8155s are in fact functional, or that maybe I damaged 8085 when I was constructing the robot. The next thing I will be looking into is a way to test the chips.
I have included top and bottom pictures of the main board below.
« Last post by mklrobo on January 09, 2016, 08:26:12 AM »
I wish I could help, but I can not even get the program to load into the Axon!
In programming respect, though, the compiler may not be optimizing your code.
I do know that there are other compilers and bootloaders from Atmel, which may help.
I have links on my post, Analyzing the Axon: Coding, Construction, and Contraptions that
may lead you to an answer. Good Luck!