Hi all,
as some of you know Osmo-fl2k has a bothersome software issue that sometimes just stop transmitting without any good reason. in my case when I was transmitting WBFM sometimes it may stop transmitting. I mean the RF output will be interrupted completely without any error or warnings on screen and I should re-execute the commands to transmit again and this goes on and on. sometimes it may work without any issues for like 10 min and sometimes it may fail after just a few seconds. the problem also appeared in executing <fl2k_file> when I was transmitting DVB-T.
you can watch this video to gain a better understanding: https://www.youtube.com/watch?v=G0tjzPHFFA8
I have no idea if this issue been discussed earlier in the mailing list or not, anyway I didn't find anything useful by Googling.your comments and suggestions are greatly appreciated. Regards,Sajjad
Hi Sajjad,
no, this issue doesn't seem related to any other topic that I can remember lately – I've seen wonder why a non-transmitting test didn't transmit, but no reports of sudden breakdowns.
Your video is about 13 minutes longer than I'd like – can you pinpoint at which time in that video your transmission stops?
As usual, debugging on the side of the observing party might very well be helpful here. Figure out whether the program halts (a software debugger, e.g. gdb, would be the appropriate tool), the USB transfers stop (wireshark might be helpful here), or whether just something happens inside the device while the computer and software happily continue to work. Observing the spectrum might help. Describe whether the signal just disappears, or changes in a manner that makes reception of DVB-T impossible. Isolate the sources of error – start with a much less complex signal, typically a single sine wave that you can easily observe.
All in all, what we'd need to help you is a complete error description.
Best regards, Marcus
On Wed, 2018-06-13 at 18:38 +0000, Sajjad Golchin poor wrote:
Hi all,
as some of you know Osmo-fl2k has a bothersome software issue that sometimes just stop transmitting without any good reason. in my case when I was transmitting WBFM sometimes it may stop transmitting. I mean the RF output will be interrupted completely without any error or warnings on screen and I should re-execute the commands to transmit again and this goes on and on. sometimes it may work without any issues for like 10 min and sometimes it may fail after just a few seconds. the problem also appeared in executing <fl2k_file> when I was transmitting DVB-T.
you can watch this video to gain a better understanding: https://www. youtube.com/watch?v=G0tjzPHFFA8
I have no idea if this issue been discussed earlier in the mailing list or not, anyway I didn't find anything useful by Googling. your comments and suggestions are greatly appreciated.
Regards, Sajjad
Hi Sajjad,
On 13.06.2018 20:38, Sajjad Golchin poor wrote:
as some of you know Osmo-fl2k has a bothersome software issue that sometimes just stop transmitting without any good reason. in my case when I was transmitting WBFM sometimes it may stop transmitting. I mean the RF output will be interrupted completely without any error or warnings on screen and I should re-execute the commands to transmit again and this goes on and on. sometimes it may work without any issues for like 10 min and sometimes it may fail after just a few seconds. the problem also appeared in executing <fl2k_file> when I was transmitting DVB-T.
you can watch this video to gain a better understanding: https://www.youtube.com/watch?v=G0tjzPHFFA8
This will happen if the host cannot supply enough data to the device, you need to use a lower sample rate in this case, or get rid of a hypervisor like VMware, as is the case in this video.
When operating as a normal graphics adapter, the frame would be skipped when an underflow happens and the screen flickers, however, when HSYNC/VSYNC is disabled the device completely stops and needs to be re-initialized. There seems to be a 'frame loss' mechanism to detect this in through an interupt transfer, but I haven't implemented this yet and have no idea if this works with disabled synchronization.
Anyway, there seems to be something wrong with your setup. Either host controller, or host controller driver etc. What setup are you using (OS, host controller, any virtualization present like in the video?)
Regards, Steve
-
Müller, Marcus (CEL) -
Sajjad Golchin poor -
Steve Markgraf