Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

novastar connection issue #16

Open
zackdickinson16 opened this issue Sep 1, 2021 · 7 comments
Open

novastar connection issue #16

zackdickinson16 opened this issue Sep 1, 2021 · 7 comments

Comments

@zackdickinson16
Copy link

Trying to use a Novastar vx6s module in companion. Getting a instance(novastar2): Network error: read ECONNRESET. Connecting for about a second then disconnecting. No one seems to be dealing with the issue on the novastar page.

Help

@josephdadams josephdadams transferred this issue from bitfocus/companion Sep 2, 2021
@DiegoMarchente
Copy link

How many machines are connected in the network?
If you have more than one, are you sure they don't all have the same MAC ADDRESS?
Have you tried to manage only 1 machine while keeping the others disconnected?
Best regards
Diego

@CVEmusic
Copy link

I having the same problem (Network error: read ECONNRESET) with a VX4S. We only have one VX4S in our network.

@zcarnefix
Copy link

I am having the same network error on a VS4X and 3 NovaPro HD's.

@cyberblaststudios
Copy link
Collaborator

Do you happen to be trying to connect with NovaLCT or another software while you are connecting to the device with Companion?

@DanielMixes
Copy link

Was anything resolved with this? I think I'm having an adjacent issue.

@CVEmusic
Copy link

@DanielMixes I was having the same problem with our VX4S and found out as soon as I close the Smart LCT software this error disappears and have a steady connection between Companion and the VX4S. Make sure after you close Smart LCT that you also close the Smart Mars server icon in the taskbar. #28

@DanielMixes
Copy link

Brilliant idea! I believe the installer left a micro-pc attached to the network for troubleshooting and maintenance and it’s probably running the software. Thanks, I’m going to check that out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants