Titanium ASC1 or ASC-1 Software Update Attempt

el bandido

TNAP-Images
The Titanimu ASC! or ASC-1 was released several years ago as a dish positioner with several features no other positioner has. Unfortunately, the software for the ASC1 had a few bugs that were never eliminated. Some time ago, I was gifted some ASC1 units and have been waiting for the right time to do something with them. That time seems to be Now.

I have been able to take the ASC1 software apart and examine it. While it is somewhat tricky to make edits to the ASC1 software, I think it is "Doable", but there is an outside possibility in bricking the device. While I am not interested in disabling an ASC1, I do have extra units which puts me in a unique position to try some software edits. Once the software is tested and proven safe, it can be distributed to others.

I will target 2 things with the first edit attempt and add a third.
(1) There will be an attempt to show coast counts. Currently when the ASC1 removes power from the actuator, the counts stop. In dish systems with worn parts, the actuator can continue to move for a bit and the operator cannot see it. The first edit will allow the counts to progress for a short period after the power is removed from the actuator.
(2) The second edit will address the ASC1 losing its position after the power blinks.
The position is saved every time the dish comes to rest.
The stock firmware only saved it during a power failure, and that save took long enough that a quick flicker could interrupt it. CF2 keeps the position and satellite number in 16 rotating slots in unused EEPROM, each with a checksum. At power-up it uses the newest good slot, never zero or garbage. If the dish hasn’t moved since the last save, a power dip writes nothing at all.
Power-blink guards:
DiSEqC commands are ignored for 2 s after power-up (the boot timing problem Titanium described).
Reset SAT data, Reset soft limit, Reset position and Global Reset are refused for 2 s after power-up and after any supply dip. A dip can look like a key press, and that’s my best explanation for lists coming back blank after storms.
In normal use, just wait 2 s and press again.

(3) Add onscreen metrics to the FTA receiver.
By utilizing RS232 port, we have the possibility of adding onscreen information about what the ASC1 is doing or what the ASC1 has done. This feature will require cabling from the receiver to the ASC1 as the RS232 ports on the FTA receiver and the ASC1 have to be connected. This addition hopefully will mean no more looking at a small display for information! ...We will see eh???

What I would like if possible is a full description of how the software failed from anyone that is currently using the unit. The edits I mentioned above have already been made and written. Now i will need to dig out a RS232 cable and flash one of the ASC1's and see what happens. Again, I am not interested in bricking the unit. But I do have spare or extra ASC1's which puts me in a very unique position to try this.
 
If I may. Please accept my input.

1) During a brief power interruption the circuit has energized the relays during boot. I have not isolated if there is a rogue or corrupted diseqc signal coming from the satellite receiver. The dish mover operates the actuator. Usually in an extension (dish moves East) of the actuator.
The counter seems to lag. There are times when the actuator continues to operate and the mover shows that it's going to a satellite that is actually lower in the arc. The dish has erratically and non repeatably been run to the East limit only due to limit switch operation at the East Limit.
Resulting in a sensor error message on the display.
Requiring a manual return to the zero reference satellite and then a position reset in the resets menu tree.
Occurs on three ASC-1 units. Again. Have not tried not cabling the receiver to the mover nor sniffed the coax for a rogue diseqc command.
I have added an octal socket with a time delay relay. The relay provides for a 30 second on-delay after power failure before sending power to the mover.
Problem has not happened since.


2) I did not realize that the serial port in its current configuration provided Tx data. Perhaps me. I've used a serial man-in-the-middle port monitor and so far have only seen Tx from the ASC-1 Loader.
3) Yes. When the MCU de-energizes the H bridge. The counter input is disabled. It was mentioned by you in a reply some time ago that any coast of the actuator was because the actuator is worn and sloppy. The actuator motor itself will coast slightly after power is removed. More when the dish weight on the actuator in retraction. Removing the actuator cover and looking at the armature clearly shows that it is true.
Using a standard 6 pole ceramic disc magnet as the sensor trigger. As is common in most actuators units.
Those small continued armature coasts add up with every application of DC power to the motor.
The result is a sector magnet that is on the verge of operating the sensor (reed switch or Hall sensor).
The MCU closes the H bridge relays. The sensor circuit misses the just about to occur pulse. The errors accumulate every time the mover actuates the motor through the geartrain.
The effect is amplified during initial setup and using the jog (West-East) buttons on the RCU to search for and peak satellite signals before storing the position in memory. Things like single, repeated key presses to move the dish to its optimum position.
Or after the errors accumulate. Using the jog function to peak signal. A mistake would be is if that happens, to store that position again in memory.

My method would be to suggest when searching for a satellite. Perhaps two or three.
Always use the satellite lowest on the horizon as your 0000 stored reference.
All others increment in positive stored positions. For me 127 W is the lowest. And is stored in the 0000 memory slot.
125 W follows as 0137. And so on.
When searching for and peaking signal on higher arc satellites. Store that position in memory.
Return to 127 W. Check signal level. The mover has returned it to 0000
But your actual signal peak may now be -0012 or perhaps +0017.
Peak the signal. Scroll to Back to main menu. Press OK (center button on the RCU).
Scroll to System Reset. Press OK.
Scroll to Reset position. Press OK. Then press the Home key (little house).
127 W will now be set to 0000. Where signal was the strongest.
You can then return to the last satellite you stored and peak and store the signal.
All other satellites will be peaked for best signal.
An occasional return to your 0000 reference satellite and doing a Reset position needs to be done.


4) A pre-release NDA schematic of the ASC-1 a PWM pin on the MCU that is conected to a MOSFET at the H bridge.
It is not used in the production release of the ASC-1. But the components are present.
The information I was given was that the intention was to provide a ramp-up/ramp-down speed control of the actuator motor.
For whatever reason. It simply was never used.
Implementing the function would most definitely reduce actuator overshoot and sensor count errors.
Enabling PWM could also enable jogging the dish at a slower rate than normal.
Switching satellites on a receiver would provide for a slow start. With speed increasing in a few seconds.
It could then zing along across the arc. When it gets close to the target position. slow the actuator motor down and nudge it to a stop.
Spot-on.
I have placed a small SPDT 24 VDC relay inside the cover of my actuator. It functions as a dynamic brake for the motor.
Opeartion is simple. The armature leads of the motor are connected to the armature (common, or points) of the relay.
The NC side is connected to a 1 Ohm resistor. And the NO side is connected to the output of the terminal strip motor power leads from the ASC-1
The relay coil is triggered by voltage from the ASC-1.
When the mover is energized, the relay contacts close. Pixies are sent to the limit switches and then motor.
The mover shuts off, the contacts open to the the resistor side and the armature halts almost immediately.
If you have ever played with a brushed DC motor. And spun the shaft with the battery leads separated. It spins freely.
But if you short the leads together and do the same. The shaft is mich harer to spin. And a free-spin is impossible.
Industrial DC motor use motor controllers that have the same braking function. And depending on the H rating of the motor, have different pluggable shunt resistors to "soak up" the motor current when the previously powered motor now turns into a DC generator.
They stop fast.


5) The ASC-1 was a fine unit. Too bad it's obsoleted and out of production. There is one other that a fellow in England makes over on SatsUK. More robust than the Titanuim. Hand built to order.
Still engulfed with NDA and trade secrets. I wish there was a version of the ASC-1 still available.

A thought came up. I mentioned it and had a bigassed light bulb light up, upstairs.
So. Here goes.
I have seen photos of different folk's satellite system setups. Different receivers, ASC-1's, V-Box and their spin-offs.
In several photos I saw what looked like a rack mount commercial receiver.
Further looks showed a Satellite Antenna Positioner. Made by Research Concepts in the good-old USA. In Kansas, of Kantronics fame.
I investigated them and asked questions. Looked on eBay. Surplus ones in very good condition are around, to somewhat more than what the ASC-1 costs and what folks are getting for them today.

The readily available RC-1500 (single axis) and RC-2000 (dual axis) units are brick wall tough.
Documentation down to the serial interface protpcol and schematic diagrams are freely available. Users manuals are robust.

I called them. Very nice people. Asked about a DiSEqC interface to use with an FTA receiver.
If we were face to face I would have seen a blank stare. They deal with commercial satellite equipment. Flyaway, tracking systems.
Nothing remotely at all concerning FTA receivers using DiSEqC or USALS.

I called several of the software vendors that they recommended. Nobody I spoke with could help.
RC units use a very old Scientific Atlantic antenna positioner protocol that is still commonly used al over still.
I have the command string kind of figured out.
Same for DiSEqC. But I'm no programmer. I'm a hardware dude. You may think differently.

So. All of the Arduino, ESP32, Pi community folks. I thought and thought for the right terminology to air my interest or a bit of direction.
Translator? Transcoder? Serial Protocol Converter.
An MCU sitting there. Yep. A "Man-in the middle". Sitting there waiting for a signal from an FTA receiver. A DiSEqC signal.
There are several Arduino dish mover projects out there. I cannot grasp the code. Brain fart? Don't know. Inexperience to just say "Hello World"?

What IF we have an MCU connected to a coax in some manner just waiting for a signal. It could be simplex, could be duplex.
It waits for a command from the receiver to move a dish. Just like the ASC-1, V-Box.
And then in a lookup table. Kind of like that goddamned satellites.xml file that has every satellite in it. Remember, I use mine (xml) trimmed down for 34 W-131 W C & Ku band only.
The lookup table stored in RAM.
The RC units need a satellite position. An actual satellite name. In a particular spot in a data packet. To initiate a go-to of the dish moving hardware.
In its simplest form. The serial port would need a RS-422 to RS-232 protocol converter.
Sits there waiting to receive the data string. Wakes up. Hears DiSEqC say "Go-to position 47". And does it happy as a lark.

The MCU could come with a lookup table. Like, oh, you get with your universal, programmable remote controls.
Position 0000: Galaxy 37/Horizons 4 at 127.0°W
Setup the RC-1500 the same way. And so on.

Damm. I need coffee. Going the send this with no spell check.
 
Last edited:
This is what I have created. It is not flashed yet, so we will need to see if it flashes or bricks.

Here is every difference between CF4 and stock 20151019v1, checked against the builder’s patch list (11 patch points in the stock code, plus one new block of code at $1400–$1BDD).

What changes for the user
1. Dish position counting
  • Coast is counted. Stock firmware stopped counting the moment motor power dropped, so the few counts of armature coast after every goto or jog press were lost and the error built up. CF4 keeps counting through the coast.
  • Counting never switches off. With the motor off, a pulse is counted in the direction of the last East/West move, like a V-box. A pulse after the dish has come to rest is reported as a stray count (STRAY E/W, then STRAY END +n). If there’s been no move since power-up, the direction is unknown: it’s reported as STRAY ? and the count is left as it was.
  • Push-back is counted too, but always in the last drive direction, because one sensor can’t tell which way the dish is turning.
  • The stock debounce (about 7.8 ms between counted pulses) is unchanged.
2. Positions survive power cuts and blinks
  • Stock firmware saved the position only at the moment power failed. That’s what produced the all-zeros unit after storms and blinks.
  • CF4 saves every time the dish comes to rest, into a 16-slot ring in EEPROM space the stock firmware never used. Each slot is checksummed and its commit byte is written last, and the writes rotate across the slots so they don’t wear one spot out.
  • At power-up it restores the newest valid slot. A cut during a save falls back to the previous slot, never zero or garbage.
  • The emergency save on power loss is faster: the next slot is erased ahead of time, so it finishes in under 1 ms. It writes nothing if the dish hasn’t moved since the last save. It also no longer rewrites the EEPROM word that holds the LNB setting, which stock firmware did.
  • Stray counts are saved after a quiet minute, so a chattering sensor can’t wear out the EEPROM. A power cut during that minute still saves them.
  • The first boot after flashing uses the stock saved position (BOOT O). From the first rest onward it uses the ring (BOOT R).
3. Power-blink guards
  • DiSEqC commands are ignored for about 2 s after power-up (DQ IGN).
  • Reset SAT data, Reset soft limit, Reset position and Global Reset are refused for 2 s after power-up and for 2 s after any supply dip. A supply dip can look like a key press.
  • No position save happens while the supply is dipping.
4. DiSEqC protection
  • Stock firmware checked parity only on the first byte of a DiSEqC frame. CF4 checks every byte, and drops frames with a bad bit or a byte cut off halfway (DQ BAD). This closes the one-bit go-to → STORE / DRIVE / wrong-slot bug.
  • Go-to, store and drive commands that arrive without their data byte are dropped. Without the data byte, a drive command would mean “run continuously”. Proper 3-byte commands (halt, limits) still work.
  • Store is refused while the dish is moving, coasting, or the supply is dipping (DQ REFUSED).
  • A go-to to a different slot in the middle of a move is refused unless a halt came first. Enigma2 sends that halt when you zap while the dish is moving, so zapping still works. A repeated go-to to the same slot is always accepted.
5. Serial port
  • Satellite list upload fixed: stock firmware aborted any record containing byte 0xEF, so positions −4352 to −4097 could never be loaded. CF4 accepts them.
  • New RS232 monitor, off until the receiver turns it on (0xC1 on, 0xC0 off, 0xC2 re-send status). Its messages:
    • ASC1 CF4 (greeting)
    • BOOT R|O ±n (power-up, and where the position came from)
    • RUN E|W, POS, STOP, SAVE, SAVE ERR
    • STRAY …
    • DQ … for every DiSEqC frame received, with IGN, BAD or REFUSED when it wasn’t carried out
    • BLOCKED, LIMIT
  • The monitor on/off bytes are recognised even when the stock serial handler gets them first.
6. Version text: the menu shows FW:20151019.01 CF4.

What CF4 leaves alone​

  • The bootloader, which is flash-protected and untouched
  • Menus, the front panel and the remote
  • Motor drive, limits and the stall logic
  • The satellite list format, and the protocol used by Loader Editor 2.0 and the Linux tool
  • The stock EEPROM position area, which CF4 only reads, once, on the first boot after flashing
  • Which DiSEqC commands it supports. There is still no USALS.

Patch points in the stock code (for the record)​

Stock addressChange
$3328timer interrupt hands off to the new code: coast and always-on counting, stray detection, timers
$32ECstock power-fail save replaced by the new emergency save into the ring
$437Dstock power-up position load replaced by the ring restore
$3597main loop hook: save-at-rest, monitor output, serial commands
$36BDDiSEqC execute goes through the new gate first (boot/BAD/REFUSED rules)
$51FC, $5227DiSEqC byte reader replaced by one that checks parity
$37A4menu table entries for the 4 reset actions point to guarded versions
$492B0xEF no longer aborts a satellite record
$480Cmonitor bytes caught in the stock serial handler’s “unknown command” exit
$67BEversion text “CF4”
 
The idea is to fix the problems, then for those that want to connect the RS232 port of the ASC1 to the RS232 port of the FTA receiver, provide an onscreen display of movement and positioner counts.

I do not know how much of this I can make into reality. The edited software may not even boot. We will see....
 
I've got one but currently use it as a spare. It developed a bad transformer hum that I was unable to fix and it's simply too noisy but that is certainly the best non commercial mover I've seen. Titanium built it like a tank.
 
Psyched! Wondering what tool decompiled the firmware, or if you were afforded the source.
Meanwhile. For those who roll your own. Just needs a relay with the footprint that you can fit in the gearbox housing.
A RT114024 would probably work. Check the datasheet for dimensions. Amazon to Mouser, Digi Key.
R1 is the braking resistor. It could be anything around 1 Ohm. 0.22 would be fine. 5, probably a bit high.
R2 is probably not needed. If the voltage while the actuator is powered is close to 24 volts. Golden. This relay coil spec. is 400 mA @ 24 volts DC
Keep the from-controller wiring and to-the motor-wires the same as the rest of them. Wago, wire nuts to the motor before the limit switches.
You can solder wires directly to the relay pins. Then make a barrier with tape around the relay body and cover the wiring with hot glue.
Mines been working over 2 years. Those who know, know.

Dynamic Brake With Limits.webp
 
EB, do you think it's possible to recover an ASC1 that got stuck halfway through a flash attempt? I have a board lying around that I'm hoping can still be salvaged.
 
Cannot guarantee anything, but most likely, yes. It will depend on what happened. Most likely though, if it died in the middle of a firmware flash and was "healthy" before that, it can be recovered.
 
Spent the evening and morning working on this system. i guess it is about 90 percent complete. Flashed 2 ASC1 units. Did not brick either one. Flashed one ASC1 twice due to an update. Beautiful running system. Log file attached. The dreamone has Onscreen Display of the dish moving. I am very happy with this. Log file for the evening is attached. (No Pulse Count Errors For Me!.)

asc1-moving-dreamone_20261122062118.webp
 

Attachments

Back
Top