Suport for SV6301A / SV4401A
- oxoocoffee
- Posts: 15
- Joined: Sat 16. Aug 2025, 15:21
Re: Suport for SV6301A / SV4401A
Hello.
I updated your app from AppStore and running version 1.3.1 using SV6301A VNA.
I connect to it as NanoVNA-F V2. It gets the band range ok. I can perform scan and it looks good.
When I take a screenshot I get corrupted screen like this. I also have NanoVNA-F V3 which I will try to run and will report my findings. Would it be possible to add the devices to the menu list after we get it working?
73.
I updated your app from AppStore and running version 1.3.1 using SV6301A VNA.
I connect to it as NanoVNA-F V2. It gets the band range ok. I can perform scan and it looks good.
When I take a screenshot I get corrupted screen like this. I also have NanoVNA-F V3 which I will try to run and will report my findings. Would it be possible to add the devices to the menu list after we get it working?
73.
Re: Suport for SV6301A / SV4401A
There is no command for the screenshot in my manual for this device. So I don't know how it works.
73 and best dx de Tom, DL2RUM
- oxoocoffee
- Posts: 15
- Joined: Sat 16. Aug 2025, 15:21
Re: Suport for SV6301A / SV4401A
Hello, Any plans in upcoming update to have these models in the menu? and also -F v3 as well?
73,
73,
- oxoocoffee
- Posts: 15
- Joined: Sat 16. Aug 2025, 15:21
Re: Suport for SV6301A / SV4401A
Maybe add the following models to the list and if selected, disable screenshot button for now, to prevent user confusions and reports?
73,
73,
- oxoocoffee
- Posts: 15
- Joined: Sat 16. Aug 2025, 15:21
Re: Suport for SV6301A / SV4401A
Hello
I like to report few things. I am running VNAMAte version Version 1.6 (14)
I see that the unit I have SV6301A is not in the supported list. Is there anything I can help with and provide additional data to help add this unit to official support? My VNA currently is running version 0.7.3.
It seems I can scan file using NAnoVNA-F v2. And I can scan a 1001 points. The graph looks correct. SWR and Smith Chart.
I have a couple additional questions beside the above support.
1. I have Auto Marker check in the list. Should the Auto marker follow the mouse move over the chart? If yes, it is not moving and it is sick at one place (A in the circle), clicking on it or trying to drag using any mouse buttons does not do anything. I did checked Manual section regarding the marker and I do not see explanation how it should work.
2. Same for any markers that I additionally check 1 - 4. They just show up with vertical line and label at the bottom. But I can not move any of them. While writing this post, I realized that Auto Marker can be moved using the horizontal slider
Would it be possible to move mouse freely in the VSWR chart with out pressing any mouse buttons, and detect when you hovering over the marker vertical line and change mouse icon when over the line with some +/- margin, so user could click on it and while holding down a mouse button, he could move the marker?
3. Should each enabled marker have its own slider in your design? With all the respect, the slider is less intuitive to me, but I am sure there are others who might like it? If number 2. could be considered, maybe add option to hide the slider for folks who like to change directly in the chart?
4. Is there a way to enable a reference chart? When making antenna adjustment, I would like to take a current snapshot, make some changes while it is running, comeback and take a snapshot, and visually compare them? Maybe up to four or more references if the host machine resources permit?
5. I also did experienced a crash, when I did open and tried the Multi Band Stimulus.
My device band is 1.8 to 29.7 MHz. I opened the Multi Band Window, selected a band for each section and clicked Run. I did see the "led" next to connect blinking in red / green (I think) really fact, nothing was drawn in that window, and after some seconds, it did crashed.
Looks like String parsing?
73,
I like to report few things. I am running VNAMAte version Version 1.6 (14)
I see that the unit I have SV6301A is not in the supported list. Is there anything I can help with and provide additional data to help add this unit to official support? My VNA currently is running version 0.7.3.
It seems I can scan file using NAnoVNA-F v2. And I can scan a 1001 points. The graph looks correct. SWR and Smith Chart.
I have a couple additional questions beside the above support.
1. I have Auto Marker check in the list. Should the Auto marker follow the mouse move over the chart? If yes, it is not moving and it is sick at one place (A in the circle), clicking on it or trying to drag using any mouse buttons does not do anything. I did checked Manual section regarding the marker and I do not see explanation how it should work.
2. Same for any markers that I additionally check 1 - 4. They just show up with vertical line and label at the bottom. But I can not move any of them. While writing this post, I realized that Auto Marker can be moved using the horizontal slider
Would it be possible to move mouse freely in the VSWR chart with out pressing any mouse buttons, and detect when you hovering over the marker vertical line and change mouse icon when over the line with some +/- margin, so user could click on it and while holding down a mouse button, he could move the marker?
3. Should each enabled marker have its own slider in your design? With all the respect, the slider is less intuitive to me, but I am sure there are others who might like it? If number 2. could be considered, maybe add option to hide the slider for folks who like to change directly in the chart?
4. Is there a way to enable a reference chart? When making antenna adjustment, I would like to take a current snapshot, make some changes while it is running, comeback and take a snapshot, and visually compare them? Maybe up to four or more references if the host machine resources permit?
5. I also did experienced a crash, when I did open and tried the Multi Band Stimulus.
My device band is 1.8 to 29.7 MHz. I opened the Multi Band Window, selected a band for each section and clicked Run. I did see the "led" next to connect blinking in red / green (I think) really fact, nothing was drawn in that window, and after some seconds, it did crashed.
Code: Select all
Triggered by Thread: 0, Dispatch Queue: com.apple.main-thread
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x0000000189d6f6b4
Termination Reason: Namespace SIGNAL, Code 5, Trace/BPT trap: 5
Terminating Process: exc handler [95819]
Code: Select all
Application Specific Backtrace 0:
0 CoreFoundation 0x00000001851c31c0 __exceptionPreprocess + 176
1 libobjc.A.dylib 0x0000000184c3e91c objc_exception_throw + 88
2 CoreFoundation 0x0000000185140798 -[__NSCFString hasSuffix:] + 0
3 VNAmate 0x00000001047d7d48 VNAmate + 32072
4 AppKit 0x00000001896b7354 -[NSTableView _dataSourceValueForColumn:row:] + 160
5 AppKit 0x00000001897a645c -[NSTableView preparedCellAtColumn:row:] + 396
6 AppKit 0x00000001897a6198 -[NSTableView _drawContentsAtRow:column:withCellFrame:] + 68
7 AppKit 0x00000001897a5d60 -[NSTableView drawRow:clipRect:] + 1184
8 AppKit 0x00000001897a56a0 -[NSTableView drawRowIndexes:clipRect:] + 680
9 AppKit 0x00000001897444d0 -[NSTableView drawRect:] + 1140
10 AppKit 0x0000000189ab550c __getCGDisplayListGetHashSymbolLoc_block_invoke + 1516
11 AppKit 0x0000000189ab5534 __getCGDisplayListGetHashSymbolLoc_block_invoke + 1556
12 AppKit 0x0000000189a7b40c block_destroy_helper + 12608
13 AppKit 0x0000000189a7ba28 block_destroy_helper + 14172
14 AppKit 0x000000018969b354 _NSViewDrawRect + 132
15 AppKit 0x000000018a2bbe0c -[NSView _recursive:displayRectIgnoringOpacity:inContext:stopAtLayerBackedViews:] + 1084
16 AppKit 0x000000018969ad64 -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 536
17 AppKit 0x0000000189f6c1f4 -[NSViewBackingLayer drawInContext:] + 56
18 AppKit 0x0000000189ad8098 _NSCGDisplayListGetHash + 900
19 AppKit 0x0000000189ad8cf8 _NSCGDisplayListGetHash + 4068
20 AppKit 0x0000000189b73fc0 block_destroy_helper.34 + 6024
21 AppKit 0x0000000189b74414 block_destroy_helper.34 + 7132
22 AppKit 0x0000000189f6be14 -[NSViewBackingLayer display] + 1284
23 QuartzCore 0x000000018f1a87e4 _ZN2CA5Layer17display_if_neededEPNS_11TransactionE + 784
24 QuartzCore 0x000000018f355d38 _ZN2CA7Context18commit_transactionEPNS_11TransactionEdPd + 620
25 QuartzCore 0x000000018f189520 _ZN2CA11Transaction6commitEv + 652
26 QuartzCore 0x000000018f3872bc _ZN2CA11Transaction25flush_as_runloop_observerEb + 140
27 AppKit 0x0000000189ec40c8 stepTransactionFlush + 220
28 UpdateCycle 0x000000027d0f92f4 _ZN2UC10DriverCore18continueProcessingEv + 84
29 CoreFoundation 0x0000000185154314 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36
30 CoreFoundation 0x0000000185154210 __CFRunLoopDoObservers + 648
31 CoreFoundation 0x0000000185226204 _CFRunLoopRunSpecificWithOptions + 484
32 HIToolbox 0x0000000191f3f560 RunCurrentEventLoopInMode + 320
33 HIToolbox 0x0000000191f428bc ReceiveNextEventCommon + 488
34 HIToolbox 0x00000001920cc14c _BlockUntilNextEventMatchingListInMode + 48
35 AppKit 0x0000000189c363d0 _DPSBlockUntilNextEventMatchingListInMode + 228
36 AppKit 0x000000018958a084 _DPSNextEvent + 576
37 AppKit 0x000000018a11f96c -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688
38 AppKit 0x000000018a11f678 -[NSApplication(NSEventRouting) nextEventMatchingMask:untilDate:inMode:dequeue:] + 72
39 AppKit 0x000000018957d13c -[NSApplication run] + 368
40 AppKit 0x00000001895557b0 NSApplicationMain + 880
41 dyld 0x0000000184ccc4e4 start + 6992
Application Specific Backtrace 1:
0 CoreFoundation 0x00000001851c31c0 __exceptionPreprocess + 176
1 libobjc.A.dylib 0x0000000184c3e91c objc_exception_throw + 88
2 CoreFoundation 0x0000000185140798 -[__NSCFString hasSuffix:] + 0
3 VNAmate 0x00000001047d7d48 VNAmate + 32072
4 AppKit 0x00000001896b7354 -[NSTableView _dataSourceValueForColumn:row:] + 160
5 AppKit 0x00000001897a645c -[NSTableView preparedCellAtColumn:row:] + 396
6 AppKit 0x00000001897a6198 -[NSTableView _drawContentsAtRow:column:withCellFrame:] + 68
7 AppKit 0x00000001897a5d60 -[NSTableView drawRow:clipRect:] + 1184
8 AppKit 0x00000001897a56a0 -[NSTableView drawRowIndexes:clipRect:] + 680
9 AppKit 0x00000001897444d0 -[NSTableView drawRect:] + 1140
10 AppKit 0x0000000189ab550c __getCGDisplayListGetHashSymbolLoc_block_invoke + 1516
11 AppKit 0x0000000189ab5534 __getCGDisplayListGetHashSymbolLoc_block_invoke + 1556
12 AppKit 0x0000000189a7b40c block_destroy_helper + 12608
13 AppKit 0x0000000189a7ba28 block_destroy_helper + 14172
14 AppKit 0x000000018969b354 _NSViewDrawRect + 132
15 AppKit 0x000000018a2bbe0c -[NSView _recursive:displayRectIgnoringOpacity:inContext:stopAtLayerBackedViews:] + 1084
16 AppKit 0x000000018969ad64 -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 536
17 AppKit 0x0000000189f6c1f4 -[NSViewBackingLayer drawInContext:] + 56
18 AppKit 0x0000000189ad8098 _NSCGDisplayListGetHash + 900
19 AppKit 0x0000000189ad8cf8 _NSCGDisplayListGetHash + 4068
20 AppKit 0x0000000189b73fc0 block_destroy_helper.34 + 6024
21 AppKit 0x0000000189b74414 block_destroy_helper.34 + 7132
22 AppKit 0x0000000189f6be14 -[NSViewBackingLayer display] + 1284
23 QuartzCore 0x000000018f1a87e4 _ZN2CA5Layer17display_if_neededEPNS_11TransactionE + 784
24 QuartzCore 0x000000018f355d38 _ZN2CA7Context18commit_transactionEPNS_11TransactionEdPd + 620
25 QuartzCore 0x000000018f189520 _ZN2CA11Transaction6commitEv + 652
26 QuartzCore 0x000000018f3872bc _ZN2CA11Transaction25flush_as_runloop_observerEb + 140
27 AppKit 0x0000000189ec40c8 stepTransactionFlush + 220
28 UpdateCycle 0x000000027d0f92f4 _ZN2UC10DriverCore18continueProcessingEv + 84
29 CoreFoundation 0x0000000185154314 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36
30 CoreFoundation 0x0000000185154210 __CFRunLoopDoObservers + 648
31 CoreFoundation 0x0000000185226204 _CFRunLoopRunSpecificWithOptions + 484
32 HIToolbox 0x0000000191f3f560 RunCurrentEventLoopInMode + 320
33 HIToolbox 0x0000000191f428bc ReceiveNextEventCommon + 488
34 HIToolbox 0x00000001920cc14c _BlockUntilNextEventMatchingListInMode + 48
35 AppKit 0x0000000189c363d0 _DPSBlockUntilNextEventMatchingListInMode + 228
36 AppKit 0x000000018958a084 _DPSNextEvent + 576
37 AppKit 0x000000018a11f96c -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688
38 AppKit 0x000000018a11f678 -[NSApplication(NSEventRouting) nextEventMatchingMask:untilDate:inMode:dequeue:] + 72
39 AppKit 0x000000018957d13c -[NSApplication run] + 368
40 AppKit 0x00000001895557b0 NSApplicationMain + 880
41 dyld 0x0000000184ccc4e4 start + 6992
73,
Re: Suport for SV6301A / SV4401A
Please e-mail me the full crash report. Use the Console app and drag and drop the report into Mail. Do not just copy and paste the text!
73 and best dx de Tom, DL2RUM
- oxoocoffee
- Posts: 15
- Joined: Sat 16. Aug 2025, 15:21
Re: Suport for SV6301A / SV4401A
Since you like to use "!" to make your point
I like to make mine. Please state somewhere explicitly and easily visible to the user, what is your preferred way to handle such case! 
I will send you logs a bit later.
73m],
I will send you logs a bit later.
73m],
Re: Suport for SV6301A / SV4401A
Just use the macOS Crash Reporter to send reports to Apple. Add few useful information to reproduce the issue or what you have done when it happened. This should be the preferred way for all applications.Please state somewhere explicitly and easily visible to the user, what is your preferred way to handle such case!
73 and best dx de Tom, DL2RUM
Re: Suport for SV6301A / SV4401A
- You can set the markers 1-4 using the contextual menu from a result table entry.
- Well, this was my first approach. Improvements are always possible.
- This should be an idea for future versions.
73 and best dx de Tom, DL2RUM