Calorified
-
Posts
38 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Gallery
Everything posted by Calorified
-
Your write-up is insightful and "royally" entertaining at the same time, @MeAndVan! This is the highlight of my morning so far. Keep it up!
-
RT @kdnuggets: Happy #MoleDay! October 23rd is the day we celebrate #Avogadro's number, 6.02 x 10^23. https://t.co/tPuD3ztoUh
-
Incredible. "How Mark Zuckerberg, Bill Gates and Elon Musk stay productive http://t.co/yQhNfWbtUc via @TIMEBusiness"
-
Fuckin' implementation of a stochastic kalman gain. http://t.co/dS8FAr9IQw. NI, this is not how to write code,sheesh! Bug cost me 1 wk.
-
Answer on @Quora by Jeff Nelson to What advice can you give to someone that isn't afraid of failing, but wasting ti… http://t.co/mrMa3phqe3
-
Sleep comes easily when he hears my heartbeat. Super /emoticons/default_smile.png" alt=":)" />http://t.co/M2IKloTwNS
-
My @Quora answer to Is it accurate to use noise as input to characterize a water system with an ARMAX model? https://t.co/wjrjhbfjQR
-
Each day is God's gift. It's the reward for the hard work you do in life. Eat, dress, look your best. Laugh. Life is short.
-
Turns out my intuition was right. The discrete KF vi will not accommodate higher-order stochastic state space systems. I confirmed this through the LaVIEW PSC engineers yesterday. If anyone is thinking of a big state space structure as I was, the easy way out might be to build your own KF application.
-
It's a bit lame but what I ended up doing was to receive the multicast on the Windows Virtual box, create a second ordinary udp broadcast to the RIO and receive the udp broadcast on RIO. Still no noticeable delay. Someone in my lab told me I could have used a shared variable engine to move the data around from my PC to RIO target. I tried this unsuccessfully with the 'Single-Process Shared Variable' as well as 'NI-PSP Shared Variable'. Maybe if someone has a way out, they could further shed some light on the shared variable host send and target receive.
-
Hello there, I tried to implement the discrete time Kalman filter in a closed loop estimator scenario based on the "CDEx LQG with Linear Simulation" example located in `C:\Program Files (x86)\National Instruments\LabVIEW 2015\examples\Control and Simulation\Control Design\State-Space Synthesis` that ships with LabVIEW. Only difference is my application is a 4 x 4 state matrix. The thing is the kalman filter output, \( y(t)(k|k) \) and output estimate, \( \hat{y}(k|k)\) do not get updated. My vi.png is here: I know it says somewhere on the help pages that the KF vi needs a second-order process components. But does this mean the vi would not work with higher order systems? Would appreciate your input.
-
I quote from here : "This will add the static route for all packets arriving from the possible UDP multicast address range (224.0.0.0 through 239.255.255.255). To make the changes persist through rebooting the device, you can either write a script to run this command on device initialization or manually add the rule to the network interface configuration file in /etc/network/interface." Why do you say it won't work for an address that starts with 235?
-
You meant this: route add -net 224.0.0.0 netmask 240.0.0.0 dev eth0 ?
-
Hi there, I have RIO in a Windows VirtualBox inside a Ubunbtu Host OS. I am sending data from a C++ program in the Ubuntu Host system to labview within the Guest OS. I can receive the data on labview installed on the windows guest os. Below is the png of the Windows working program. But when I tried to send the data to myRIO, I was getting a udp read only error 42. Somewhere on the NI forums, someone suggested the net address of the "UDP Multicast Read-Only" vi be wired to the address of the RIO which I have done below . Now, the code runs on myRIO but I can't receive any data on RIO. The multicast address I am sending to from Boost Asio C++ is 235.255.0.1 on port 30001. The RIO has a public ip of 172.22.11.2 and I set up a static ip address for it in NI MAX as the address of the UDP Multicast : "235.255.0.1. At this moment, I do not see what I am missing. All firewalls have been disabled and I have set the permissions for RIO through the Windows security page. Any help would be appreciated. Thank you!
-
glad my contribution is proudly featured on the libfreenect2 github webpage...a small step for a dawg ... :-)
-
This is my face with the Kinect for Windows v2 Infrared Camera Sensor (=awkward) http://t.co/MlGGkVuHpF
