Tomatobro

I dont have the camera you have but do have some others that run on the older version (3.2 I think) which when I last looked was still downloadable. Otherwise try the 32 bit 4.0 version.

A couple of questions. which version of Sharpcap have you installed?

My hunch is that NINA is using Powershell to call the batch file and allowing it to run in the background while just displaying the CMD screen. There is also something going on where if the USB to serial module is not connected then calling the batch file direct it runs but reports that the call to the none available serial com port is not available but completes the batch file instructions. NINA looks to be running a check first and reports that the batch file cannot be run with the designated com port missing.

When NINA calls the batch file you get a plain CMD terminal with no other text. In SharpCap you get the c:\ Program Files (x86) SharpCap 4.0 as a first line. So my thoughts were that SharpCap is invoking the batch file in a different way to NINA. I don't have the "Program files" bit as part of my batch file so it must be being generated by SharpCap.

Sharpcaps sequencer treats the batch file as I would expect in that there is no difference between it being called or run direct I wonder if a clue lies in the first line of Sharpcaps call

These two screen shots show the difference between the two terminal screens. Don't worry about the illegal com port it was not connected. Capture1 is when the batch file is called direct and capture 2 is when called via NINA. For both screens the batch file is running successfully.

1) when the batch file is called from the directory where it is stored (documents) it displays the terminal screen and it runs properly. Shows things like the timeout counter counting down etc. Both NINA and Sharpcap have provision in the sequencer to set up a path to a batch file and will run the batch file when it is called. When the batch file is completed the terminal screen closes and returns to the next step in the sequence. The difference is that when called by NINA the command terminal opens but does not display the information (like the countdown timer) but is just a terminal with a flashing cursor. However, by watching the output to the serial port I can see that the batch file is running in the background, and when finished the terminal screen closes and NINA then goes to the next step in the sequence 2) In the advanced sequencer you pull across the bar from the menu and type in the path to the batch file Why clicking directly on the batch file it runs AND displays the progress but called from NINA it runs but the progress is not displayed seems odd as control is passed to the same bit of DOS code. Hope this clarifies but I will try to capture and post both terminal screens if it helps

Tomato has an older Pulsar dome for which we built the dome control. We use Rf solutions modems to do two way communication to the dome (all electronics rotate with the dome) As we make changes to the controls to allow for unattended imagining we need for Nina to run on one laptop. The idea is that NINA will do focusing on scope A then run a script that will switch the usb port to the other focuser if FWH changes. then run focusing and then switch back. We also will be able to close the shutter at sequence end rather that rely on a timer. Other changes are planned such as stop on cloud detection etc

I also checked to make sure black text was not being printed on a black screen....

As I say its not the end of the world because when the batch file runs I should be tucked up in bed fast asleep....... So no one will be their to read the screen anyway but for completeness it would be good to have it run as it should

NINA in the advanced sequencer allows for a .bat file to be inserted and run I have a .bat script that sends via a com port a command to open and close a relay. This batch file when run directly from the documents folder shows the terminal screen and displays all my echo text and opens and closes the relay and closes the terminal when done. When called from NINA the terminal screen is shown and the batch file runs properly in the background but the terminal just shows the CMD and a flashing cursor then exits when the batch file is done. No echo's are shown. I can live with the way it works now but are there any MSDOS experts out there who can point me to the command to make it display the script? I have tried all kinds of Google searches but nothing seems to fit this problem I am beginning to think this is a NINA issue as Sharpcap 4.0 sequencer has the same run batch file facility and it runs my batch file normally i.e. it shows on the console all my echo's for script progress.

There is a feature on this in the July 2021 Astronomy Now magazine.

Just packed away my PST. Have been watching two flares on the limb, a really big one that seemed to eject the top of it and a arched shaped one in the other hemisphere. Plus sunspot group, three more isolated ones and a big filament

I remember doing a knife edge test on my OO 10 inch Newtonian mirror and seeing a pronounced raised round ring on the centre of the mirror. When I questioned it I was told not to worry as its probably in the shadow of the secondary 🤣 This was back in the late 80's

I find the guiding assistant really helpful for the initial setup. I know getting on with imaging is a priority but take the time to run the assistant and see what it tells you

Just noticed you image from New Zealand so I would add Earth tremor........ I used to setup about 50 metres from a full width road speed hump and some high speed cars and vans would shake the ground enough that I could see it in PHD

A Gust of wind associated with the advancing cloud front ( star quality drop at the other end of the graph)? Cable snags, voltage droop, intermittent connection somewhere, guide camera flexure, tripod leg sinking into the ground.

I use a variety of equipment on my Star adventurer and I mounted my guide scope onto the C/W bar and found a lighter counter weight. I works very well.

If its the Canon version of the Samyang 135 lens then you are good to go with the adapter. The Sony version, while being a lot cheaper to buy used requires a special adapter to get the correct back focus

Ha capture is on the "to do" list

UKMON analysis : https://archive.ukmeteornetwork.co.uk/reports/2022/orbits/202204/20220409/20220409_024010.013_UK/index.html

currently being analysed by the UKMON network. Caught on about 10 cameras I believe.

I made a custom clamp for the counterweight bar. I can move it up or down for balance and rotate for alignment. I use pulse guiding via PHD on a laptop. Guide scope alignment is not critical as long as its near enough pointing to the same bit of sky. You can see a custom red counterweight which is lighter than the one supplied with the SW adventurer.

I mount my guide scope on the counter weight bar and it works well. If the ASIair was moved to the bar it would distribute the weight better and solve the flip interference problem.

Looks like a long wait for my Nobel prize and they don't award posthumously anyway.........