LabVIEW dashboard for Duet 2 Wifi

amit.bandarwad

Hello,

I am looking to build a LabVIEW dashboard for Duet 2 Wifi controller board. I was wondering if there are any LabVIEW or .NET DLL libraries available. If not, can you please let me know how to go about it?

Regards,
Amit

Veti

not sure if there is labview integration.

but you can query the duet via http calls

see this for example
https://github.com/DanalEstes/DuetPython/blob/master/getCoordsDemo.py

amit.bandarwad

@Veti yes, Thank you. I think it is feasible to make http calls to duet board using through the LabVIEW.
Also, I am interested to know if .NET DLL libraries are available or can be provided by the Duet 3D, that can be called through the LabVIEW.

Apologies for the very late reply.

Regards,
Amit

T3P3Tony

@amit-bandarwad we do not have .NET dll libraries to query a Duet.

mendenmh

LabVIEW does have a quite complete HTTP integration library that comes with it. It should be entirely trivial to make requests and send commands to the Duet.

amit.bandarwad

@mendenmh yes, I have just a look in to the LabVIEW HTTP library. Will get some hands on experience on them before deciding on the integration.
Also, I think there is always USB serial communication as a fall back option for interfacing with LabVIEW.
What are your thoughts on the of HTTP vs USB LabVIEW interface?

Regards,
Amit

amit.bandarwad

@T3P3Tony Is it the case for all the Duet boards?

Regards,
Amit

Veti

@amit-bandarwad said in LabVIEW dashboard for Duet 2 Wifi:

What are your thoughts on the of HTTP vs USB LabVIEW interface?

keep this in mind.
https://duet3d.dozuki.com/Wiki/USB_ground_loops

http query would be much simpler

amit.bandarwad

@Veti Sure, Thank you.

mendenmh

@amit-bandarwad I would go HTTP; you already have the network available, avoid extra wires, and (as mentioned elsewhere) ground loops. There is also a lot better handling of non-determinism in HTTP (well, in TCP really) that makes such communications very reliable. Communications hiccups are 'someone else's problem' in that they are handled by the TCP stack. USB/Serial you have to make sure you never get any surprises, such as cable jiggles causing disconnects, or extra characters due to diagnostic messages, etc. The HTTP protocol guarantees exactly what to expect.

amit.bandarwad

@mendenmh Thanks you very much for your input. Appreciate that.

Regards,
Amit