Hello CD Forum members,
I was wondered if it would be possible to save data to the flash memory, to use it like between matches or things like that (when the robot is off)
if it is possible i would like to know how and would be extra happy if ill get some of you to guide\assist me.
About Encoders, Ive wired all up, and it still doesn’t read info from it, i think the code is good, because its really basic (only things like OPEN, CLOSE GET bla bla…)
The encoder does infact generate is light.
Its wired like this(i dont remember the line color BUT I DO know what every color is):
srcA: contain 1 cable to +5v, and 1 cable signle in DIO 13 on the sidecar
srcB: contain 1 cable Ground (-), and 1 cable signle in DIO 14 on the sidecar
I would like to thanks to every help, any help would be really appreciated by me and my team Thunder-Bolts
GREAT THANKS ,2630 THUNDER-BOLTS, Emek Hefer, Programing TEAM.
And i Nimrod Beker (sorry for too long thread)
Go ahead and post the relevant part of the code so we can verify what you think. It would help us to help you better.
Nimrod,
I’m not qualified to answer your file I/O question other than to say that I know it is supported in Labview.
Regarding encoders, I would suggest that you watch the video tutorial labeled “LabVIEW Encoder Example” on this page and see if it answers your questions.
Good Luck,
Mike
Wow great thanks Alan and Mike!
Soon ill post the relevant code…
Wow great thanks both of you again!! first i didnt even thought my code is bad but Alan you was correct!!!
Ive fixed it all up and i read fail-free data from the encoders.
But again i need help with data saving to the flash, Im joining to Ori request
from my team.
Please, any help about how to do it with LabVIEW programming would be appreciate and blessed!!!
Nimrod Beker, 2630 Thunder-Bolts, Programming TEAM
The palette icon looks like a blue floppy disk. There are functions to open the file, write using text or binary, and functions to close. Use a path control to specify where the file should be placed.
For the first run or two, set a breakpoint on the file Open and either use exec hilighting (light bulb) or probes to check for returned errors from the file I/O functions.
Greg McKaskle