Kulp 16A-B RJ45 Ports Not Working

[chdkhff]

I purchased a Kulp 16A-B v1.01 last summer from Wired Watts for my first light show this past Christmas (2021). When setting up, I noticed one of the RJ45 ports (21-24) did not send any data. Since I did not have time to investigate it further, I simply reconfigured the layout to work for the season. In the process, I encountered a few other RJ45 ports (18, 31, 32) that either sent no data or had issues. I rotated receivers to determine that the receivers were not the issue. It seems to be with the controller. 

I am wanting to expand this season and would really appreciate being able to use these ports. I noticed there is an update for v.09 pre-production boards with a similar issue. Is there a software issue here or likely a bad board?

Thanks so much! @dkulp

[tbone321]

Post an image of the Kulp configuration screens, both input and output so that we can see of it is configured correctly.  In may cases it is the configuration that is the issue and not the hardware.

[Poporacer]

Troubleshooting can be a bit of a pain at first. You stated that one of the RJ45 ports was not sending data? How did you make that determination? Do you have an oscilloscope or make the assumption because nothing was lighting up? You stated that ports 18,31, and 32 didn't send data or had other issues? Can you explain what these issues were?
Like @tbone321 mentioned, post your screenshots.

[chdkhff]

tbone321
Thank you for the reply! Attached is an image of the outputs. I do not have inputs (is that bad?), but have attached the image as well. I'm currently working on re-configuring my layout, so I did a simple setup (16 strings of 50 nodes) to test my differential ports. On a Kulp16A-B, these are ports 17-32 (pictured).

Poporacer
I agree! I'm new to the process but have had my fair share of opportunities to trouble shoot. Ha. Glad to have found this forum!

Unfortunately, I do not have an oscilloscope. I noticed the issue last year when setting up, but did a quick reroute to make it work.

To test I created a group of 16 strings in XLights and ran it through FPP in Bridge mode. I rotated the same receiver through each RJ45 port. Lights connected to Port 18 will not light up and the data LED on the smart receiver will flash for that port. I noticed my ports 31 and 32 seemed to be working today.

When I connect the smart receiver for Ports 21-24, nothing lights and the data LEDs remain off.

Is there a better way for me to be testing? Thanks again for your time! Really appreciate all the help!

Chad

[Poporacer]

Unfortunately, I do not have an oscilloscope.

I asked because you said it was not sending data and an oscilloscope is the only way to determine that. There is a difference in no data and incorrect data and the results will look the same and we need to know what it is.

I do not have inputs (is that bad?)

It could be depending on your usage

ran it through FPP in Bridge mode

And if you are running in Bridge Mode then you must have the proper inputs enabled. In your case you do have them enabled but only if you are using DDP data. You didn't mention if you were using E1.31 or DDP data.

I rotated the same receiver through each RJ45 port.

Were you using the same cable and connected directly to the controller and not a pass through gland?


What version of FPP?

You do have a bit of a configuration problem but it is partly contributed to a minor bug. 
Your controller has to be configured to match your receiver settings. Typically if you are not chaining the receivers, you would use Standard mode (even though it is a smart receiver) and set the receiver to normal mode. 

Your FPP shows Standard AND Smart Receiver options which is NOT a possibility. On each section, change the Differential Receiver option to one of the Smart Receiver modes (V1 or V2) and if you are going to use them in Normal Mode, then change back to Standard mode. Then Save and make sure that your receivers are configured correctly.

Is there a better way for me to be testing?

You really didn't give enough detail to determine that. The most important thing is to eliminate as many variables as you can. 

For example, use a short network cable connected to the receiver, then make sure that the port settings are exact on all of the ports (except for channel numbers) then plug that cable directly into the jacks on the controller without going through any glands adapter etc.

[chdkhff]

You didn't mention if you were using E1.31 or DDP data.

I am using DDP. 

Were you using the same cable and connected directly to the controller and not a pass through gland?

Yes, I directly connected the same, short network cable from the Kulp board to the receiver.

What version of FPP?

I used 4.6.1 for last year's display. I've updated to 5.5 recently to see if that would fix the issues.

Typically if you are not chaining the receivers, you would use Standard mode (even though it is a smart receiver) and set the receiver to normal mode. 

I hadn't noticed that issue. I am not chaining any receivers (v1.03) and have set them all to standard (see attached image). I retested after this change with the same results I was getting earlier.


Again, thanks for all your advice! 

[Poporacer]

Just to be sure, on the receivers the jumpers/switches are configured for Normal mode and terminated?

[chdkhff]

All receivers are set to the normal mode and are terminated. When testing I used the same receiver to avoid receiver issues.

[bloojoop]

Additional comment, on the Kulp controllers, the data lights on the receivers will ONLY light up when it is actively receiving data from the controller.  This is different that when attached to falcon controllers.

[Derick_hardy]

What was the final solution on this issue I think I'm having the same problem.