Crashes with indi on Raspberry Pi with ASI120MM/MC: Page 2

Crashes with indi on Raspberry Pi with ASI120MM/MC

Sam@ZWO

dokeeffe wrote:
Sam,

Are you sure releasing the source will not help? My camera was working perfect up to a few weeks ago.

I have not made any changes other than updating the INDI drivers which were compiled against your latest SDK.

Regarding:: set the "USB BANDWIDTH" to minimal value

I have a feeling that this call, from the INDI driver through your SDK is not functioning as it used to. Could you please take a look? Or just let us have a look at the code?

Thanks.

Derek

Hi Derek

there did have one bug of setting "USB Bandwidth" we will fix it soon

universalmaster

Sam wrote:

"compatibility" firmware is only used to fix the problem host doesnot recongize it

the old firmware has the best performance, so please flash it back and feed back

I tried to flash the original firmware and then the camera does not work with the RPi at all. I tried to take an exposure from the shell, using indi_setprop, and take an exposure from PixInsight, but both exposures failed. This is the output from indiserver when PixInsight was taking an exposure:

pi@observatory:~ $ indiserver indi_asi_ccd 2016-12-29T12: startup: indiserver indi_asi_ccd 2016-12-29T12: Driver indi_asi_ccd: recorder: setpixelformat 1195528775 2016-12-29T12: Driver indi_asi_ccd: recorder: setsize 1280x960 2016-12-29T12: Driver indi_asi_ccd: recorder: setsize 1280x960 2016-12-29T12: Driver indi_asi_ccd: recorder: setsize 1280x960 2016-12-29T12: Driver indi_asi_ccd: stderr EOF 2016-12-29T12: Driver indi_asi_ccd: restart #1 Child process 4285 died 2016-12-29T12: select(9): Interrupted system call 2016-12-29T12: good bye

Now, back to the compatibility firmware to make it work again.

Sam@ZWO

universalmaster wrote:
Sam wrote:

"compatibility" firmware is only used to fix the problem host doesnot recongize it

the old firmware has the best performance, so please flash it back and feed back

I tried to flash the original firmware and then the camera does not work with the RPi at all. I tried to take an exposure from the shell, using indi_setprop, and take an exposure from PixInsight, but both exposures failed. This is the output from indiserver when PixInsight was taking an exposure:
pi@observatory:~ $ indiserver indi_asi_ccd
2016-12-29T12: startup: indiserver indi_asi_ccd
2016-12-29T12: Driver indi_asi_ccd: recorder: setpixelformat 1195528775
2016-12-29T12: Driver indi_asi_ccd: recorder: setsize 1280x960
2016-12-29T12: Driver indi_asi_ccd: recorder: setsize 1280x960
2016-12-29T12: Driver indi_asi_ccd: recorder: setsize 1280x960
2016-12-29T12: Driver indi_asi_ccd: stderr EOF
2016-12-29T12: Driver indi_asi_ccd: restart #1
Child process 4285 died
2016-12-29T12: select(9): Interrupted system call
2016-12-29T12: good bye
Now, back to the compatibility firmware to make it work again.

got it. then PI3 only support "compatible firmware"

universalmaster

Sam wrote:

got it. then PI3 only support "compatible firmware"

PI3??? I use Raspberry Pi 2b. "Funny" thing is that it worked fine 6 months ago with the "original" firmware. If it is not changes to the indi_asi_ccd driver, could it then be changes to the linux kernel that ruins it for us?

Sam@ZWO

universalmaster wrote:
Sam wrote:

got it. then PI3 only support "compatible firmware"

PI3??? I use Raspberry Pi 2b. "Funny" thing is that it worked fine 6 months ago with the "original" firmware. If it is not changes to the indi_asi_ccd driver, could it then be changes to the linux kernel that ruins it for us?

that's weird, new update of linux kernel may cause this, did you update your kernel?

you can run dmesg to check what kernel says when you plugin the camera

the only difference between old firmware and new firmware is the size of endpoint

the "original" firmware set the endpoint size to 1024 and compatible firmware set it to 512

some kernel may don't accept 1024 size of endpoint

yang

I've update our SDK in indi driver on Github, and test on Raspberry Pi2 with ASI120MM, 8bit frame now works.

universalmaster

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

yang

a customer reported that he restore raspi image from November and the camera worked fine again:

http://zwoug.org/viewtopic.php?f=17&t=6718, maybe you can have a try.

Sam@ZWO

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

universalmaster

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

universalmaster

Here is a 24 hour movie with one image pr minute with the "new" driver:

https://drive.google.com/open?id=0B182-tJ-4ZQtZHB2bjk5V2tYUlE

as you can see, there are some glitches every now and then. It seems to me that the glitches occur most frequently when I am changing the exposure time and/or gain. If I run with the same exposure time and gain for a long time it does not seem to happen so often. Anyways, it is not perfect but it is much more stable that when I started this post

olivia545

I am using Google drive for store files and it is really the best platform for free files storage service but from few days I am getting Google drive server error, I also searched on the internet and I got to know that this kind of error occurs due to server issue Can anyone tell me the valid reason and also any suggestion to solve this issue?

chad

olivia545 wrote:

I am using Google drive for store files and it is really the best platform for free files storage service but from few days I am getting Google drive server error, I also searched on the internet and I got to know that this kind of error occurs due to server issue Can anyone tell me the valid reason and also any suggestion to solve this issue?

I think it is too long ago, so the file had been deleted.

Thanks

Chad

« Previous Page