![]() |
Re: TI and future Jaguars
Quote:
Are we designing an electronic motor controller or are we discussing the finer points of why forums for Internet communication have issues yet to be resolved? It's not like I personally am the reason that Newton's Telecommunication Dictionary has 25+ editions and so many pages of often cryptic and slang terms. In fact I never even saw a copy of Newton's Telecommunication Dictionary until some college professor started looking for clever word games to play. It's also not like other people didn't basically figure it out in subsequent posts. |
Re: TI and future Jaguars
If I can't understand what you are talking about, a lot of folks won't be able to follow it.
|
Re: TI and future Jaguars
Quote:
So if they are lost and not following the topic (and everyone is probably lost now or soon will be because of the side-track): 1. It's not interesting enough to them to take the time to ask about something. 2. They are worried about distracting the topic as this has. 3. They are intimidated that if they ask the question or make an error they'll get themselves attacked. I've made every effort to explain myself even when I'm wrong. When I am wrong I apologize generally. However, once that is out of the way it doesn't seem to stop there. So yes, I do see why someone might feel that participation might have negative results. It's nothing personal to anyone. It's a very valid concern. It's like being incredibly sensitive about grammar. Acceptable grammar changes with time. So what might be correct in one English standard today, in about 5 years might be entirely unacceptable. So do we not communicate because we might offend the resident grammar expert? No. We do our best. Then once the result is formal writing we insure the utmost accuracy. I can't even say that TI managed that formal documentation process with the Jaguar responsibly. The documentation for the Jaguar has both grammatical and factual engineering errors. I see no apology or official attempt to correct from them. It's an electronic document...they don't even feel the need to fix that. It's somewhat hypocritical to put so much effort into worrying about brief brilliant communication when the official documentation for the product that started all this can't even communicate the proper operation of it's own H-Bridge and TI didn't think it important to fix that. More importantly how bizarre is it that whenever Ether or other members who know about this error tell someone to read that section of the manual they have to post a warning that section is wrong. How handy really. So for all the rest of the students out there that don't happen to have the benefit of that disclaimer how much time do they get to waste trying to figure out or worse memorize that error? How much damage can that officially sanctioned document from TI do before someone finally demands it be fixed? Read the manual sort of implies that effort was made to produce a proper manual to take as gospel. |
Re: TI and future Jaguars
Well as a software guy, who understands little about the intricacies of motor controllers, I understood exactly what Brain meant regarding in band vrs out of band messaging. Of course, all of the discussions on mosfets and other things leave me bewildered.
At the end of the day, we all want the same thing for the teams. A motor controller that provides lots of flexibility with regards to command and control, and high reliability. TI bought the IP for the Jaguars, and the product was really just a way to demo the chip. Not to really sell motor controllers, so I was not surprised when I heard that they didn't want to continue to support it for FIRST. I'm a bit concerned about the ability to manufacture in quantity a motor controller without getting a someone with deep pockets to cover the losses/expenses. Maybe sparkfun might be interested in such a project. They could in theory resell to other hobbyist. I really like the module design, and as an embedded software guy would be more than willing to help on a ROTS/Firmware development project. But I suspect that the timeframe would be at least 12 - 18 months out. |
Re: TI and future Jaguars
Quote:
I think after we sell 50 to 100 which I can finance we'll be in a much stronger position to justify further expense. I can bank roll this that far. Then we can shop it around like LinxuBoy is doing with his CAN terminators and see who wants to help. It's a hard sell right now. Some people will be skeptical of the ability of anyone to make the project. Some people are in serious financial trouble. Some people will place terms on this project that might not fit a project of this nature. SparkFun or other sources are certainly welcome to take from the project and manufacture so far as I'm concerned as long as they give credit where it's due. Quote:
I'm okay with funding this well into next year and further if it gets to production. I'd rather ship a really well designed product than something we slammed together just to cross the finish line. If somehow FIRST finds a supply source of the Jaguar in the meantime, good for them it just takes more pressure off this project (I'll still fund it). |
Re: TI and future Jaguars
Quote:
[quote]It's not clear to me how you would be able to benefit from inputs on the PWM version. I suppose you could use them to provide basic limit switches. However, generally PWM is an output from the existing control system and an input into the electronic motor control. You'd need to come up with some way to configure the electronic motor control to get more elaborate when using PWM. With CAN I can see having optional input and output modules would add more flexibility.[quote] One idea is to have a potentiometer input to recreate the function of an RC servo, but with whatever motor, transmission, and range of motion you want. Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
I believe that the minimum system should be reduced down to the common H-bridge and a basic processor module. if the team then wants to upgrade then they shouldn't need to buy a new processor. Things like high-speed counters (due to cost) and CAN bus interfaces (due to size) should be add-ons. More advanced users could buy more advanced processors to get systems that exceed Jaguar capabilities, but most of what a Jaguar can do should be possible by adding onto the basic processor module and all of what a Victor can do should be possible with out any add-on parts (beyond the minimum system). |
Re: TI and future Jaguars
Quote:
Maybe we could outfit the PWM module with a simple serial interface that can be set up once and left that way? Quote:
I suppose instead of really, really tall headers which would be hard to come buy one could use belt cable or PCBs with typical 0.1" headers. However, in either case passing up the sides of the module would block the side intake of airflow leaving access on only 2 sides. Quote:
However, if you put them physically above the MOSFETs which could disipate 80W-100W of heat under the right circumstances as the heat rises it'll basically cook the chip. In fact in a really bad circumstance I can see how the rising heat might start to reflow the solder paste and since most higher end microcontrollers are surface mount they won't have the mechanical lock that through-hole parts get from the pads their leads pass through. Quote:
Obviously mica insulators for these transistor packages are made, it just adds to the base cost of manufacture. Also it's unlikely that we can avoid the fan even with the heatsink. If we put the entire unit in a plastic box we'll need to move the heat out of that enclosure somehow. One solution is put the heatsinks outside the enclosure, but then the transistor leads need to pass through the enclosure walls which makes inspection disassembly more difficult (adding connectors to those wires is possible but just adds more cost and points of failure). Quote:
Quote:
Quote:
|
Re: TI and future Jaguars
Seems to me that there are two problems here.
1. small package high amp pwm controller (aka victor) basic fault detection and over current limit voltage control rather than straight pw as victor wdt other robot markets 2. added features can, ic2, encoders, software, control algorithms. possible USB interface for broader appeal Can the basic small package be built cheap, durable, and flexible enough to add the second set of features at a resonable cost |
Re: TI and future Jaguars
Quote:
Anything more complicated like CAN, I2C, encoders, A/D, control algorithms, USB...all that adds costs like fancy 32bit processors and microcontrollers. In small quantities these things will drive up the costs over $100. Hard to get around it. I'm not worried about the foot print or the durability. Hitting it with a big hammer will both make it smaller and test for durability. ;) That said I figure that teams would be willing to pay a little more for electronic motor controls if they work, if they are supported, and if they are reliable (course we have to prove that point by a show of endurance and that will take time). If the initial units are received well it'll be much easier to get additional investment to drive down the costs. So I'm not indicating these units will always be more expensive than the current selections. We just have to walk before we run. |
Re: TI and future Jaguars
Ok, I'll chip in some capital if we can make this work.
When will we hear (if at all) about the responses to the RFP . if no commercial entity bids for this , I'll consider co-investing in our own. Dean |
Re: TI and future Jaguars
Do you guys know what you are committing to? For just the KOP and enough to fill Spare Parts you are looking at almost 10,000 units before teams start to buy extras.
|
Re: TI and future Jaguars
Quote:
However, according to my contacts at FIRST KOP we can get something approved by September when the documents are finalized and then, because we don't wish to put it in the KOP, we just have to make production volume for those that buy when they find out it's approved in January. If we did put it in the KOP we'd need production volume by October. As stated I'm willing to provide boot strap resources to get working near production ready prototypes, and produce 50-100 of whatever FIRST ends up approving. More if people actually gobble those up. If we can't make the deadlines for this year I'm perfectly fine putting resources into this into next year. Additionally between the monitoring equipment I am working on right now for the power supplies on the robot, the websites, I've already poured $3,000 of mine into this (never mind the $4,000 I spent already messing around on my own outside of resources sent to Team 11 for projects over the last 2 years). Besides 10,000 units is really trivial. With the resources involved if push really came to shove I could probably easily make 50,000 units a year if there was demand to buy it and the schedules weren't ruinous. |
Re: TI and future Jaguars
I think we need to wait for the RFP results.
Brian: do you know from your FIRST contact when that will be? I think IFI may be the only bidder. And if so, I don't see how an open-source solution can compete. The best we may be able to achieve is to keep IFI under pressure not to make too much profit from FIRST. Dean |
Re: TI and future Jaguars
Quote:
I am guessing you don't know the history of IFI and First. You don't need to worry about this. |
Re: TI and future Jaguars
Quote:
After looking back over the thread, it appears to me that Brian is talking about a completely separate proposal from the "future Jaguar" RFP that I though the discussion was about. That difference in assumptions will likely have led me to make comments that aren't quite applicable to what he has in mind. Brian, if that's the case, it would have avoided a lot of confusion if you had split your project ideas into a separate thread instead of filling this one with them. |
| All times are GMT -5. The time now is 00:50. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi