I thought I would go over some FAQ that I get regarding our legacy PCI and ISA slot computers. Feel free to add to this and I'll be happy to try to address some of your questions!
1. Are these computers new?
YES! These are manufactured by NIXSYS and we build to order. All new components are installed and we use our own NIXSYS motherboards with PCI slots and ISA slots. The hard drives, optical drives, RAM and all other components are new. This means that you're getting a quality system you can depend on for years to come.
2. How do I know it will work for me?
We can't guarantee functionality in all cases, there's simply too many variables to consider. But if you speak with us and explain your unique situation, we're usually able to provide a recommendation that ensures you're getting the functionality you need. In almost all cases, we're able to make sure you're able to pull our machine out of the box, load your software onto it, and get working.
3. I dont have my original software to load onto the new machine, what can I do?
This can be tricky in many cases and it's typically dependent on the OS you're using. We can offer a service in some cases where we charge to migrate your data over, the costs on this can vary by the situation. Sometimes, a cloned image of the old machine's hard drive can be used. Sometimes, individual file structures need to be copied over into appropriate directories. Other times, a download of that software version you're using is still available. Where there's a will, there's a way.
4. Where are you located?
Our entire operation is located in Irvine, California. We are 100% US based.
5. What is the return policy?
While it rarely happens, we do have a 30 day return policy. Unless there's been damage to the machine, we typically only withold the shipping costs from your refund.
6. How long have you been in business?
We've been in business for 13 years.
7. Do you offer discounts?
Normally we don't. In some cases where we get inquiries for a high quantity we can offer a volume discount but it's heavily dependent on the configuration and individual circumstances.
8. How long does it take to get one of these?
Most machines will ship in 3 business days or less. Special configurations or multiple machines can take 3-5 business days.
9. Do you ship overseas?
Absolutely. We have shipped all over the world and we're very flexible in working with our international clients due to the different import/export laws and regulations in individual countries. We are very knowledgable in navigating these waters.
10. Why would I buy from you?
Everything we're selling is new and carries our warranty. You're not buying a refurbished system that's been someone else's headache for 15 years. We are an American business with experience in assiting customers with legacy computing needs. We realize the value of a solid relationship with our clients and that's the core of our business.
11. What does the warranty cover?
The warranty covers all hardware we install. Installing your own hardware does not void the warranty as we've designed these systems to be open for ISA slot and PCI slot cards and other add-on hardware.
I know I said way back when that ideas are cheap until someone puts the work in. here
My gift to you (mostly NI, Alliance Partners, Entrepreneurs and customers), is an idea I've put some work and risk into. It is an also an idea I'm enthusiastic about.
The image above came from my NIWeek 2016 presentation on Shock Testing and was intended to describe the standard way organizations purchase large expensive distributed systems. Essentially you have 2 choices.
1. Purchase a turnkey system
2. Do it yourself (DIY)
Over a certain price range and system complexity the risk of DIY becomes potentially career limiting. From what I have observed it becomes harder for DIY vendors (like a certain Texas based company) to sell these systems over a certain price point. So if for example the system consists of some PXI racks full of cards and the alternative supplier offers software or even just screens and a USB slot, the "full" system will always win. I've stuck "full" in quotes because the purchaser will always settle for 80% of their required functionality. As an example for the system I have developed I've had over 5 enquiries and each time they want it exactly the same (but with a few changes).
To add insult to injury from what I have seen, the hardware purchased is inferior and lots of compromises are made on the software.
Looking at the image again you can see that the turnkey system is controlled by the vendor and in my experience they are not that responsive to change requests and are quite prescriptive when making changes and removing support. Also they are prone to takeover and business refocusing.
In short the DIY vendor finds themselves at a considerable disadvantage, but actually the turnkey vendor is not providing a good solution either.
The ideal situation is that the hardware comes with software that is easily adaptable using an industry standard language, this software could be loaded from the language vendors app store. I'm talking LabVIEW and the tools network here for anyone still struggling to keep up.
I can't believe that my system is the only example here (Singleshot High Channel Count Oscilloscope). So what else? I dunno, RF, Spectral Analysis, we're looking at any large distributed system, synchronized readings, high value hardware, replacing existing bespoke distributed electronics. Thinking caps on people.
I thought long and hard about the licensing because in the traditional world there is a value to this code, my conclusion is that I'm not a salesman and my assumption is that customers will want changes and who better to do the these changes than the designers (talking high value business here in customer accounts that you would normally struggle to get access to). When you are in these large accounts you will find extra work, we always have. Also I would never get into the companies I'm talking to without this, I probably wouldn't even get into the carpark!
So a standard BSD license, with liability restrictions.
Freeing up this bottleneck will also help your relationship with the hardware supplier, essentially your software is the enabler for selling their hardware. This improved relationship is mutually very beneficial.
This is a matter of trust, you are throwing your code to the world and trusting everyone to do the right thing. In the real world there should be little incentive for any of the parties to do anything but help each other. Obviously small mindedness, short term thinking and profiteering could cause issues. For me the worst bit is feeling disconnected from the code.
So far the experience has been really excellent. Our method has transferred to remote working.
In truth tho' it's actually not that much of a problem if you can get over the initial hurdle of being paid for development. In my case a long term relationship with an existing customer mitigated the risk of tackling the project.
What can NI (or another hardware vendor for that matter) do to mitigate the risk? They can have decent amounts of high value equipment available and maybe there is even a business case to provide a grant to pay for or contribute to the development. They will then need to resist the temptation to OWN the code, open-sourcing it will be better for everyone believe me.
A Different Type of Sales
You might be thinking that because I espouse ideas in writing and with some force that they are well thought through. This particular idea is pretty much me trying to make sense of it by writing about it (I'd say a fair few of the things I write about fall into this category!). So here goes.
I think some of the sales and marketing that alliance members/consultants and integrators do is misplaced (mostly this is aimed at SSDC). The last two large opportunities that we have successfully pursued have been where we have had something to sell, rather than where we have tried selling ourselves. In someways I think this is also more useful/profitable than selling toolkits etc into the LabVIEW community. So we are changing our model to one where we sell ourselves to solve any problem, to where we have a solution and can adapt it quickly and efficiently.
Why Open Source?
Most systems integrators are more problem solver than entrepreneur. We negotiate a price to design some code and then we design it, for us we nearly always offer up the source code to the customer. Our experience so far is that the customer is keen to engage with us at the "Trusted Advisor"* level and it's a nice start to a relationship. Also they are freaked out by someone giving something away! This fits the Open Source model much closer than other models I've looked into.
I think this is an enormous opportunity for NI and system integrators. We just need to identify the gaps in the market.
Lots of Love
* for more on "Trusted Advisor" see my comedy skit at CERN, where all is explained.
Hai Semua, saya Muhammad Septyawan dari Sekolah Tinggi Teknologi Nuklir - Badan Tenaga Nuklir Nasional. sedikit ingin share. myRIO Surveillance Wheeled Robot (mySweet) adalah sebuah robot beroda yang menggunakan NI myRIO-1900 dari National Instrument sebagai controllernya. Robot ini bisa bergerak maju, mundur dan berbelok. selain itu, robot ini dilenkapi dengan camera sebagai fungsi pengawasan. Sehingga robot ini bisa dikontrol secara wireless dan melakukan streaming video ke komputer. Project ini merupakan bagian dari project selama 1 bulan Internship di National Instrument Indonesia.
myRIO Surveillance Wheeled Robot Video
Alat dan Bahan :
myRIO-1900 (AQUILA - belongs to Suryo-sensei)
Tamiya Dunny 4WD Chassis with DC motor Mabuchi 540SH and Servo HS540
USB Camera Logitech C525 720HD (Belongs to Mbak Gaby)
EMS 30A Motor Driver
EMS 3A adjustable regulator
Jumper Cables + power switch
Karet gelang ???
Membuat robot beroda yang memiliki kebebasan bergerak maju,mundur dan berbelok. memiliki kemapuan pengawasan yaitu mengambil citra bergerak untuk dikirimkan dan ditampilkan serta dapat di tonton ulang.
karena menggunakan chassis tamiya, maka separuh pengerjaan hardware sudah selesai. dari chassis tersebut, dilengkapi CD motor Mabuchi 540SH. motor ini cukup powerfull, kuat, mudah digunakan namun cukup menyedot arus yang besar (dan mahal ) karena itu untuk mengontrol motor ini, digunakan PWM yang diumpan ke Motor Driver untuk mendrive kecepatan motor. disini digunakan pin C/PWM0 myRIO untuk mengontrol kecepatan motor. kemudian untuk mengatur arah putar motor, digunakan logika driver melalui pin C/DIO1 dan C/DIO2 myRIO melalui driver motor juga. sedikit nge-betak juga. But It works so no problem
kemudian, untuk mengatur robot untuk berbelok, digunakan servo HS540. servo ini cukup (mahal)mudah diperoleh dan diprogram. saya gunakan pin C/PWM1 untuk mengontrol servo. karena robot ini merupakan tipe mobil robot propotional, maka perubahan arah dari robot sebanding dengan simpangan servo. untuk kamera, digunakan port USB.
terakhir untuk hardware adalah penataan tempat komponen dan wiring.
Penampakan Depan. kind of mess, but I proud of it. heheh
untuk software, terdapat 2 VI. satu running di Host dan satu running di myRIO. untuk VI yang running di Host, terdapat 2 loop utama. yang pertama adalah loop control yang berfungsi membaca perintah arah dari keyboard dan kontrol kecepatan. loop kedua untuk downstream image yang dikirim myRIO melalui TCP/IP kemudian ditampilkan. selain itu image disimpan dalam bentuk .avi sehingga dapat dilihat ulang.
untuk VI yang running di myRIO, terdapat 2 loop utama juga. loop pertama untuk membaca kontrol dari Host dan menerjemahkan menjadi gerakan robot. untuk pengakses I/O dimyRIO, menggunakan low level. pengkondisian nilai PWM untuk kecepatan motor dan arah servo dicari berdasarkan uji coba.loop kedua adalah untuk image upstream untuk mengirim image melalui TCP/IP.
gini, saya masih punya sdikit masalah dengan tugas saya kemarin, skrng masalahny perintah yg saya kirimkan dri labview kearduino sepertinya tidak ditanggapi arduino dengan baik...
sekarang pertnyanx: bagaimana cara perintah arduino untuk membaca angka 1 dan 0 dari labview... 1 jika High/ON (tegangan 5V arduino aktif dan 0V/GND nonaktif) dan 0 jika Low/OFF (tegangan 0V atau GND arduinony yg aktif dan 5V nonaktif)...
saya rasa masalahny ada diprogram arduinonya.... tpi gk ada salahny klw saya sertakan juga progrm labviewx brang kali masih ada kekeliruan....
trimakasih saya ucapkan sbelumnya...
semoga kwan2, abang2 atau adek2 semua dapat membantu....