Jump to content

Bo Fu

  • Posts

  • Joined

  • Last visited

Bo Fu's Achievements


Newbie (1/14)



  1. Thanks to hoovahh's suggestion and I used his Low-Level VI Manipulation Hooovahh Edit.zip in the other post. It allowed me to convert the VI to XML. But now the tricky bit, it looks difficult for me to retrieve the names of the nodes and VIs from the XML file. I don't know if there is a 'dictionary' somewhere to explain the fields in the XML file. All I need to know is which kind of subVI/node (e.g. DAQmx Timing, add, Enqueue Element) there are in the target VI and how they are connected. I tried to compare the XML files every step when I made a change in the target VI. But I failed to find the ID to stand for the type of the VI and node. So is there any way to 'extract' this information from the XML file? Thanks for your help. Regards, Bo
  2. Hi Yair and hooovahh, Thank you for your suggestions. Yair, if the buffer only tells us as the edit menu, I don't think that's enough information for me. Alternatively, I would like to try the VI --> XML method and it seems more flexible for further development. hooovahh, thanks for the link. I will have a read of that. Thank both of you very much! Cheers, Bo
  3. Hi all, I am trying to get the history of the commands in LabVIEW for my hobby project and didn't work it out. So what I want to do is to keep a record of the functions (could be VIs, nodes, constant, control and indicators...) that I placed on the block diagram when I am doing the LabVIEW coding. For example, if I do "5 + 8 = ?" function, the history it generated may be something like: -- Placed "Add" node -- Created Constant 1 -- Set Constant 1 to '5' (not required) -- Created Constant 2 -- Set Constant 2 to '8' (not required) -- Created indicator Is there any way I can access to this information? I think it may have something to do with the buffer file that stores the undo/redo commands. But I don't know how I can see that information. Any thought? Thank you for any input! Cheers. Regards, Bo
  4. Bo Fu

    LabVIEW Comic

    Hey, Yair FYI: Steve said:" Nobody knows how to program with 'multiple core'." and Bill:"All the S/W nowadays have to deal with the 'parellel' problem." Regards, Bo
  5. is about to move forward to FPGA module

  6. Hi all, I'm using lv 8.5 in winXP, and I'm doing a DAQ task. I created a synchronized AI/DO task, and wanted to have it run for a long time (for hours@1M Hz). I'll change the DO commonds based on some feedback, and acquire the corresponding AI signals. I have 2 options to do that with my NI m-series DAQ card. In "Do not allow regeneration mode", I know when the updating happens, and I can handle the CORRESPONDING AI, but I have to keep writing to the FIFO for hours, which may harm the hardware (in my thought); or I can use "Allow regeneration mode", because the updating does not have to be fast, as long as I know which is its corresponding AI (when DO updating happens). So is there any way to know the time of updating in allow regeneration mode? or is there any better idea to implement the updating? Thank you! Best wishes, Bo
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.