I have met something with using Moku GO with Labview. I have entered IP address, which I have used same address well in Python. However, in Labview, it report Error message code 54. I am not sure how to solve this problem.
Hi @Sushiki
Thank you for posting. The Moku connection failure is likely due to the fact that LabVIEW doesn’t support an IPv6 address. May I ask how you connected Moku to a PC, i.e. WiFi / Ethernet / USB? If via WiFi or Ethernet, you can find the IPv4 address under the corresponding tab of Device settings, as shown in the screenshot. In the case of USB, as USB requires the use of IPv6 to function properly, you would need to set up a proxy port to convert the IPv6 address into a IPv4 format. The instructions can be found via this link: https://knowledge.liquidinstruments.com/moku-labview-api-support-over-usb.
Please kindly let me know how this goes. Thank you!
Best regards,
Le
Dear Wang,
Thank you for your assistance. What I use is USB, and I have convert IPv6 to IPv4 according to the instructions. However, the labview also cannot work, and it report Error message 42. Here I show the screenshot. If you could help me solve this problem, it would be really helpful. Thank you for your help.
Dear Sushiki,
Thank you for sharing the feedback. I tried the Moku:Go Oscilloscope LabVIEW example on my side with USB connection, and I couldn’t reproduce this error message. Could I trouble you to check on a few things?
(1) Did you modify any sub-VIs in this example, especially the ‘Get_Data.vi’? If so, could you please share the updated .vi file so that I can try running it on my side?
(2) Could you quickly try other examples and see if they report the same error?
Thank you very much!
Dear Wang,
Hello. Thank you for your help. I have checked other examples however, it also has such problem. I have made no change on these sub-VIs. I would like to ask how to solve it. Thank you for your help.
Dear @Sushiki ,
Thank you for testing other examples and sharing your feedback. The error code 54 and its associated message suggest an invalid IP address. Could you kindly check if the IPv6 address has changed since a few months ago or if the localhost port has been overwritten? If so, re-running the configuration of the port proxy might resolve the issue.
As a quick follow-up, is error code 42 still appearing?
For your information, we have recently released a firmware and software upgrade, along with updated API packages. The LabVIEW driver package 3.3.1 is now available on our website if needed.
Thanks,
Le
Dear WANG
Thank you for your help. I have solved it.
Hello @LeWang
I am having a similar issue but I am using a moku go device that is connected through the wifi. I have tried finding my IPv4 format address but when I look under device settings, it says my address is 0.0.0.0 .
All the best,
Alex
Hi Alex @tu108,
May I quickly confirm whether you connected to your Moku:Go via the hotspot it broadcasts or through your institutional WiFi network (with your Moku:Go also on this network)? Were you able to successfully access and use the device in the Moku app?
Thanks,
Le
Hello @LeWang ,
I am connected to the Wi-Fi through an Ethernet cable and have connected to the Moku Go through its local hotspot. I am able to access the Moku through the Moku app.
Alex
Hi Alex @tu108,
Thank you for confirming the Moku:Go connection approach. When connected via Moku:Go’s hotspot, the static IP address is 192.168.73.1, which can be used in LabVIEW to access Moku. Could you give it a quick try and see if it works?
Thanks,
Le
Hello LeWang,
I have used that IP address but now I am getting error 502
REST Client.lvlib:REST Client.lvclass:Error Handler.vi
HTTP error: Bad Gateway
The moku device says there is no API device installed. I have downloaded version 3.3.1.5 from the VIPM program.
Alex
Hello Alex @tu108,
It seems that the API server not being installed is likely the root cause. You can follow the steps in this Knowledge Base article to update the API server. Could you also quickly confirm your Moku is running firmware 600, which is compatible with VI package 3.3.1.5?
Thanks,
Le
Hello LeWang,
That worked.
Alex