Using ADO toolkit on fieldpoint?

[nellli]

Hello,

I used the ADO toolkit to connect to a MySQL Server, select some data and for now the data is shown in an array on the front panel.

Everything is working fine so far on my Windows PC.

I would like to have the program run on a fieldpoint module and I guess there is an issue within the ADOTool_ADO API.vi.

This vi uses "Automation Open" which comes from the ActiveX palette and I think the Fieldpoint doesn't know anything

about ActiveX.

Is there any way to connect to a MySQL Server from a fieldpoint module?

Could the ActiveX-part be replaced by something?

I am using LabVIEW 8.5.1 with RealTime 8.5.1 and Fieldpoint 6.03.

Thank you in advance.

nellli

[rolfk · Accepted solution]

---

nellli wrote:

Hello,

I used the ADO toolkit to connect to a MySQL Server, select some data and for now the data is shown in an array on the front panel.

Everything is working fine so far on my Windows PC.

I would like to have the program run on a fieldpoint module and I guess there is an issue within the ADOTool_ADO API.vi.

This vi uses "Automation Open" which comes from the ActiveX palette and I think the Fieldpoint doesn't know anything

about ActiveX.

Is there any way to connect to a MySQL Server from a fieldpoint module?

Could the ActiveX-part be replaced by something?

I am using LabVIEW 8.5.1 with RealTime 8.5.1 and Fieldpoint 6.03.

Thank you in advance.

nellli

---

Well, ActiveX is certainly out of the question. ODBC in fact too, so the only way that could MAYBE work is to take the actual MySQL native client library, and recompile it for the Fieldpoint device. I assume you are using cFieldpoint devices, which have a PPC CPU and run VxWorks. Depending on the LabVIEW version you use you will have to use either the VxWorks 6.1 (LV 8.2) or 6.3 (LV 8.5 and 8.6) development toolchain and create an according .out shared library. Then you can create VIs using the shared library node and interface to that shared library, although you must obviously also create a compatible shared library (DLL) for your development platform to be able to do the actual development of the VIs. All in all an interesting but very tricky solution requiring rather specialistic knowledge.

And although I like to do this kind of work I would actually not do the SQL connection from the Fieldpoint directly but instead pass the data to some host system and put it into the DB from there.

Rolf Kalbermatter

[nellli]

Dear Rolf,

In fact I am using the Fieldpoint (without 'c' in the beginning), which is the previous version of cFP.

Your idea which could maybe work seems to be theoretical feasible, but

---

All in all an interesting but very tricky solution requiring rather specialistic knowledge.

---

that was the key sentence for me to keep my fingers away from that 🙂

---

And although I like to do this kind of work I would actually not do the SQL connection from the Fieldpoint directly but instead pass the data to some host system and put it into the DB from there.

---

This is a solution for me. I will think about this way to get the data in the database and rewrite my program. 

Another advantage comes along with this way. I can save space on my Fieldpoint because I don't need the ADO libraries there anymore.

Thanks a lot for your helpful answer!

nellli

[rolfk]

---

nellli wrote:

Dear Rolf,

In fact I am using the Fieldpoint (without 'c' in the beginning), which is the previous version of cFP.

---

I'm not sure at all what CPU is contained in the traditional Ethernet Fieldpoint controller. It is certainly at least as slow as the slowest compact Fieldpoint module and as such ActiveX would be also impossible because of processing power too, but even without, ActiveX is only executable on Windows and Windows alone (well there is Wine which attempts to be a better Windows, but it is not something you would ever want to do on a RT system anyhow).

Rolf Kalbermatter