32 replies to this topic

[jlarysz]

OzAndrew:  I ran the AudioStar through the diagnostic cycle twice. It worked exactly as you describe except it did not reboot itself at the end, it just cycled through the keypad test again. I did not see a "Fail" on the RTS232 test, so I'm guessing the unit is fine - which is definitely a good thing. 

 

Now I'm waiting for a new USB - RS232 cable; I should have it tomorrow.

 

I totally appreciate you help here. None of this stuff is in the manual.

[OzAndrewJ]

Gday jlarysz

Its a simple test that sends ascii "0","1","2"..."9"

out and receives it back.

If any send fails, you get a beep and "Fail"

If you got no beep and fail with rs232 then the Hbx is working.

( and that makes me happier as i couldnt understand

how both the Hbx and the converter could be faulty )

 

None of this stuff is in the manual

Correct, and some of it varies between firmwares.

There are lots of hidden QC type functions, but most arent useful for general use.

I had actually forgotten about this test as i was assuming you had the classic 497

and it has no proper inbuilt diagnostics.

 

Andrew Johansen Melbourne Australia

 

PS will have a look at the A1F7 code re not rebooting

as i tested on a 5CE1 ( 497EP ) hbx

Edited by OzAndrewJ, 11 December 2022 - 03:38 PM.

[jlarysz]

Fixed it! A new Amazon choice usb-serial cable worked as expected. 

 

The old cable was made by Oikwan, and was about 18 months old. That seems like a short life span for a cable.

[jlarysz]

Thanks you OzAndrew for all the effort you in on helping me. It was above and beyond.

[jlarysz]

Thanks you OzAndrew for all the effort you in on helping me. It was above and beyond.

[OzAndrewJ]

Gday jlarysz

The old cable was made by Oikwan, and was about 18 months old

What chipset did it have

Lots of people recently report problems with their converters

if windoze overwrites the specific drivers.

Reloading the old drivers seems to fix it for most

but FTDI based drivers seem to be the most bullet proof at present.

 

Andrew Johansen Melbourne Australia

[Skywatchr]

Gday jlarysz

What chipset did it have

Lots of people recently report problems with their converters

if windoze overwrites the specific drivers.

Reloading the old drivers seems to fix it for most

but FTDI based drivers seem to be the most bullet proof at present.

 

Andrew Johansen Melbourne Australia

I still use my oldie but goodie Keyspan model USA-19HS up to and including Win10.  Win10 finds it and loads it's own driver for it. I don't run Win11 so I can't comment about that.

It was made for Win98/ME/2000, and XP (newest at the time), MAC OS8.6 or higher, and MAX OSX 10.2 or greater, and works with Linux.  I still have a new one as a spare.

[jlarysz]

Both the old and new cables have the FTDI chip set. In tried reloading the drivers with the old cable; it didn't help.