Hey Carl,
Check out this thread regarding the same Child Processes error that you’re getting:
In short, a “child process error” occurs when a subprocess created by a program (the “parent process”) runs into a problem that prevents it from completing its task. We’ve become aware of a rare issue with a recent Windows update that can cause this error when trying to run FireControl; it seems the update affected how the computer handles power efficiency, as it seems to have affected specifically power-efficient CPU models. It’s worth noting that this issue is related to the Windows operating system, not a problem with the FireControl software itself.
I recommend trying a fresh FireControl installation:
- Uninstall FireControl from your computer via the Control Panel.
- Delete the “.FireControl” folder, which is typically located at the file path: C:/Users/[YOUR USERNAME]/.FireControl
- Restart your computer.
- Reinstall FireControl.
- If the issue persists, try again, this time installing the “compatibility” version of FireControl.
@toolboy and @Upstategrowguy77 are exactly right, FireControl functionality is locked unless connected to a CrossFire Motion Control Board via USB. That said, the program should remain open but “dormant”, this wouldn’t cause it to crash with the Child Process error.