I tried installing the sensors on the EDU and test them out, but the coding doesn’t seem to be working
this is what i have:
if c_sensor1=1 then c_p1_y=1
what’s wrong with this code if it keeps telling me that it expects a label
:ahh:
I tried installing the sensors on the EDU and test them out, but the coding doesn’t seem to be working
this is what i have:
if c_sensor1=1 then c_p1_y=1
what’s wrong with this code if it keeps telling me that it expects a label
:ahh:
try using just ‘sensor1’ and ‘p1_y’
And also, it seems like you’re trying to make the robot go forward when the sensor is active. Since p1_y is a analogue input/output, it goes from 0 to 254 (note: a common mistake for rookies - including us last year - is thinking that PWM outputs go up to 255. Although TECHNICALLY right (analogue-wise), it’s a, uh, how do I put this… bright flashing red lights<b>bad</b> thing to output that). Anyways, if you’re outputing p1_y to a PWM port, make it equal to 254.
*Originally posted by Fares *
**I tried installing the sensors on the EDU and test them out, but the coding doesn’t seem to be workingthis is what i have:
if c_sensor1=1 then c_p1_y=1
what’s wrong with this code if it keeps telling me that it expects a label
:ahh: **
A couple of problems: Both c_sensor1 and c_p1_y are CONSTANTS used in initialization to set up communications with the master microprocessor. You’re not going to be able to SET c_p1_y. You should use if sensor1=1 then p1_y=1 as SuperDanman suggested.
Also, since you are using PBASIC v2.5 syntax (if … then … statement) rather than v2.0 (if … then … label), you need to enable 2.5 syntax by including a '{$PBASIC 2.5} directive. (If 2.5 syntax had been enabled, the error message would have said: “Expected a label, variable, or instruction” instead of “Expected a label”.)