Any Macbook Pro users can help me??

[taintedsaint]

I'm almost done sequencing my first show. I'm a long time Mac guy and haven't run into a single bug yet.
Will be running data into a 5 port switch over Cat5, then to each of 4 SanDevice controllers at locations of show elements. I'm doing it to prevent data loss over distance. Cat5 carries farther than the 3 wire.
I have set up controllers as Unicast since I'll have over a dozen universes and SanDevice recommended Unicast. But that doesn't address why I'm here.

My older Macbooks had an ethernet port and could use it anything, not just send/receive Internet connection.
New Mac has no port, so I have a Thunderbolt to ethernet adapter.
Problem is, Mac doesn't really recognize it the same way. It wants an IP address setup. Can't do that because each controller in Unicast mode has its own IP.
I couldn't even use the Mac to access the controllers interface, had to borrow a friends PC. When I plugged controller into his ethernet, entered controller IP in browser, it just simply connected. Mac won't do that.

I am not interested obviously in buying a PC and definetly not going Raspberry route. So any Mac gods out there able to help out?
I ask that you speak slowly and don't use distracting hand motions  as I get lost easily.

Thanks for all help.

Joe S.

[Gilrock]

...
Problem is, Mac doesn't really recognize it the same way. It wants an IP address setup. Can't do that because each controller in Unicast mode has its own IP.
...

My MacBook Pro still has an Ethernet port but in regards to this statement I quoted there shouldn't be a problem setting up an IP address for the port you just need to make sure everything is on the same subnet i.e. the first 3 octets match like 192.168.5.xxx where the xxx is all your cards.

[taintedsaint]

Thanks for that Gilroy. I have done exactly that. Controllers are setup 169.254.74.73 then .75 then .77
For the Network preferences should I just setup the first three fields? Meaning enter just 169.254.74 and leave last off?
Network preferences pane shows the Thunderbolt to Ethernet connection but with a yellow light next to it.
I have tried dozens of different settings but when I try to test sequence with 'output to lights' just nothing.
All the downstream hardware is correct, controller is setup right, etc.
Really frustrated.
Any other help would be appreciated or info you might need to help, just ask.

Joe S

[Gilrock]

I wouldn't leave the last field blank you need to treat it as another controller on the network and give it an IP address.

[taintedsaint]

I've tried so many things in the network field. I guess my confusion is why the PC I borrowed simply ran the sequence. No network setup required.
I love my Macs and have always enjoyed how when you plug something in it just works. However in this case it doesn't. I don't want it looking for an IP because there will, in the end, be three different IPs. One on each controller. Just need it to work as a data output.
Very frustrating.
I set IP for controller I'm testing. Nothing. Never shows 'green light' in network list.
Using borrowed PC, I can load a test and bam! right out to lights.

[dkulp]

Why are things on the 169.254 network?   That is NOT a valid network.   That is a range reserved by Microsoft  and shouldn't be used.   

Move everything over to a proper network range.

[Gilrock]

So first start using a different subnet like Dan suggested.  Second you keep acting like you don't want to assign an IP to the device on the computer but newsflash...everything that talks on a network has to have an IP address.  You are defining and IP address for the network adapter in the computer and it needs to be on the same subnet as your controllers.  Network devices either need to have hard coded IP addresses or needs to be configured for DHCP with a DHCP server like a router on your network providing the IP addresses.  You have not provided a single screenshot of the setup you are describing so its hard to give any other advice.

[logandc99]

This may not necessarily be your issue but I use a macbook pro with no ethernet port and use the adapter.
My home network is on 192.168.1.x and my Christmas light controllers are all on 192.168.2.x and each one has a fixed IP address and everything communicates nicely.
However, I have noticed that if I have my laptop wifi on and connected to my home network and my ethernet port is connected to the controllers, with the wifi still on I can't communicate with the controllers. As soon as I turn the macbook pro wifi off, it all connects to the controllers happily.
I still get a green light symbol next to the ethernet in the network preferences when the wifi is also on as if it's connected fine, but won't actually be able to access the controllers until the wifi on the macbook pro is turned off.

I will have to check tonight with my older mackbook pro that has an actual ethernet port to see if it can talk to the controllers even if the laptops wifi is on or not.
Anyway, just a thought.

[keithsw1111]

XLights can force the output it uses.


Sent from my iPhone using Tapatalk

[logandc99]

Keith, is there some setting in xlights to change to allow it to force output through the right network port (i.e ethernet vs wifi) because mine definitely has to have the wifi turned off before I get lights. Can't even get to a controller's webpage unless wifi is off (or is this maybe just a mac thing).

[keithsw1111]

There is in settings.


Sent from my iPhone using Tapatalk

[logandc99]

There is in settings.


Sent from my iPhone using Tapatalk

Lol


Sent from my iPhone using Tapatalk