PJM_labview

I think you can't debug a CIN while LabVIEW is running. Note: I am not 100% sure PJM

Jimi, Did you try my suggestion to uncheck allow debugging in the reentrant VI(s) that prevent your project from opening? Did it had any effect? PJM

Just a quick comment.In most situation, trying to save money on hardware not compatible with LabVIEW will most likely end up costing you money for the time spend to do the driver development and testing. PJM

While changing the menu or text ring to embed the string info will be good for my LV usage, I can see why this could potentially create problems in other people existing code.The reason why I was using the ring constant was to create a sparse enum, so if we had the ability to have enum with non sequential string this would cover most of the use case (if not all) I may have for using a menu/text ring constant. PJM

Jimi,I think this particular issue is due to the debugging capabilities of reentrant VI in LV 8.x. I have seen it many time both in LV8.0x and 8.2 (although less in LV8.2) and this was happening only when I was debugging a reentrant VI. I think you may be able to alleviate the issue by unchecking allow debugging of the culprit reentrant VI. Note: I have not checked whether this work or not. PJM

This is a good trick. Thanks PJM

Editing a strict type def ring does update controls or indicators instances but does not update constant instances. This is a severe bug in my opinion, as it make using ring text constant unusable on block diagram (since for every edit you have to fix all of your constants instances. You loose the entire benefit of the typedefness [is this a word?]). See example below that demonstrate the bug. Download File:post-121-1163454674.zip PJM Edit: Apparently this may not be a bug but an expected behavior. I knew there was a reason why I though that I should never use either text or menu Ring.

Cool info Ben. The insert>bundle by name or insert>bundle is working as expected now. Nice :thumbup: Too bad that while they were at it, they did not fix the insert>unbundle by name or insert>unbundle. But this is nice that NI is finaly working on the insert menu (and it need a lot of work). PJM

I though it was part of the LabVIEW DSC package, but I may be wrong.PJM

See this post

The separator are not displayed properly when the right click is done over a pane (see images). This is a bug present in both LV 8.0 and 8.2. Note: See attached VI for a demnostration of the bug. Download File:post-121-1163364438.vi CAR # for this bug is: # 43CGK1U4 PJM

Just a side note, the correct name is Tour Eiffel (or Eiffel Tower for the English speakers) named after the engineer Gustave Eiffel. PJM

I'll give you a clue PJM

This is cool! :thumbup: PJM

As we all know, we can run a VI by clicking the run arrow button , Ctrl+R, the stepping arrows buttons or finally the run continously button . I just found out that in LV 8.2 there is another way to directly run the stepping arrows buttons using a keyboard shortcut. There is a direct mapping between CTRL + Direction Keys (Ctrl+down, Ctrl+up and Ctrl+right) and (the stepping arrows buttons). This is pretty cool :thumbup: Note: too bad the Ctrl + Back does not reverse the execution! PJM

This is an interesting methaphor. I never though about it that way before. I like it! PJM

Time to change bank then... Joke apart, I used to buy a fair amount of stuff online (chemical, materials, hardware...), and whenever I add issue accesssing a vendor webpage, my reasoning was the following: If the vendor webpage did not work well with the browser I was using (whatever it may be) then they dont want my business, therefore I will buy from the competition that has a web page compatible with my browser. PJM

Stephen,Look at the date on the post; this was in december 2004. I can't see that far in the futur yet PJM

Hi Does any of you guys happen to have a driver for Sanyo Denki motors (more specifically PB series). This motor is controlled over RS232. I have the manual[pdf] and I am ready to start writing the driver, I just dont want to re-invent the wheel, unless I have to . Thanks PJM

Hmm,The last benchmark I run were either on LV 7.0 or LV 7.1. At the time I consistantly got better result (not by much though, I think it was in the order of a couple %) using the explicit coercion. It is possible that the implicit coercion has been improved in subsequent LV version. PJM

Ed, I believe I post a LV8.0 version somewhere here on the forum (I dont have time right now to locate it) that does not suffer from this issue. For some reason the LV 7.1 version crash because of an enum (this is very odd). PJM

I think we need to see a screenshot of your code. Eventhough you provide a detailed explanation it is hard to say what is happening. PJM

It has been my experience that explicit coercion does improve performance.PJM

I don’t believe there is any way to access the profiler programmatically. I think it is somehow part of the LV resources and it is not accessible to us.PJM

I think an externalNode (XNode) will be better for that, because, as you modify the connector pane of the parent, the connector pane of the child (the recursive call subVI) should modify itself as well.Edit: Another benefit is that you would not even need to create a SubVI in your project folder. The code would be right there behind the XNode. PJM