
Originally Posted by
Ioannis
I do not see why you should leave PBP and start another similar language and your project all over again.
I wouldn't normally suggest it, as PBP can do just about anything. But here is why I think it might be a good idea in this case.
Configs are confusing for adults, I would hate to frustrate middle school students. This would keep them from having to worry about those.
PBP kind of expects you to read and understand the data sheet. StickOS would just require them to get read the device pinout. They could just start with the data sheets for their sensors, and not be overwhelmed by a 200 to 500 page data sheet.
They would not have to worry about setting ADCONx, trisx, cmconx etc...
With StickOS, they can just say:
Code:
10 dim pot as pin an5 for analog input
20 print "potentiometer= ",pot
Now here is some PBP code that does a similar function:
Code:
Define ADC_BITS 10 ' Set number of bits in result
Define ADC_CLOCK 3 ' Set clock source (3=rc)
Define ADC_SAMPLEUS 50 ' Set sampling time in uS
adval Var Word ' Create adval to store result
TRISA = %11111111 ' Set PORTA to all input
ADCON1 = %10000010 ' Set PORTA analog and right justify result
mainloop:
ADCIN 0, adval ' Read channel 0 to adval
serout2 PORTC.6,396,["Value: ",DEC adval,13,10] ' Display value
Pause 100 ' Wait .1 second
Goto mainloop ' Do it forever
End
And pretty high up there in my opinion is the cost. I know the school my son goes to has trouble buying pencils and paper. They would pretty much need everything donated to be able to do it. I think Ken said the cars were $80, this CpuStick is about $40. The PBP software is $250. So the cost per unit is $120 with StickOS vs $370 for PBP. That's over three times the cost. So, for the same cost of having 30 students share 10 PBP units (one kid does the work, while the other two watch), they could have one for each kid in the class.
Bookmarks