Jump to content

ASTDan

Members
  • Posts

    360
  • Joined

  • Last visited

  • Days Won

    6

Posts posted by ASTDan

  1. I would recomend a State machine archture over a sequence structure. In LabVIEW when you select New go to State Machine template. You can also type in State Machine on NI's website to find some good info on this versitile archtecure.

    sorry for my bad spelling its late

    Dan

    QUOTE(pjsaczek @ Sep 13 2007, 08:48 AM)

    thanks alot for all the help! it's working now.... ending with <CR> worked on hyperterminal, but in labview I needed to add the Cariage_Return to the end of the strings I was writing........ rookie error!

    now i'm just wondering how to arrange my program. it has to basicaly start the machine running, then take readings of the force etc, then stop the machine. I'm thinking sequence structures are the way to go?

    cheers again,

    pete

  2. Here is is in 7.1

    Let me know if that helps

    QUOTE(pjsaczek @ Sep 11 2007, 09:28 AM)

    cheers, but i'm on version 7 or 7.1. any chance you could send it in one of those versions?

    the help is much apreciated!!

  3. Try Concatating a cariage return on the output text as shown. Sorry for my terriable spelling.

    QUOTE(pjsaczek @ Sep 10 2007, 11:52 AM)

    thanks alot, in the instructions it says the command has to be ended with <CR>. so for example, for it to read off the current position of the tester, and the force on the load cell, type RB<CR>. is the basic serial VI putting some more characters on the end? or do I need to add something to the end?cheers, pete oh, and the instrument doesn't do handshaking cheers!
  4. Hello,

    Have you tried this example that ships with LabVIEW, see attached.

    Make sure you COM settings are correct (i.e. baud rate etc) .

    I would also verfy you don't need to pull up one of the handshaking lines this would be found in your instrument documentation.

    If your device is not seeing your commands try a different carrage return constant after the text you want to send. I notice in the example I posted a carriage return is not concatenated after the text. Sometimes the instrument nees a carrage return to recognize the commands. LabVIEW has end of line, carrage return, and line feed constant. Sometimes it doesn't matter what you put to send text. Sometimes your instrument will only recognize one. For example end of line works, plain carrage return doesn't.

    In general that is all I can help with right now. If you could post your code that might help.

    Thanks

    Dan

  5. Hello,

    I have a question/comment. I am trying to find a master .pdf document for DAQmx. The request I had was for a 300+ page manual for DAQmx. Does something like that exist? I found a "getting started with DAQ" http://zone.ni.com/devzone/cda/tut/p/id/5434 on NI's website. It looked cool. Is there 1 pdf manual that has everything, or is the documentation all in help files or on line?

    My comment is where is NI headed in regards to documentation? I feel NI's documentation in general is good but could be better. Sometimes when reseaching something I wish they had more detail. Are they moving away from detailed manuals? Is documenation just chunks of html posts and the era of an all encompasing manuals over?

    I am interested to hear other people's comments.

    Thanks

    Dan

  6. Hello,

    That is how the power supply should work. I have worked with those before. If the current is 0 the voltage will be 0 Ohms law. The power supply can control to Voltage or current. If you want to control to voltage set the current to higher than you need, and set the voltage. The power supply will output the voltage you want. The current will be a function of whatever load you have on the power supply. If you have 0 resistance on the powe supply you will have infinite current. If you have infinite resistance on the power supply you will have 0 current.

    Hope that helps

    Dan

  7. You might want to take a look at Open G's varient configuraiton files.

    www.openg.org

    It takes Clusters or arrays and saves them as .ini files.

    I would also sugest taking a look at the .tdm file fromat from NI. It uses an XML header with a binary file.

    Hope this helps

    Dan

  8. I have a supid question.

    I have created some control templates of my common control clusters I use as type defs. This is really cool! This should save me time and I am a happy labview programmer. However how do I load these now? When I go to File\New all my vi templates are there, but not my control templates.

    How do I load in my custom control templates? Is saving them in the template directory a good idea?

    What am I to do?

    Thanks

    Dan

  9. The applications I have been looking at have been very simple. I have had a couple that I just needed to control a 2 axis stage using a servo motor. I just needed to go to a position. Path was not a factor.

    I had another application where they needed to control Torque which was just controlling the current. Again very simple applicaiton. The drive had digital inputs for home and out of limit contitions.

    So from what I gather simple motion applicaitons can be handled with an intelligent drive. Where as a complex motion you are better off with the NI Motion control card.

    Is that a fair statement?

    Dan

    On a releated note.

    What is a good reference for motion control? I ordered the Motion control Cource Kit from NI. Is there another resource? I am looking for a good book or article.

    Thanks

    Dan

  10. Hello,

    I have been quoting on a motion control job and I wanted to ask a question regarding NI's Motion control boards.

    What are the pro's/con's of using a NI Motion control boad over an intelligent motor drive. An intelligent motor drive you can send commands via the serial port or control the position,velocity,or torque using an analog output. The drives I have seen you can set the PID parameters and also store moves to be called using RS232. So with all that functionality what does using a NI motion board get you?

    Thanks

    Dan

×
×
  • Create New...

Important Information

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