Re: pic: SPARK
 

Does it overheat more than previous motor controllers?

Re: pic: SPARK
 

Re: pic: SPARK
 

We are considering ordering these. Our team programs in C++. Is there anything different needed programming wise to use this type of motor controller as opposed to a talon.

Re: pic: SPARK
 

Talon SR? No. Talon SRX? Yes.

Also same to program (basically) as Victor 888, Victor SP, or PWM Jaguar.

Re: pic: SPARK
 

Which version? (Talon, Talon SR, Talon SRX)

Re: pic: SPARK
 

We were thinking if the spark was similar programming as the talon, and talonSR

Re: pic: SPARK
 

Now when robot parts will be in Lowe's/Home Depot/Menards Stores nation-wide :P Would make it easier to fix stuff during outreach events if it breaks :P (hey, those handy HVAC duct clips worked magic for a temporary fix for a weld that came undone in the middle of a day-long outreach event :D

Re: pic: SPARK
 

I do not see any where in that document where they talk about temperatures of the various controllers. However I'm also unaware of any controllers currently on the market that will overheat when utilized correctly.

Re: pic: SPARK
 

That is a concern for the new mindsensors controller. The graphs they released were...let's say warranting further investigation. I have yet to see third party results on how well they work and whether we should be concerned about overheating, especially with the Rev B version being released so recently.

Re: pic: SPARK
 

Programming the SPARK is identical to the talon and talon SR.

Re: pic: SPARK
 

plz help we bought 2 sparks and there unresponsive and wildly sending low voltage plz help its causing alot of problems it would be greatly appreciated

Re: pic: SPARK
 

Have you contacted anyone? I think calling whomever you bought the motors from and informing them of the difficulties you're currently having would be a good idea. If you've already done that, might I ask what you've done so far with the motors? Are you stressing them?

Re: pic: SPARK
 

Hi Jarrett,
I sent this to you in an email also, but if you could tell us a bit more information we will be able to help figure out the problem.

• What programming language are you using?
• Are you using the included PWM cables, or other ones that your team had previously?
• Have you tried calibrating the controllers or doing a reset?
• Does the issue happen as soon as the power is turned on or only after the robot is enabled in the driver's station?
  

Please also check that power and motor connections. If motor and power connections were swapped, motors could spin uncontrollably regardless of the robot state.

If you send us a photo of your electronics setup, it might be easier to diagnosis the problem. Also if you would prefer, we can talk you through it over the phone.
You can reply to the email I sent you or send me a private message here on Chiefdelphi.


Thanks,

Greg

Re: pic: SPARK
 

The fact that you have two Sparks exhibiting this behavior makes me suspicious that something else could be in the mix. Does it exhibit this same behavior with another speed controller? If a Victor/Talon/Jaguar/etc exhibits the same behavior wired the same way, then definitely email REV.

It's possible that a couple duds escaped any testing they're doing, but for a team to go 0 for 2 on semi-random pulls (we'll assume there's a degree of randomness with Amazon's fulfillment network that picked and packed your Sparks) would surprise me.

(Full disclosure: REV donated four Sparks and a Digit board to Team Cockamamie's Robot in 3 Days build this year, and Greg and I have known each other for some time. I'd say the same thing about any brand of speed controller, though.)

Re: pic: SPARK
 

If I were going to venture a guess based on the limited information in the initial post, I'd say they have their PWM wire or their power wires plugged in backwards. My only complaint about the spark was that the white molded "B" to signify the black wire on the PWM connection didn't jump out at me when I was looking for it. I had the same complaint on the old victors too.