Labview control of Roboard RB-100 PWM Channels
by goofylogic98
Wed Nov 04, 2009 5:41 pm
Thanks for the help. I know have the stuff working. Now another simple (i hope question).
I know that in the init rcservo.vi, if the noservo value is 24 and the channels is FFFFFFFF then all 24 PWM Pins are active for PWM signals and the GPIO (rcservo outp.vi) does not work. I also have tested setting the noservo value to 1 and the channels to 1 and I have PWM control on PWM Pin 1 and GPIO control on pins 2 through 24. My question is how do I set it up so that pins 1, 5, 20 are PWM pins and the rest GPIO.
I know that in the init rcservo.vi, if the noservo value is 24 and the channels is FFFFFFFF then all 24 PWM Pins are active for PWM signals and the GPIO (rcservo outp.vi) does not work. I also have tested setting the noservo value to 1 and the channels to 1 and I have PWM control on PWM Pin 1 and GPIO control on pins 2 through 24. My question is how do I set it up so that pins 1, 5, 20 are PWM pins and the rest GPIO.
by ries
Wed Nov 04, 2009 8:15 pm
unused channels are GPIO.
a sample with rcservo_outp is included.
I think you better can reserve the lower channels for PWM and the rest as GPIO.
in the example channels 0-15 are for PWM and 16-23 for GPIO.
You question with pin 1,5,20 is possible but not convenient for programming since the rcservo_setservo is driven by a for loop.
take a look at the sample, maybe it explains it to you.
http://robosavvy.com/Builders/ries/pwm+outp%20sample.zip
Regards,
Ries
a sample with rcservo_outp is included.
I think you better can reserve the lower channels for PWM and the rest as GPIO.
in the example channels 0-15 are for PWM and 16-23 for GPIO.
You question with pin 1,5,20 is possible but not convenient for programming since the rcservo_setservo is driven by a for loop.
take a look at the sample, maybe it explains it to you.
http://robosavvy.com/Builders/ries/pwm+outp%20sample.zip
Regards,
Ries
by roboard
Sat Apr 30, 2011 3:32 pm
To ries,
information for the issue of using adc_ReadMCH() in LabVIEW: adc_ReadMCH() returns a pointer (int*) to an integer array and isn't suited for use in LabVIEW. Instead of adc_ReadMCH(), one should call adc_ReadMCH2() in LabVIEW. (adc_ReadMCH2() is declared by "void adc_ReadMCH2(int* buf)", where buf is an int[8] array for receiving the A/D value of every channel.)
information for the issue of using adc_ReadMCH() in LabVIEW: adc_ReadMCH() returns a pointer (int*) to an integer array and isn't suited for use in LabVIEW. Instead of adc_ReadMCH(), one should call adc_ReadMCH2() in LabVIEW. (adc_ReadMCH2() is declared by "void adc_ReadMCH2(int* buf)", where buf is an int[8] array for receiving the A/D value of every channel.)
by Yequan
Wed Jun 15, 2011 8:53 am
Error that, roboio.dll ERRMSG is generated into a buffer. With six roboio_GetErrMsg.vi you can get the coach shoes errors / warnings generated....