I'm developing a new version of the dragonfly driver for indi, and I'm facing a strange issue. When I connect to the dragonfly all comands I'm sending are ok, but after some minutes, or if i disconnect and connect again, when I send a command, the dragonfly's response seems to be related for another command, is like they are mixing, and then the lights of the switches are incorrect
in this example, the response for the command !relio rldgrd 0 1# is related to !relio snanrd 0 6, so I'm asking for the state of a relay, and dragonfly is answering a sensor analog state ...
I've tried with the current release of the dragonfly's driver, and the same is happening. I've added in the bool DragonFlyDome::sendCommand
a flush withtcflush(PortFD, TCIFLUSH);before and after the execution of the command, but without luck, the issue persists. I've added a method to check if the command is related to the answer, and if not, I'm closing the connection and connection again, which works but seems not elegant...tcpConnection->Disconnect();
tcpConnection->Connect();any help would be apreciated
I want to develop an improved version for the DragonFly controller, so that I can send a pulse to open and close the roof when that dragonfly relay is configured to send a pulse. Now it only opens the relay until the sensor is closed, which no works in all scenarios.
I am getting the data from each relay correctly, but now I want to change the label of each relay, so instead to show "Relay #1", the driver shows "Lights", for example. But I'm not able to change the layer of the switch vector, in this page seems that there's a function to change the label
error: no member named 'setLabel' in '_ISwitchVectorProperty'
can anyone give me some indications?
Hi, installing twice for me did the work... "Do note that you might have to install it twice for it to work, as the first install will just remove the existing driver. If it's installed, there should be a "SiLabsUSBDriver.kext" file in /Library/Extensions with a date created of June 16, 2017.". It's not wotking for you? I'm on macOS High Sierra 10.13.6
for others with this issue, I solved it on OSX thanks to this page:
As discussed in the following thread, it appears the v5.x SiLabs driver is completely broken.
Fortunately the v4.x driver, which is included in the "Legacy MacVCP Driver" folder in the same download, works fine. Do note that you might have to install it twice for it to work, as the first install will just remove the existing driver. If it's installed, there should be a "SiLabsUSBDriver.kext" file in /Library/Extensions with a date created of June 16, 2017.
Every time I try to connect, kstars crash with my previous reported log, so I'm unable to use the sesto senso 2 focuser with kstars. Anyone else with this issue?
on osx high sierra 10.13.6, kstars crashes when trying to connect to senso 2:
Process: kstars 
Version: 3.4.2 (3.4.2)
Code Type: X86-64 (Native)
Parent Process: ??? 
Responsible: kstars 
User ID: 501
Date/Time: 2020-06-12 19:06:08.025 +0200
OS Version: Mac OS X 10.13.6 (17G65)
Report Version: 12
Anonymous UUID: 78AA750A-47EC-FF60-7CDC-E9AF4F34CF4D
Time Awake Since Boot: 1600 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000001
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler 
VM Regions Near 0x1:
__TEXT 00000001025de000-0000000103110000 [ 11.2M] r-x/r-x SM=COW /Applications/KStars.app/Contents/MacOS/kstars
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 0x0000000102eec420 INDI::BaseDevice::getRawProperty(char const*, INDI_PROPERTY_TYPE) + 64
1 0x000000010272cbe3 0x1025de000 + 1371107
2 org.qt-project.QtCore 0x00000001058c0552 0x1056a0000 + 2229586
3 0x000000010269bc6f 0x1025de000 + 777327
4 0x00000001026a86cd 0x1025de000 + 829133
5 org.qt-project.QtCore 0x00000001058b8c4d QObject::event(QEvent*) + 957
6 org.qt-project.QtWidgets 0x00000001049c0b5d QApplicationPrivate::notify_helper(QObject*, QEvent*) + 269
7 org.qt-project.QtWidgets 0x00000001049c1f95 QApplication::notify(QObject*, QEvent*) + 581
8 org.qt-project.QtCore 0x000000010588e804 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212
9 org.qt-project.QtCore 0x000000010588f8b3 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 691
10 libqcocoa.dylib 0x0000000108a30052 QCocoaEventDispatcherPrivate::processPostedEvents() + 322 (qcocoaeventdispatcher.mm:888)
11 libqcocoa.dylib 0x0000000108a30758 QCocoaEventDispatcherPrivate::postedEventsSourceCallback(void*) + 40
12 com.apple.CoreFoundation 0x00007fff2f421d31 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
13 com.apple.CoreFoundation 0x00007fff2f4d960c __CFRunLoopDoSource0 + 108
14 com.apple.CoreFoundation 0x00007fff2f404d3c __CFRunLoopDoSources0 + 300
15 com.apple.CoreFoundation 0x00007fff2f40415d __CFRunLoopRun + 1293
16 com.apple.CoreFoundation 0x00007fff2f4039b7 CFRunLoopRunSpecific + 487
17 com.apple.HIToolbox 0x00007fff2e6e3d96 RunCurrentEventLoopInMode + 286
18 com.apple.HIToolbox 0x00007fff2e6e3a0f ReceiveNextEventCommon + 366
19 com.apple.HIToolbox 0x00007fff2e6e3884 _BlockUntilNextEventMatchingListInModeWithFilter + 64
20 com.apple.AppKit 0x00007fff2c994a73 _DPSNextEvent + 2085
21 com.apple.AppKit 0x00007fff2d12ae34 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
22 com.apple.AppKit 0x00007fff2c989885 -[NSApplication run] + 764
23 libqcocoa.dylib 0x0000000108a2f5c8 QCocoaEventDispatcher::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 2648 (qcocoaeventdispatcher.mm:430)
24 org.qt-project.QtCore 0x000000010588a97f QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 431
25 org.qt-project.QtCore 0x000000010588ee52 QCoreApplication::exec() + 130
26 0x00000001025f2a63 0x1025de000 + 84579
27 libdyld.dylib 0x00007fff5731a015 start + 1
For any others have this isuse, I can connect to the sesto senso 2 after install this driver, on osx 10.14.6:
Hi all! just received the sesto senso 2, but is not connecting on kstars 3.4.3 on an osX computer.
2020-05-08T16:36:50: [INFO] Debug is enabled.
2020-05-08T16:36:49: [ERROR] Failed to connect to port (/dev/cu.Bluetooth-Incoming-Port). Error: Port failure Error: Resource busy. Check if device is connected to this port.
2020-05-08T16:36:49: [INFO] Trying connecting to /dev/cu.Bluetooth-Incoming-Port @ 115200 ...
2020-05-08T16:36:48: [WARNING] Communication with /dev/cu.usbserial @ 115200 failed. Starting Auto Search...
2020-05-08T16:36:48: [ERROR] Failed to connect to port (/dev/cu.usbserial). Error: Port failure Error: Resource busy. Check if device is connected to this port.
The camera is well attached to the guide scope, and the guide scope is well attached to the main scope, there's no movement, it's like a single block. Anyway, repeating from one day to another the same PA routine gives me exactly the same values for main and guide scope (+-2' / +-9'), if it was flexure the value for guide scope the PA error would never be the same?
focal length: 1280 mm
camera: canon EOS 4000D
sensor size: 22.3 x 14.9 mm
sensor resolution: 5184 x 3456
pizel size: 4.29
focal length: 230 mm
camera: QHY 5L-II Mono
sensor size: 1/3 inch
sensor resolution: 1280 x 960
pizel size: 3.75
one doubt: on the main scope I'm not taking pictures at full resolution, I'm taking pictures at 2592x1728. These are the values that I've write in the indi control panel, both for "Image settings" and "image info":
I've been using kstars and ekos during lasts months, and I'm in love with it. I'm always do the polar alignment routine with the main optical tube (c8 with 6.3 focal reducer), but last night I tried with the guidescope , and there's significative differences... With the main scope ekos gives me a polar error of 2' 13"