• Get involved.
    We want your input!
    Apply for Membership and join the conversations about everything related to broadcasting.

    After we receive your registration, a moderator will review it. After your registration is approved, you will be permitted to post.
    If you use a disposable or false email address, your registration will be rejected.

    After your membership is approved, please take a minute to tell us a little bit about yourself.
    https://www.radiodiscussions.com/forums/introduce-yourself.1088/

    Thanks in advance and have fun!
    RadioDiscussions Administrators

AutoPilot 2.3

S

SamBuca

Guest
Welp...Burk is stumped so now I ask everyone. When loading autopilot, it says "Unable to load DLL" with "APLogin" as the source. Win2k service pack 4, AutoPilot v2.3.

At the very least I'm seeing the data stream in hyperterminal so I got the null modem pinouts correct.<P ID="signature">______________
</P>
 
Off the wall but....

Software with Burk has always been a "down the rabbit hole" experience for me.

I was recently involved in the partial installation of a completely new system, replacing one that was over 10 years old and worked perfectly. Why? I dunno.
Maybe the station had money to spend....

It's partial because the programming of "watchdogs", etc. is beyond arcane,
nothing like previous versions, and they keep promising a more user-friendly
version very soon. Last time I heard "very soon" was in July.

Point is, there are incompatibilities between the newer versions of software
and hardware that isn't very new...latest and greatest versions. If by
"loading" you mean getting your setup out of the computer into the Burk,
you may have a software/hardware incompatibility. Even if the control
unit and the software arrived in the same box, sounds like it might be good
to look hard at board versions and be sure they're compatible with the
software. Especially if the software is the very Latest & Greatest, new
since perhaps July.

You are infinitely sharper than am I about the various versions of Windows
but if you're taling about just getting their software off CD and into the computer, I'd be looking at the real system requirements for the particular
software they delivered...what versions of Windows it expects to work with.

I love the Burk hardware...damn near bulletproof....but their software
people seem to arrive weekly from some other planet or even perhaps a new
planet every week! Highly unlikely they were ever anything but software
gurus with little empathy for those of us who are only moderately computer
literate!
<P ID="signature">______________
In Christianity neither morality nor religion come into contact with reality at any point.
--Friedrich Nietzsch</P>
 
Re: Off the wall but....

Burk was showing Autopilot 3.0 at the radio show in Philly a few weeks ago. Previous (windows) version users can upgrade for less than the full price but I don't remmeber what that was.

They do now support the style of scripting like that from the DOS versions (a script wizard).

For me? Still stuck with the DOS version of Autopilot - and loving it, actually.

Joe



>>>>
It's partial because the programming of "watchdogs", etc. is beyond arcane,
nothing like previous versions, and they keep promising a more user-friendly
version very soon. Last time I heard "very soon" was in July.
<<<<
 
Re: Off the wall but....

> Software with Burk has always been a "down the rabbit hole"
> experience for me.

Now it suddenly works....but it says it can't access the ARC-16. I'm seeing the datastream in hyperterminal.

Dear Burk,

Please release the protocol for the unit so that I may write my own software. It would take LESS TIME than troubleshooting yours.

Sincerely,

Me<P ID="signature">______________
</P>
 
Follow up

Looks like it's a problem with the security code...it won't accept it.

I will be thoroughly upset if I have to reprogram the entire unit.<P ID="signature">______________
</P>
 
Re: Follow up

> Looks like it's a problem with the security code...it won't
> accept it.
>
> I will be thoroughly upset if I have to reprogram the entire
> unit.
>

You don't need to reprogam the unit if you have a security code issue. Just change the code on the remote ARC-16 and you'll be set.

Now, if it's caused by corrupt firmware, that's a different story.<P ID="signature">______________
</P>
 
Re: Follow up

> You don't need to reprogam the unit if you have a security
> code issue. Just change the code on the remote ARC-16 and
> you'll be set.

Did they change the procedure in firmware v5.6 or did I kill off those brain cells at the bar last night?<P ID="signature">______________
</P>
 
Status
This thread has been closed due to inactivity. You can create a new thread to discuss this topic.


Back
Top Bottom