I use TrackSkull to create tracks for my animatronic skeleton skulls. I import the tracks created by TrackSkull into Brookshire VSA. I believe I have adjusted the settings in the VSA software to SSC32servo correctly and set the assigned number, port, and servo settings correctly to accept the import of the TrackSkull .txt file however VSA is giving a Bad Event at event 1, and others event numbers on retries so it does not load the track and I cannot edit the track, or delete the bad event etc. I did this a few years ago and everything worked fine and now when I am getting back into it I am encountering this major issue. How do I address it. I can control the skull using the joystick in TrackSkull and export the file fine.
Hi skyking,
My understanding is you have issues with the Brookshire to TrackSkull conversion.
Can you make a very simple sequence to move one servo in VSA to test if the SSC-32 is operating correctly ?
All the best,
1 Like
Thanks for reaching out. The SSC32 is working. After considerable troubleshooting and running some VSA routines saved a few years ago it appears that the issue is related to software compatibility. I concluded this because I found some old VSA routines I had saved and used a few years ago when made using my older version of TrackSkull 2.1.6.2 software vs the current 2.1.9.0 that I had recently downloaded and re-installed on my new computer. The skull worked and was able to run the routine in VSA version Professional v6.010. I was also able to get one of my animatronic skulls working by creating a new track using 2.1.6.2 and importing it into VSA and it also worked moving the skull properly. However I was unable to get a second skull working shortly thereafter which may have been because in my haste to solve the issue I had some servo settings in VSA not adjusted correctly for the second skull or I had accidently selected the wrong version of TrackSkull to create the track when I was testing it as both versions of TrackSkull were loaded on my computer. Unfortunately I ran out of time to do any further checking to resolve the issue in time for my 2025 Halloween display so it remained inoperative. I will have to do further testing to fully verify if software compatibility was the issue. A possible other resolution could have been that I had overlooked the setting to designate the controller to SSC32 in TrackSkull when I initially installed it however when I checked it I observed it was set correctly.
1 Like