http://decibel.ni.com/content/community/first
reading the folder displayed at 3:56 min of the video…
I think one of the folders reads “asynchronous start” , “asynchronous stop”
as well i see the standard “autonomous” as well as “tele operated”
any thoughts why we might need an asynchronous program?? apparently (from what I hear) the new controller can communicate with other robots…
thoughts… speculation??
Mr Yeagle
TEAM 2229
I suspect that these were test files to make sure everything was running smoothly, but i could be wrong.
I have plenty of ideas how we could use asynchronous programs. Bear in mind that labVIEW is inherently “multi-threaded”, and therefore asynchronous is easy. Also, VxWorks gives us multithreading capability.
Tasks that do not need to be synchronous to each other can now easily be split up and handled separately. For example, the compressor runs asynchronous to the joystick/drive base. If you have a vision based turret, this can now run completely separate from the drive base.
Perhaps those are the VIs that help launch separate tasks?
Not sure, just speculatin`.
Doesn’t asynchronous start/stop just mean that response to the command is immediate and cannot be delayed by other operations?
Seems like that would be an absolute requirement for an emergency stop feature.
These elements will start and stop a task that then runs asynchronously or independently from the rest of the program. There are definitely uses for this, but I will wait till the code comes out to reveal the rest.
Greg McKaskle