RUMlogNG version 5.9

[DL2RUM]

RUMlogNG 5.9 is available for direct download here:
https://dl2rum.de/RUMlogNG/RUMlogNG.zip
Available in the App Store: https://itunes.apple.com/app/rumlogng/id964454561?mt=12

English manual: https://dl2rum.de/RUMlogNG/docs/en/
German manual: https://dl2rum.de/RUMlogNG/docs/de/

• Fix: Scoring in ARRL Digi Contest - Tnx Mike, AG7AB
• Fix: CW keying in the ExpertSDR3 software - Tnx David, CT1DRB
• New: Native support for FlexRadio 6xxx, incl. CW Keyer - Tnx Georg, DJ6GI für a loaner device
• New: Support for Icom Remote Encoder RC-28
• New: SpotToSunFlex App integrated
• New: More options for DX-Spots in the Icom scope
• New: CW Mode selection when Flrig is in use
• New: Florida QSO Party

[hb9hnu]

Rumlog crash when i try to put something in "Callsign" .I had no problem before this bug

Nom du modèle : iMac
Identifiant du modèle : iMac18,3
Nom du processeur : Intel Core i7 quatre cœurs
Vitesse du processeur : 4.2 GHz
Nombre de processeurs : 1
Nombre total de cœurs : 4
Cache de niveau 2 (par cœur) : 256 Ko
Cache de niveau 3 : 8 Mo
Technologie Hyper-Threading : Activé
Mémoire : 32 Go
Version du programme interne du système : 451.120.7.0.0
Version du chargeur de système d’exploitation : 540.120.3~6

Process: RUMlogNG [5265]
Path: /Applications/RUMlogNG.app/Contents/MacOS/RUMlogNG
Identifier: de.dl2rum.RUMlogNG
Version: 5.9 (534)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2022-07-12 19:05:12.8963 +0200
OS Version: macOS 12.4 (21F79)
Report Version: 12
Anonymous UUID: 8D5BFB2D-A23F-B618-2B58-330C2C282FAE


Time Awake Since Boot: 6200 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: NSManagedObjectContext 0x600001af7a80

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4
Terminating Process: exc handler [5265]

Application Specific Information:
BUG IN CLIENT OF LIBDISPATCH: dispatch_sync called on queue already owned by current thread
Abort Cause 9005618706776320


Thread 0 Crashed:: Dispatch queue: NSManagedObjectContext 0x600001af7a80
0 libdispatch.dylib 0x7ff8020aeabd __DISPATCH_WAIT_FOR_QUEUE__ + 409
1 libdispatch.dylib 0x7ff8020ae696 _dispatch_sync_f_slow + 170
2 RUMlogNG 0x10e05683c 0x10d837000 + 8517692
3 CoreData 0x7ff808263e8e developerSubmittedBlockToNSManagedObjectContextPerform + 158
4 libdispatch.dylib 0x7ff8020a1317 _dispatch_client_callout + 8
5 libdispatch.dylib 0x7ff8020ae7ee _dispatch_lane_barrier_sync_invoke_and_complete + 60
6 CoreData 0x7ff808263da5 -[NSManagedObjectContext performBlockAndWait:] + 277
7 RUMlogNG 0x10e056585 0x10d837000 + 8516997
8 RUMlogNG 0x10dcb9761 0x10d837000 + 4728673
9 RUMlogNG 0x10dcb99da 0x10d837000 + 4729306
10 RUMlogNG 0x10d9def33 0x10d837000 + 1736499
11 RUMlogNG 0x10d9c1ce1 0x10d837000 + 1617121
12 CoreFoundation 0x7ff80231475c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12

[hb9hnu]

5.9 installed but same bug for me...

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process: RUMlogNG [3302]
Path: /Applications/RUMlogNG.app/Contents/MacOS/RUMlogNG
Identifier: de.dl2rum.RUMlogNG
Version: 5.9 (534)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2022-07-13 18:16:23.7854 +0200
OS Version: macOS 12.4 (21F79)
Report Version: 12
Anonymous UUID: 8D5BFB2D-A23F-B618-2B58-330C2C282FAE


Time Awake Since Boot: 3100 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: NSManagedObjectContext 0x600003bfc340

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4
Terminating Process: exc handler [3302]

Application Specific Information:
BUG IN CLIENT OF LIBDISPATCH: dispatch_sync called on queue already owned by current thread
Abort Cause 9005618706776320


Thread 0 Crashed:: Dispatch queue: NSManagedObjectContext 0x600003bfc340
0 libdispatch.dylib 0x7ff815b16abd __DISPATCH_WAIT_FOR_QUEUE__ + 409
1 libdispatch.dylib 0x7ff815b16696 _dispatch_sync_f_slow + 170
2 RUMlogNG 0x109e6183c 0x109642000 + 8517692
3 CoreData 0x7ff81bccbe8e developerSubmittedBlockToNSManagedObjectContextPerform + 158
4 libdispatch.dylib 0x7ff815b09317 _dispatch_client_callout + 8
5 libdispatch.dylib 0x7ff815b167ee _dispatch_lane_barrier_sync_invoke_and_complete + 60
6 CoreData 0x7ff81bccbda5 -[NSManagedObjectCo
------------
Model: iMac18,3, BootROM 451.120.7.0.0, 4 processors, Quad-Core Intel Core i7, 4.2 GHz, 32 GB, SMC 2.41f2
Graphics: Radeon Pro 580, Radeon Pro 580, PCIe, 8 GB
Display: iMac, Retina 5K (5120 x 2880), Main, MirrorOff, Online
Memory Module: BANK 0/DIMM0, 8 GB, DDR4 SO-DIMM, 2400 MHz, 0x802C, 0x3841544631473634485A2D324733423220202020
Memory Module: BANK 0/DIMM1, 8 GB, DDR4 SO-DIMM, 2400 MHz, 0x859B, 0x4354384734534644383234412E433136464600
Memory Module: BANK 1/DIMM0, 8 GB, DDR4 SO-DIMM, 2400 MHz, 0x802C, 0x3841544631473634485A2D324733423220202020
Memory Module: BANK 1/DIMM1, 8 GB, DDR4 SO-DIMM, 2400 MHz, 0x859B, 0x4354384734534644383234412E433136464600
AirPort: spairport_wireless_card_type_wifi (0x14E4, 0x16F), Broadcom BCM43xx 1.0 (7.77.111.1 AirPortDriverBrcmNIC-1710.3)
AirPort:
Bluetooth: Version (null), 0 services, 0 devices, 0 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: APPLE HDD ST2000DM001, 2 TB
USB Device: USB3.0 Hub
USB Device: USB3.0 Hub
USB Device: USB30Bus
USB Device: USB2.0 Hub
USB Device: USB2.0 Hub
USB Device: Bluetooth USB Host Controller
USB Device: FaceTime HD Camera (Built-in)
USB Device: Back-UPS RS 900G FW:879.L4 .I USB FW:L4
Thunderbolt Bus: iMac, Apple Inc., 41.5

[DL2RUM]

Send me the full crash report as file from the Console app by drag & drop. Do not use copy & paste.

[LA0FA]

with the latest 5.9.1. I have had an endless stream of crashes this weekend ... I just downloaded the 5.10 test version and no crashes observed so far. 73 de LA0FA

[BG6LH]

Dear Tom!

I am using RUMlogNG on my macbook pro, as a main logging service.
the RUMlog was connect to flrig via TCP/UDP.
flrig is running on a raspberry Pi, which connet to my YAESU FTDX10, as a main CAT control server.
they are working well.

the flrig was config to a CW keyer. So, I can play CW via fldigi, both on my macbook and RPI, all of them are clients the flrig on rpi.

now I'm wondering how to play CW via RumLogNG to flrig, just like fldigi can do...
I am trying to set the "Preference/CW/CW interface" to transceiver, but it was saying "isn't supported for CW keying"...
if am I on wrong way?

Thanks! BG6LH

[DL2RUM]

I'm wondering how to play CW via RumLogNG to flrig, just like fldigi can do...

The flrig control functions are too limited for a useful operation. A WinKeyer is strongly recommended for serious CW.

[BG6LH]

I do agree with you about serious CW should be using a winkeyer.
I have a K3NG keyer. I can play it when RUMLogNG connect to my rig directly.

However in my case I have to operation my rig remotely in most time. so I have to made a config like this figure shown:



I am thinking, how to play CW in local? now the only way is from VNC to remote Fldigi...