oacapture/oalive 1.8.0 released

[Pete6]

Here is the output of lsusb with and without the QHYCCD PoleMaster. 

Edit: I turned off the power to a 4 port hub to kill the PoleMaster.  This explains why two devices went down when I cut the PoleMaster's power.  If you need this done differently, please say.

With:

Bus 002 Device 003: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge
Bus 002 Device 002: ID 03c3:224a  
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 009: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 008: ID 0ac8:3520 Z-Star Microelectronics Corp. 
Bus 001 Device 007: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 005: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 012: ID 1618:0941  
Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 

 

Without:

Bus 002 Device 003: ID 174c:55aa ASMedia Technology Inc. Name: ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge, ASM1153E SATA 6Gb/s bridge
Bus 002 Device 002: ID 03c3:224a  
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 009: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 008: ID 0ac8:3520 Z-Star Microelectronics Corp. 
Bus 001 Device 007: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 005: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I hope this helps.

 

Thanks again

Pete

Edited February 26, 2021 by Pete6

[Pete6]

You may be right about how the PoleMaster is being mounted.  I have been play with the configuration a little.  I have a set of relays at the bottom of my pier that allow me remotely to turn various  devices on my telescope.  Because of the problem I was having with the PoleMaster I put in onto its own relay.  If I power up my rig with the PoleMaster power at boot time I can access it and it works.  I can also cut the power to the PoleMaster with no problem but I cannot turn it back on again.  If I do the astroberry Pi 4 crashes and needs a power cycle to recover.  This too is repeatable.  Turning off/on the OnStep controller works as does power cycling the myFocuser, camera heaters (no USB connection, obviously) all work fine.

Maybe these observations will help point you to a solution.

[JamesF]

I don't think this can be a configuration problem then.  As far as the configuration is concerned there should be no difference between the device being connected at boot time or reconnecting later on.  That the RPi crashes when the camera is reconnected makes it sound like it could be some sort of hardware issue, but I thought those were all ironed out now.

Probably my next step would be to remove all the QHY packages from the RPi and try powering down and reconnecting the PoleMaster again.  If that still crashes the RPi then it does look like an OS/hardware issue.  If it doesn't cause a crash then we'll need to find a way to debug what's going on somehow.

James

[Pete6]

I'll need to get back to you in a day or so as I'm in the middle of a few other mods right now.  I have a spare RPi that I can load  a virgin copy of astroberry so that should give me a clean test environment.  One I have that I shall play Lego bricks with t e configuration until I break it.  More on this in a few days.

 

Cheers

Pete

[Peter Rosen]

Hi James,

I am on Mac OSX 10.9.5.

Some 2-3 years ago I  bought the ASI 120MC and discovered oaCapture which worked fine for me for a while.

I borrowed an ASI 1600 cooled mono camera and caught some Tiff-frames in 8 bits. When I switched to 16 bits, oaCapture crashed.

Every new version of oaCapture since then have all crashed upon startup so I finally gave up.

I have a new ASI 462 color camera and yesterday I downloaded oaCapture 1.8.0 and... success... it worked!

I am now able to capture Ser, Avi, Tiff... but only in 8 bit. Since the camera is 12 bits I would like to capture the higher bits.

In the camera settings, I ticked "Force Input Frame Format "RGB48LE" and also tried "RGB48BE" as well as "RGB36LE/BE" but the Tiff files I get are all 8 bits only.

Could you please guide me here to the correct way to proceed,

Thanks

/*Peter R