Feedback on NI Community
Congratulations Dennis Knutson!
Way to go Dennis!
Looking at chilly charly's recent compilation, you are also still the top poster with 4.4 posts/day for the last 15 days. At that rate, the gap to us mere mortals will be ever increasing!
Impressive any way you look at it. We've learned a lot from you. Thanks!
🙂 I hope NI sends you at least a T-shirt for the occcasion! 🙂
Looking at chilly charly's recent compilation, you are also still the top poster with 4.4 posts/day for the last 15 days. At that rate, the gap to us mere mortals will be ever increasing!
Impressive any way you look at it. We've learned a lot from you. Thanks!
🙂 I hope NI sends you at least a T-shirt for the occcasion! 🙂
Impressive!!!
Let me propose your new goal: 10,000 posts by 2007
- With 9 posts a day you will even be able to afford a few holidays...
Seriously, you are our hero here at NI. We are honored by your amazing support to the community.
Hail to the King!
Let me propose your new goal: 10,000 posts by 2007
- With 9 posts a day you will even be able to afford a few holidays...
Seriously, you are our hero here at NI. We are honored by your amazing support to the community.
Hail to the King!
I have a weird problem with a DK4000 macrocontroller. (see the technical info here ).
Seems that it can’t be programmed reliably with LabVIEW. Each time I upload a new program, the memory content changes for something else a few seconds later.
The funny thing is that the modified program is still working, but has switched to a different task, doing something completely different.
I found out that sending an ascii string composed of a series of $2A chars (5 is optimal) can maintain a stable state for a few minutes, but not more.
After spending six months on this problem, it seems that LabVIEW is the cause of all the trouble. Probably some nasty bug with the serial communication vis.
I have attached a simplified vi to illustrate the problem. Sorry for the mess in the diagram, but that’s the result of the patch work I have been obliged to do to track the problem.
Does somebody know if the recently released new generation DK5000 still exibit this strange behaviour ?
CC
Seems that it can’t be programmed reliably with LabVIEW. Each time I upload a new program, the memory content changes for something else a few seconds later.
The funny thing is that the modified program is still working, but has switched to a different task, doing something completely different.
I found out that sending an ascii string composed of a series of $2A chars (5 is optimal) can maintain a stable state for a few minutes, but not more.
After spending six months on this problem, it seems that LabVIEW is the cause of all the trouble. Probably some nasty bug with the serial communication vis.
I have attached a simplified vi to illustrate the problem. Sorry for the mess in the diagram, but that’s the result of the patch work I have been obliged to do to track the problem.
Does somebody know if the recently released new generation DK5000 still exibit this strange behaviour ?
CC
