Jump to content

alukindo

Members
  • Posts

    113
  • Joined

  • Last visited

Everything posted by alukindo

  1. Jaegen: Thanks for your insightful suggestion. I tried your suggestion and determined that a new plot, however small, will be affected by the same problem as long as it is located beyond the position where grid lines disapear. I called NI today and they think that it is bug in LabVIEW which should be fixed. ... I will confirm this tomorrow.
  2. It seems that plot area size has a maximum size beyond which the grid lines stop appearing: ----E.g: if you make an X-Y plot up to 50000 units in height, the horizontal grid lines will disappear at some point when you scroll to near the bootom of the chart. ----Does anyone know if this has a fix? I need these long charts because I end-up printing the front panel as a strip chart for a lithology profile.
  3. I think that deleting the LabVIEW ini file would have done it. I was able to recover from this by un-installing LabVIEW 8.2 and then deleting the entire LabVIEW 8.2 folder, and then re-installing LabVIEW 8.2 Note that uni-installing LabVIEW via Windows>>Control Panel>>Add-Remove programs and then re-installing LabVIEW did not work! Thank you Ton and Jimi for replying to my post!
  4. After I made corrections to a user.lib VI, the functions palette has disappeared when invoked via Tools>Advanced>Edit Palettes. Has anyone come across this and knows of a fix? ... I repaired and unistalled/re-installled LabVIEW but this did not resolve the problem.
  5. Hi Jeff: I am having the same problem when re-connecting to a TCPIP server using my custom TCPIP client-server VIs. The error manifests as error 42 on the server-side, while it reads as error 64 on the client side. It only happens on the 10th-or-so reconnect. It is repeatable and can be easily reproduced. At present, I am trying to work around it by maintaining the connection open. I use regular polling to ensure that either side of the connection is alive. This particular application needs to run reliably & 'forever' on a real-time PXI system. Otheriwse, were you able to find any other solutions to this problem? Thanks Anthony L
  6. Does anyone know how a timed loop can be stopped and re-started? I know about the method to create a timer and then destroying it, and then doing the same on re-start of the loop. However, if I put that timed loop inside a regular loop (for re-start) my other code in the same VI stops running. Infact, even when I put a case structure around a timed loop the other regular loops stop running. . . . Could this be a bug in LabVIEW? Thanks for any help Anthony L.
  7. Thanks for input on this anomaly. Actually the echo happens whithout any cable being present on the Comm Port. This is why users think that the cable connection is fine and everything while in-fact they are not even connected. I can find a way to filter the polling characters, but if I can turn echo off then I would go for that Thanks again Athony
  8. Hi: Is there a way to hold back a Serial COM Port from echoing back characters written to it? Can this be done from within LabVIEW? I have this LabVIEW application which must poll a COM Port to get back data. However, the polling characters get echoed back giving the impression that the other system is talking back --while in-fact this is not the case. Thanks for any help Anthony
  9. Yes, the 'ViewDistance' property did the trick! Thanks much! Now: I only wish I could smoothen the axes label fonts and flip them by 180 deg. Otherwise all is set! Anthony
  10. Hi: Regarding the LV 3-D plot, when hiding all planes and leaving say the X-Y plane only, and then viewing it from the top, the plot area covers less than 60% of the plot area size. Is there a way to increase the size of the X-Y plot to cover more of this object's overall plot area. In other words, the 3D plot leaves alot of white space when viewed in 2-D mode. Is there a way to re-size it so as to recover the white space? Anthony
×
×
  • Create New...

Important Information

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