I have a TV1 miniCASTER vehicle-mounted satellite uplink positioner system. It is designed to go on top of a minivan, has azimuth bearing around 50cm in diameter, and an altitude motor which attaches to an arm which holds the dish and can fold down automatically for storage when not in use. Would this suit my intended purpose to use it to point at and track masers?

Your description matches the TV1 miniCASTER vehicle-mounted satellite uplink positioner much more closely than a conventional antenna rotator.

From the material I found, the system was mounted on broadcast vans and consisted of:

• A large circular azimuth bearing on the vehicle roof.
• A motorized elevation arm carrying the dish.
• Automatic stow/fold-down capability for transport.
• Separate azimuth and elevation motors.
• A control box and wired hand controller with variable-speed movement.

The most useful lead is a recent sale of exactly this unit, identified as a “TV1 Minicaster Mobile Satellite Dish Pointer”, removed from a KA-SAT outside-broadcast van. The photos show the azimuth turntable and elevation mechanism you describe.

Unfortunately, I still cannot find the actual service or installation manual. However, the search turned up evidence that TV1’s miniCASTER product line included a vehicle-mounted “Satellite-Uplink Car Unit” with automatic pointing, introduced around 2012.

My suspicion is that:

1. “TV1 Minicaster 1” is the vehicle positioner assembly.
2. The rotator itself may have been manufactured by a third-party motion-control company and integrated by TV1.
3. The installation and service documentation may have been distributed only to broadcast engineering customers rather than publicly.

If you have the unit in front of you, a photograph of:

• the azimuth bearing,
• the elevation gearbox,
• the control box interior,
• or any motor nameplate,

would likely let me identify the original actuator manufacturer. Once we know the motor/gearbox supplier, the service manual is often much easier to locate than the TV1 documentation itself.

I can also try searching German broadcast-engineering archives and old IBC exhibition documents for the original TV1 miniCASTER Car Unit manual if you’d like me to dig deeper.

This is the exact one I purchased.

That’s a fascinating find, Andrew.

The more I’ve dug into it, the more convinced I am that you’ve acquired a fairly rare piece of outside-broadcast hardware rather than a consumer satellite system.

The strongest evidence is the original product literature for the miniCASTER Satellite-Uplink Car Unit, which explicitly describes a vehicle-mounted system that:

• Mounts on a car, van, or SUV.
• Folds the antenna away safely when not in use.
• Uses a motorized pointing system.
• Is controlled via a joystick remote control.
• Includes a motorized frame, feedarm, dish, and controller.

The sale listing for the identical unit confirms:

• Large azimuth/elevation motorized positioner.
• Wired remote with variable-speed control.
• Separate control box converting mains power to motor voltages.
• Use on KA-SAT broadcast/uplink vans.

Even more interestingly, the original TV1 press material states that the Car Unit had autopointing capability, meaning there may originally have been:

• GPS input,
• a compass or heading sensor,
• limit switches,
• and possibly position feedback encoders on the azimuth and elevation axes.

I did locate what appears to be the original product brochure:

and another catalog containing a description of the Car Unit:

What I have not yet found is:

• an installation manual,
• service manual,
• wiring diagram,
• controller schematic,
• or maintenance manual.

Given your interest in radio astronomy and QO-100, this mount could be extremely useful. A 50 cm azimuth bearing suggests it was designed to withstand motorway vibration and wind loading, so it is likely far more robust than typical TV rotators.

The next step I’d suggest is photographing:

1. The control box front and rear panels.
2. The inside of the control box.
3. The azimuth motor and gearbox labels.
4. The elevation actuator label.
5. Any connector markings.

If we can identify the motor manufacturer (many such systems used industrial DC gearmotors from companies like Dunkermotoren, Bodine, Parvalux, or similar), we may be able to reconstruct the entire control system even without the original TV1 manual.

I suspect there is a good chance the actual positioner was built by a third-party antenna-motion manufacturer and rebranded by TV1. If so, the engineering documentation may still exist under the original manufacturer’s name.

Below is a link to a relevant edition of miniCASTER® Satellite-Uplink Car Unit magazine:

So how does this device compare to Yaesu G-5500DC for my desired purpose of pointing at and tracking masers?

For tracking astronomical masers (or any fixed celestial radio source that drifts slowly across the sky), I would actually lean toward the TV1 miniCASTER positioner rather than a standard , assuming you can get reliable position feedback and computer control working.

Attribute TV1 miniCASTER vehicle positioner
Intended use Amateur satellite antennas Professional satellite uplink dish
Azimuth range 450° Likely continuous or near-continuous (depends on slip-ring arrangement)
Elevation range 0–180° Probably optimized for horizon-to-zenith satellite work
Load capacity Designed for Yagis and small dishes, ~1 m² wind area Designed to carry a vehicle-mounted satellite uplink dish
Pointing accuracy About ±4% of scale according to Yaesu specs Unknown, but likely intended for Ku-band satellite acquisition
Computer control Well supported (GS-232, Hamlib, GPredict, SatPC32) Unknown until controller is reverse-engineered
Spare parts Readily available Probably difficult to obtain
Reliability Proven by thousands of satellite operators Depends on condition of your unit
For your specific application at 1420 MHz:

The sky moves at only about 15° per hour, or 0.0042° per second.
Even a fairly crude drive can keep a 2–3 m dish on target.
Unlike amateur satellite work, you do not need rapid slewing or sub-second updates.
The key question is not motor accuracy but position knowledge.

If the miniCASTER has:

potentiometers,
optical encoders,
resolvers,
or any other position sensors,
then it could become an excellent radio astronomy mount. The huge azimuth bearing and industrial construction are attractive advantages.

For maser observations with a dish of around 2–3 m at 1420 MHz:

A G-5500 is a known quantity and integrates immediately with astronomy software through Hamlib.
The miniCASTER is mechanically superior but electronically uncertain.
My assessment:

If you want something working next month: buy/use the Yaesu.
If you enjoy engineering projects and already own the miniCASTER: it has the potential to be a considerably more robust mount than the G-5500.
For a future 3–5 m dish, I would trust the miniCASTER’s mechanical structure far more than a G-5500, which was designed primarily for satellite Yagis rather than heavy professional dishes.
What I’d really like to know is the diameter and weight of the dish you intend to mount. If you’re thinking of the 2.4 m offset dish you’ve discussed previously, I can estimate whether the G-5500 would even be suitable, and my suspicion is that the answer may be “not comfortably.”

In first instance 1m offset dish which will be adequate as long as I can get it to track for few hours.

For a 1 m offset dish at 1420 MHz, the requirements are much less demanding than many people assume.

A 1 m dish at 1420 MHz has a beamwidth of roughly:

which works out to about 15 degrees (roughly 14–15° depending on illumination efficiency).

The sky moves at:

So if your pointing error is:

±1°: negligible loss.
±2°: still very little loss.
±5°: target remains well within the beam.
±7°: you’re approaching the half-power points.
For masers, hydrogen-line mapping, and other continuum work, a 1 m dish is therefore surprisingly forgiving.

What this means for the miniCASTER
Even if the original control system only allows manual movement:

Point at the source.
Move the dish every few minutes.
Record continuously.
You could still obtain useful data.

If you add computer control later, the tracking rate required is extremely slow. The mount only needs to move a fraction of a degree every minute.

Compared with a Yaesu G-5500
For a 1 m offset dish:

The G-5500 is electrically easier because Hamlib and other software already support it.
The miniCASTER is mechanically over-engineered for the job.
The miniCASTER’s large azimuth bearing was designed to survive vehicle vibration and carry a satellite uplink antenna. A stationary 1 m offset dish should be a relatively light load.

The big unknown
The crucial question remains:

Does the mount know where it is pointing?

If there are:

potentiometers,
encoders,
synchros,
resolvers,
Hall sensors,
then software tracking becomes straightforward.

If it only contains motors and limit switches, you would need to retrofit position sensing. Even then, adding a pair of rotary encoders is not a major obstacle.

Tracking for a few hours
For a 1 m dish, I would be optimistic.

A source moving from azimuth 120° to 170° and elevation 30° to 45° over several hours only requires smooth, slow motion. That is exactly the sort of motion a satellite uplink positioner was designed to perform.

My concern would not be tracking accuracy. It would be:

identifying the motor voltages,
understanding the controller,
determining whether position feedback already exists.
If you can post photos of the control box internals and the motor assemblies, we can probably determine within a few minutes whether the mount already contains everything needed for automated astronomical tracking.

Do you think it would integrate with any of the Yaseu G-5500DC control boxes we discussed earlier such as the Aliexpress clone or the Arduino board you told me about?

Short answer: not directly, and trying to make it behave like a Yaesu G-5500 system is usually more work than it’s worth. But it can absolutely be made to integrate with a G-5500-style controller with some interfacing, depending on what’s inside the miniCASTER drive unit.

Let’s break it down properly.

1. What the Yaesu G-5500 system expects
   All Yaesu-style controllers (including most Aliexpress clones and Arduino Hamlib builds) assume the rotator behaves like this:

DC motors
Reversible polarity for direction
One axis = one motor
Position feedback via:
0–5 kΩ potentiometer (classic Yaesu)
Simple control loop:
controller compares desired az/el vs pot voltage
drives motor until match
So the entire ecosystem assumes:

“motor + pot feedback = rotator”

2. What your miniCASTER likely is
   From your description (and typical broadcast uplink car units), it is very unlikely to be Yaesu-like internally.

It is more likely one of these:

A. Industrial DC servo system (most likely)
DC motors or brushless motors
Encoder feedback (incremental or absolute)
Separate motor driver electronics
Possibly CAN, RS-485, or proprietary control
B. Hydraulic / high-torque actuator system (less likely but seen in broadcast gear)
Requires valve control, not DC polarity reversal
C. Hybrid system
Motor drivers + limit switches + encoder feedback
Central controller handles motion profiles

3. Can you plug it into a G-5500 clone?
   ❌ Direct connection: NO
   You should not connect it directly because:

Motor voltage/current is unknown (likely far higher than Yaesu controller output)
Feedback is almost certainly not a simple potentiometer
You could damage the controller or the rotator

4. Can you adapt it to behave like a G-5500?
   ✔ Yes — but only if you add an interface layer
   You essentially have two workable strategies:

OPTION 1 — “Yaesu emulation layer” (recommended if you want simplicity)
You ignore the original controller entirely and build a translator:

What you do:
Keep miniCASTER motor drivers (if usable)
Read its real position sensors (encoders or pots if present)
Convert that into:
“virtual Yaesu potentiometer outputs”
Feed a Yaesu-compatible controller (or Arduino Hamlib rotator interface)
Result:
The G-5500 clone thinks it is driving a normal rotator.

This is the cleanest way to integrate with GPredict / Hamlib / SatPC32 style software.

OPTION 2 — Replace everything with Arduino + motor drivers
This is often simpler in practice:

Arduino (or ESP32)
Motor drivers matched to your actual motors
Encoders read directly
Hamlib rotctl interface
GPredict or custom tracking
In this case:

You do NOT need Yaesu compatibility at all
You treat it as an “industrial AZ/EL mount”
OPTION 3 — Attempt direct Yaesu clone control (NOT recommended)
Only possible if:

Motors are simple DC reversible types
You physically bypass original electronics
You install:
2× potentiometers (one per axis)
relay or H-bridge drivers
This effectively turns your professional mount into a Yaesu-style rotator, which wastes much of its capability.

5. The key deciding factor (critical)
   Before choosing any path, you need to answer one question:

What feedback system does it already use?
If you find:

✔ Potentiometers → easy Yaesu-style integration possible
✔ Optical encoders → Arduino/Hamlib best route
✔ Resolver / industrial encoder → Arduino or industrial controller only
❌ No feedback → you must retrofit sensing

6. My practical recommendation for your setup
   Given your goal (radio astronomy, masers, slow tracking):

Best approach:
Use the miniCASTER as an industrial AZ/EL mount + Arduino/Hamlib control

Because:

Tracking is slow (degrees/hour, not fast slewing)
Precision is modest (1–2° is fine at 1 m dish)
Mechanical stiffness matters more than “plug-and-play”
The Yaesu ecosystem is excellent—but it is optimised for:

lightweight yagis
satellite hopping
hobby control systems
Your mount is closer to:

“broadcast uplink positioning system”

7. If you want next step help
   If you can provide photos of:

motor nameplates
control box PCB
any wiring labels
azimuth bearing area underside
I can tell you very quickly:

whether it is encoder-based
whether it is reversible DC
and the easiest way to interface it (Yaesu-emulation vs direct Arduino control)
And we can pick a control architecture that won’t fight the hardware.