Open overbog opened 9 months ago
@SpaceCadet1249 The build uses the same code as the repo, there's nothing changed. Are you able to try the old version see if the Rig Control works in your specific setup ? If not then it's not supported by cubic sdr and probably need support from the maintainer. And probably you need to do some troubleshooting first like debugging what's coming out from serial and try with different baud rate see if that's help.
And it appears @mg1011 can use rig control and has no problem.
@radito This is the first build that I could get to run on my MacBook M2, since all the others crashed on startup. I believe there's some kind of problem with the SoapySDR library since its reception is very weak compared to SDRconnect. For instance WWV on 15mhz tonight (on the Yaesu) was 10 points above S9, yet I could not even hear it using CubicSDR. And every time I start the CubicSDR I must DELET the config file in order to start the SDRplay box. It's not a counterfeit, but the real RSP1b device. I'm sorry, but I'm not a programmer and wouldn't know how to debug the serial port. I'm using 9600 baud N81. Matching settings on my Yaesu FTDX-1200. If I should be looking at another thread for this, please point me to it. thanks
@cts409
For the build i'm including the library from the official SDRPlay website the version is SDRplayAPI-macos-installer-universal-3.14.0.pkg
From your case it seems the soapySDR hasn't detected the SDR and probably the the clone is not supported by this API ? I'm not so sure can you try this specific api version in sonoma and do the probe again ?
Works. Thanks!
@cts409 If you're interested, here's a short video of SDRplay trying to initialize. Bear in mind it tries to come up with the RF frequency set to zero. I have tried setting it to, say 15Mhz before initializing, but get the same results. To exit the program at this point, I have to do a Forced quit. The only way I can get it to initialize is to blow away the config.xml file AND unplug and replug the SDRplay USB cable. Then it can initialize again. First is a picture where you can see the SDRplay is actually detected. Then next there's the video. If you unmute the speaker you can hear my narration.
https://github.com/cjcliffe/CubicSDR/assets/164538664/9d4bc062-5940-4101-924b-6f1311c84cec
@cts409 @radito @mg1011 When I finally found a USB > UART cable that worked, all these other problems went away. For details on which two cables I've found that work, and why, please see #1028 I've been using CubicSDR version 0.2.8-4-Darwin-Arm64 RELIABLY for over a week now. Thanks!
@sidewinder666
can you try
brew install soapysdr soapyrtlsdr
see if that helps ?
This solved the issue for me.
@radito Thanks for all the effort to make something available for ARM64.
I've followed so far on a Apple M3 Pro with Sonoma 14.5, but had no final success. Is there some further advice?
CubicSDR.0.2.8-aarch64.dmg
works using Open
manually as describedSoapySDRUtil --probe
but doing brew install soapysdr soapyrtlsdr
lists my device (I have a Nooelec NESDR SMArTee v2
:
SoapySDRUtil --probe
######################################################
## Soapy SDR -- the SDR abstraction library ##
######################################################
Probe device Found Rafael Micro R820T tuner [INFO] Opening Generic RTL2832U OEM :: 00000001... Found Rafael Micro R820T tuner
driver=RTLSDR hardware=R820T index=0 origin=https://github.com/pothosware/SoapyRTLSDR
Channels: 1 Rx, 0 Tx Timestamps: YES Time sources: sw_ticks Other Settings:
Full-duplex: NO Supports AGC: YES Stream formats: CS8, CS16, CF32 Native format: CS8 [full-scale=128] Stream args:
- Still, there is no such SDR device, if I start the application
<img width="1327" alt="Screenshot 2024-05-23 at 07 59 21" src="https://github.com/cjcliffe/CubicSDR/assets/307481/79e0fe27-ad0b-4cff-b8e4-4edb6d68c448">
@jforge are you using the latest release ?
0.2.8-4 Latest
It looks like you're using CubicSDR.0.2.8-aarch64.dmg
not the dash 4
@radito Thanks for the hint, you're right, I grabbed the 0.2.8-aarch64
from elsewhere.
With 0.2.8-4
everything looks fine from my side.
Hello:
That version is working fine for me too.
Thanks!
Vic
On May 29, 2024, at 2:04 AM, jforge @.***> wrote:
@raditohttps://github.com/radito Thanks for the hint, you're right, I grabbed the 0.2.8-aarch64 from elsewhere.
With 0.2.8-4 everything looks fine from my side.
Screenshot.2024-05-29.at.11.00.28.png (view on web)https://github.com/cjcliffe/CubicSDR/assets/307481/92675d46-a4df-432f-a611-efa1ad0e468c
— Reply to this email directly, view it on GitHubhttps://github.com/cjcliffe/CubicSDR/issues/1011#issuecomment-2136913228, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BHHKSKBY7T76AC2DWPGNFWLZEWK2XAVCNFSM6AAAAAA5T54TNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZWHEYTGMRSHA. You are receiving this because you were mentioned.Message ID: @.***>
Crashes at startup:
Crashed Thread: 4 Dispatch queue: CA DispatchGroup
Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000024a Exception Codes: 0x0000000000000001, 0x000000000000024a
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [17843]