Jump to content

germ

Members
  • Content Count

    21
  • Joined

  • Last visited

Community Reputation

0

About germ

  • Rank
    Active

LabVIEW Information

  • Version
    LabVIEW 2009
  • Since
    1998

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The ViewPoint TSVN toolkit does not work with the latest 1.9.x version of Tortoise SVN client. I have emailed ViewPoint but have not gotten a reply yet.
  2. Can you share how you set this up? Is it a setting in Tortoise SVN? Yes, I did notice that. Thanks.
  3. Hello, sorry to start a new thread on this, but my searches turned out posts that are mostly outdated or relate to SCC tools other than SVN. So, we have decided to use SVN as our SCC platform. I have setup a VisualSVN server on our Windows 2012 Server and Tortoise SVN client on the developer machines. This is working quite nicely at the file level, but I wonder if we can get more functionality, especially VI comparison. We are using the latest LV 2015 Full Development System (not Professional Development system). So I understand that I cannot use the lvdiff tool. I have however setup LVcompare as a tool for .vi files in the SVN Advanced Setup. I found two SVN tools for LV: 1. JKI TortoiseSVN Tool. This has a somewhat steep price at $200 per developer (10% discount from 5 seats) 2. TSVN Toolkit from Viewpoint Systems. This is free. However, it states that the latest version supported is LV 2014. I am interested in the experience from other users regarding: Q1. Which of the two tools, if any, do you find useful and why? Q2. Does TSVN Toolkit work with LV 2015? Q3. Any other tips/suggestions for effectively using LV with SVN? Your opinion and help is much appreciated. Thanks in advance. --germ
  4. Final update: It works now. It must have been the terminator character, which was enabled when the device does not expect any.
  5. Update: I now have it working....on another computer. And of course it is possible to open the VISA Configure Serial Port VI, sorry for having missed that. Either: The Terminator character was set incorrectly (to LF while the device expects none) or: An additional USB hub or two on the other computer prevented this from working. I will be able to check only later this week. One question I still have: This device can use one or two characters termination, but the VISA serial seems to only accept one. How would I set it up to use CR/LF? Is this possible?
  6. OK, I will try to open it today. No freeze. The VI works, but after issuing the same command there is no further reply from the device (zero "bytes at port"). The VISA Read then times out if I use the Advanced Serial example. The funny thing is that this used to work correctly about a year ago.... so yes, I am sending the right commands. Regarding the termination character, according to the device documentation, it is set to "no termination character". The software included with the device should allow to change that, but it appears not to work. That is, if I change the "End of reply" character, it doesn't stick when I exit that software.
  7. Well, that's a basic VISA VI. Can't open it. Took another stab at it today. Didn't have much time, and didn't get any further. I noticed that the example VIs have both a Basic and Advanced serial port. The Advanced wires the Terminator character, but then has a loop that tries to read the serial port many times. Anyway, it all only works the FIRST time I run a simple command. After that, everything is locked when I send the same command. No "bytes at the port".
  8. Thanks Yair...but what's "top to bottom"? The terminals are arranged around all edges of the Configure Serial Port VI icon. There's no "top to bottom" order that I can discern. Anyway, it seems that arg8 is the Termination character, which I set to ASCII 13. I will experiment here and report on the solution. Since the native software that came with the device CAN communicate just fine, it means the serial port is working.
  9. I have previously written an LV program to communicate with a US Digital QSB-D encoder (http://www.usdigital.com/products/interfaces/pc/usb/qsb) via a virtual COM port accessed through USB. The computer has a newly isntalled C: drive. After re-installing LV (2009 SP1) I got the "Hardware resource not available" error. Re-installing NI-VISA got rid of that error. However, my previous program does not work. I get the following error when calling the "VISA Configure Serial Port (instr).vi": code -1073807194, "property note (arg 8) in VISA Configure Serial Port (Instr).vi->...". How can I find out what's "arg 8"? There's no clear sort order to the arguments of that VI that I can see. Anyhow, the device can be setup to output CR, LF, or nothing as the "end of response" character. It is currently setup to "nothing". If I use the "Simple serial communication" example, in which, infuriatingly, the "terminator" character terminal is NOT connected and the "user terminator character" is hard-wired to False, then the error happens ONCE, but when I try again I can issue and read a command ONCE. After that, communication is blocked (no data are returned when issuing the same command). There is some software that comes with the device, but it seems to reset the device to the above-mentioned state on quitting (very annoying). Any suggestions before I go back for another day of fiddling with serial ports? Thanks.
  10. germ

    RS-422 encoder counter

    jdunham, thanks for your reply. I am aware of the $$ NI option. Now we have bought those: Counter to USB converter Hopefully they will work....
  11. germ

    RS-422 encoder counter

    Well, yes, but I also explained (obviously not clearly enough) my situation. Sorry, but the documentation that comes with the positioner clearly states RS-422. No idea what you are talking about. Hmmm....a PIC.....what is that? Maybe this? http://en.wikipedia....microcontroller I am asking for a finished solution, a box that I can buy. Not a chip or something where I have to spend a month building something around it...
  12. germ

    RS-422 encoder counter

    ShaunR, those are serial interface cards. It is not clear to me that they will work for my purpose: The encoder emits quadrature pulses through the serial interface, but I need a COUNTER to read the position, then poll it from the PC. I don't think a simple serial interface card will do this.
  13. Hello, I have an optical position encoder (actually three of them, one for each axis) that transmits electric signals according to RS-422 standard. There are two quadrature channels (A and B) and a reference/stop channel. How to read this in LabVIEW? There is an expensive NI solution: the NI cFP-QUAD-510 4-Axis, Quadrature Encoder Input Module for Compact FieldPoint. This also requires a chassis and LabVIEW RT, which we don't have. Seems like overkill to me. There are third-party multi-axis RS422 counters with, say, an USB interface like this one: http://accesio.com/go.cgi?p=../usb/usb-ctr-15.html Unfortunately this one won't work, because it can't read quadrature signals. Actually having an added display would be nice. So what I am looking for is a box which accepts 3 or 4 RS-422 inputs and has a display for the counter and a USB, Ethernet, or serial interface from where I can get my position. Any suggestions?
  14. I was able to implement what I wanted using Mark's suggestion: An array of clusters, each cluster containing a 2D array. Because the arrays involved are small, this generates a nice, readable TSV file, which can be edited by a human if needed. Because the arrays in the clusters are of variable size, I use a delimiter line ("[Ch1A1]"), etc. to mark the end of the array. Writing the settings file is straightforward using the "Convert 2D array to spreadsheet text" and "Write text to file" functions. For reading I wrote a small VI that parses the lines containing the array of clusters by looking for those delimiters. As others pointed out, this works only if your settings/ini file is small. And any change to the global variables will necessitate a change to the VIs for saving and reading the settings file. For large, complex files, XML is probably a better solution.
  15. Mark, thanks a lot for your reply. I saw the XML Vis. I think this would work, but it is overkill. I only want the user to be able to take a peek at the configuration file, perhaps edit a couple of numbers by hand on occasion. A (small) 2D array is actually nicely human-readable in a text file. Thanks for this pointer. I will take a close look at those VIs. This is useful as well. IIUC, by using an array of clusters, each containing a 2D array (instead of a cluster of 2D arrays) I gain an easy way to process the individual 2D arrays.
×
×
  • Create New...

Important Information

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