|
Re: Vex Programming Question
Quote:
Originally Posted by Kingofl337
easyC 1.x never had any code to monitor the transmitter. The problem you were having was probably using "PWM Control".
Found inside the "RC Control" pallet Instead of a motor block. PWM was in a loop with the controller functions so it may have acted oddly without the controller turned on. This was later eliminated in V2 and later versions of easyC.
Also, V5 is the correct master code version to use with easyC 1.x
|
OK - let's notice that I didn't say that EacyC 1.X monitored the transmitter.
I said that the transmitter had to be turned on before some programs (at least one) written using 1.X could work.
And I think you just agreed with me.
Acting "oddly", in my case, meant sitting there like a lump, cycling through my infinite loop just fine; but not issuing any useful (useful to me) commands to the PWM outputs, until the transmitter was turned on. It was a very frustrating night (and morning).
If I remember correctly the PWMControl documentation did not mention any situations in which one might expect odd behavior.
Blake
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
Last edited by gblake : 02-05-2007 at 19:02.
|