Search

Forum


ArtNet connectivity checklist
You are not authorized to post a reply.
Basic Member
Posts:10 Basic Member

--
2014-11-18 11:15

Hi,

For some reason, Capture Argo is returning an ipAddress of 0.0.0.0 in the NodeDiscovery reply packet, and NodeStyle is null.

This is when the Artnet ipAddress (In tools->Connectivity) is set to Automatic.

When I set the ipAddress to my WiFi interface, then Capture is not replying at ALL to the node discovery packet.

Any ideas?

I am sending Node discovery from my own Java application using artnet4j library. The see what Capture replies with the debugger. Just to be clear, when it replies an ipAddress of 0.0.0.0 , the reply packet include the "Capture" value in the long-name of the node, so I am sure it is Capture.

Thanks,

Erez.

Staff Member
Posts:2016 Staff Member

--
2014-11-18 11:34

Hi Erez,

I can confirm that it's a bug that Capture uses the IP address setting from the Options window rather than the effective IP address. We have fixed this for the next update of Capture now.

You should see 0x06 as the NodeStyle field in the poll reply though. And you should get replies to all polls, given that Capture receives them well. You could check Capture's log file (Capture Argo.log in your user's home directory on Windows or ~/Library/Logs on Mac) to see if the packets count at shutdown are reasonable, and whether it reports receiving any malformed packets.

Technical Director
Capture Visualisation AB
Basic Member
Posts:10 Basic Member

--
2014-11-22 11:59

Hi,

I don't see in the log file any indication of the poll replay. Though I am getting a poll reply with empty Style, and ip=0.0.0.0, and a name=Capture. I verified this with Wireshark.

I tested also with a software called QLC+ , and it also receives the same reply ("ip=0.0.0.0,etc...), check with wireshark. But QLC+ seems to be able to send ArtNet to Capture although it got this faulty poll reply, I am guessing it just sends unicast to the specified ArtNet sub-net, and it works.

I tried this with my own Java code, and it works as well.

So I have a workaround for now, but I just wanted you to know that this issue exists.

(I am working on MacBook Pro, with OS X Yosemite.

The 2nd issue I am having, is that I can't get this to work with localhost (loopback interface),

in this case, unicasting to the sub-net doesn't get any reaction in Capture. Although I set Capture's ArtNet address to "Automatic" (And restarted it).

Any ideas about the loopback issue?

Thanks,

Erez.

Basic Member
Posts:10 Basic Member

--
2014-11-22 14:44

ok, problem solved.

I was my mistake. I used ip address 127.0.0.255 instead of 127.0.0.1

Staff Member
Posts:2016 Staff Member

--
2014-11-25 09:42

Hi,

Generally speaking I would recommend not relying solely on ArtPollReply packets to know where to send ArtNet. Also keep in mind that Art-Net has a 4 port limitation in the reply, so devices and/or softwares capable of receiving more than 4 universes are prevented from properly indicating that with the exception of visualizers that can set a style for the purpose. Make sure to always give the user the ability to send ArtNet anywhere. If the machine you're running on doesn't have any IP interfaces connected, I would also recommend unicasting to 127.0.0.1, either automatically or with an option.

Technical Director
Capture Visualisation AB
Basic Member
Posts:10 Basic Member

--
2015-02-17 13:10

Hi,

I am having trouble connecting with Artnet to Capture running on the Local machine (127.0.0.1).

Basically it works fine, but sometimes (maybe after the computer is out of sleep mode), then Capture stops responding to Artnet packets unicasted on the loopback interface.

When it happens, then restarting capture doesn't help at all.

the only thing which fixes this is restarting the computer.

I am running on Macbook Pro Retina with OS X Yosemite.

Is this a known issue?

I am not sure if this is a capture issue, or an OS X issue.

I tried restarting the loopback interface using:

sudo ifconfig lo0 down

sudo ifconfig lo0 up


but it didn't help.


Thanks,

Erez.

Staff Member
Posts:2016 Staff Member

--
2015-02-25 16:49

Hi Erez,

If restarting Capture doesn't help, then it's not a Capture issue. However, it doesn't have to be an OS X issue, it could be an issue on the sender side as well. Chances are the sending socket is broken on sleep and needs to be reopened.

Technical Director
Capture Visualisation AB
Basic Member
Posts:46 Basic Member

--
2016-09-09 10:03
Hi

I have a problem with my new atlas.
I have a titan mobile connected to my capture laptop. Tuitan is 10.0.0.1, capture is 10.0.0.3
When I open a file in my old argo, all is good and I can see all my universes.
When I open the same file in atlas, with the same settings, I cant see any universes.
What can be the problem
Staff Member
Posts:2016 Staff Member

--
2016-09-20 08:50

Hi,

When everything works in one application but not at all in another, a good place to check is your firewall settings which may contain per-application exceptions.

Technical Director
Capture Visualisation AB
New Member
Posts:1 New Member

--
2023-01-04 05:28

Looking for help with connectivity. I have the latest version fo Capture running on Windows 11 on my laptop. I have our on-pc lighting software (Lightforge) running which is outputting ArtNet, verified with both connected fixtures, as well as using on-PC Artnet diagnostic tools. Capture is not showing up the External Universes for the software. This is all running on the same PC. I have set both software to use the same network adapter. Have tried it both with the Microsoft Windows firewall turn on (with an inbound exception for Capture) and also wtih the firewall turned off. Any ideas? I also have ETC Nomad, and same results, Capture doesn't see the external control. 

Thanks!

You are not authorized to post a reply.
Page 4 of 4 << < 1234