I am using a PrimaLuceLab Eagle 6 connected through the thunderbolt port to a Solo10G SPF+ to the Aluma AC455. This connection is very wonky, much more so than I have time to describe here. Recently, when I connect the fiber optic cable the windows system requires me to re-login, which is a problem if I am using a remote connection, because it will not turn on the wifi until I login, which I cannot because I am not connected. In addition, Maxim is only seeing one camera, which is says is the SC4, but when I take a photo it is really the Aluma 455. Both are physically connected. This seems very hard to figure out. The Eagle 6 has a 2.5 GB ethernet port. I know it is slower, but would I be able to use this, instead of the Solo10G which might allow me to debug this. I have spoken to PrimaLuceLab, but they are not familiar with the solo, and recommended trying to solve this though some windows settings, which failed.
Ok, agreed "wonky" is not optimal. Set the 10 Gigabit network's Interface Metric to 1000, a very high number. That way Windows will try to use another network connection (eg 2.5GB Ethernet, then Wi-Fi, then last attempt will be 10GB Ethernet on the Solo) for internet / remote access. Similar to this: Otherwise, when you add the new network connection (plug in the fibre or Thunderbolt or camera gets linked), Windows goes "hey that's a new, very fast connection, let me try using that for everything". And remote desktop connections drop when this happens, until windows figures out that it can't connect, so RDP drops, retries, and makes you log in again. I'll follow up with engineering on your other items.
Thanks Colin, This seems to have worked for allowing me to recognize the SC-4 and AC455 independently. Prior to your fix, the DL ConfigX4 utility only saw the SC-4 (but weirdly when connected was the AC455). Both cameras are recognized and work correctly in Maxim LT 7. Unfortunately, the issue with the Eagle Wi-Fi disconnecting when connecting the fiber optic cable is not fixed. You still need to use a password on the Eagle directly to restart the WiFi. What is puzzling is that the Eagle had never been connected to the internet between when the Wi-Fi was not interrupted and when it is interrupted. So, there should have been no Windows updates. I did plug the Solo into the second thunderbolt port (I was using the first before) for a time, and this may be related to the issue with Wi-Fi interruption.
What happens if you hook a monitor and keyboard/mouse to the Eagle? Is it popping up some message, like UAC admin approval needed? Or something in the toolbar notification area? Is there any way you could provide a screen shot? This sounds like an authorization/group policy configuration issue. Doug has an Eagle 4 Pro with the Solo, and a couple other customers do as well. Am wondering what might be different on your setup.
Some additional thoughts: 1. It just occurred to me that the Solo in the other port may have kicked off that same issue you had originally. eg Kernel DMA Protection 2. How are you connecting to the Eagle in your normal operation? eg RDP via Wi-Fi? What's asking for the password?
I've updated this article with additional tips: https://forum.diffractionlimited.co...et-with-optical-fiber-sfp-transceivers.10113/
This has been happening from the beginning. But I hadn't figured it out because I thought it might be a power protection/management issue on the PrimaLuce side. I thought this because the Wi-Fi disconnect would happen when I toggled on the power for the AC455. Eventually I tried powering up the AC455 but not connecting the fiber optic cable. Powering up without the fiber optic cable connection did not cause any problem. I found that the Wi-Fi disconnection happened immediately on connecting the fiber optic cable. At first, I had no idea why this was happening. Also, it did not happen every time. Then is stopped happening. Then it started happening again (I believe it started again when I tried the other thunderbolt port). I switched back to my original (working) thunderbolt port and the problem now occurred using that port. I deleted and reinstalled the Solo in the device manager. and it worked again, but only one time. Now it disconnects Wi-Fi every time I connect the AC455 to the Solo using either thunderbolt port. I typically use the window's remote desktop protocol with my laptop, connecting to the Eagle 6 via the Eagle 6 Wi-Fi. The Eagle 6 is running Windows 11. I have run the system with the Eagle 6 connected to a monitor, keyboard, and mouse. When I connect the fiber optic cable there is no error message. It appears as if the Eagle Management System logs off (or maybe shuts down?), and the Wi-Fi shuts off. The Eagle Monitor shows no error message, I just need to hit the return key, and re-enter the password. When I do this the eagle management restarts, and I hear the beep for the Wi-Fi restarting. I can then re-connect using my laptop. The problem, of course, is that in the field I have no way to enter a password once the Wi-Fi is disconnected, and no way to reconnect the Wi-Fi without entering the Eagle Password. I believe I have disabled the DMA Kernal protection in the Windows Setting.
I have tried using the instructions you site in your link (You have sent them before). I did not hink I needed to do : Marvell / Aquantia Chipset-based network cards and adapters instructions, as I had followed the instructions for the Solo.
Is there anything in the Windows Event Log telling you what's going on? Is the Eagle utility doing a crash dump? Is there a log? What happens if you connect a wired ethernet cable between the Eagle and a hub+the laptop? Does it drop out then?
I think you're going to need to reach out to PrimaLuce on this. If I hear back from them, I will discuss with them. It sounds like the issue is a change in the network configuration of the machine is not handled by their software automatically. Is their software controlling the Wi-Fi? I am not very familiar with what their software does.
I think you are correct. I had to use the bios and turn off kernal protection on the new intel chip, so many of the log errors have gone away. But that is not the problem. The Wi-Fi is controlled by the eagle manager, and that is what is crashing. I have enclosed the relevant events. But thank you for your help, I would not have been able to figure this out without your guidance
Ok, let me know what you learn, and we're happy to assist PLL as needed. I think it might happen with any network change - eg maybe with a USB network dongle.
