LittleFoot Elegance Photo > LFEP ASCOM
COM Schnittstelle wird nicht erkannt
Heinz-S:
Hello Armando,
I've not tested the new driver intensely, but here's a little feedback.
You removed the controller parking feature successfully. Only the PC parking display appears.
The handbox only shows the paddle speeds. Drift compensation and user rate aren't available. The clicks on the several tracking rates are confirmed by the LFEP immediately.
The synchronization function is only working partially. The date information was applied perfectly. The PC time unfortunately was not detected by LFEP.
For testing I clicked all displayed setup functions one at a time. The only function, that returns an error message was “Extras”. You can see it in the attachment.
CS
Heinz
Armando:
Hi Heinz,
--- Quote from: Heinz-S on Thursday, 06.03.14 - 17:19:41 - CET ---The synchronization function is only working partially. The date information was applied perfectly. The PC time unfortunately was not detected by LFEP.
--- End quote ---
By RealTerm in ASCII MODE (RealTerm Display group - display as Ascii) send #:SL13:14:15# to set 13:14:15 as local time...
Then send #:GL# to read LFEP local time and check if it really updated its time...
Then use the attached driver, enable the log panel and also the date/time synchronization. Disconnect, reconnect and give a look at the log.
You should find a logged message like time to save: .......
I need to know the exact logged message. Also a screen-shot of the ASCOM handbox is fine...
--- Quote ---For testing I clicked all displayed setup functions one at a time. The only function, that returns an error message was “Extras”. You can see it in the attachment.
--- End quote ---
The attached driver manages the issue.
Later on I'll disable the unsupported setting commands. Anyway now you should have no issues while "accessing" unsupported features but don't play with them...
CS
Armando
Heinz-S:
Hello Armando,
using the implemented driver, I set the time to 13:14:15 (screen-shot 1). The HW-handbox then also displays that time.
After updating to the new driver the message “time to save” appears as represented in screen-shot 2. The HW-handbox only shows the updated time from the first setting (13:48:34).
My last test, that returns the error message by clicking on “Extras” should only be a hint. The message still occurs (screen-shot 3). Please spend no more time in those functions, you'll disable later.
The manual flip function reacts properly. The automatic flip I've not tested yet.
The parking feature is also functioning very well. I can set a parking position. The mount is slewing to that position by clicking the parking button. A click to “Unpark” sets the mount in tracking mode.
Using my preferred application program “Eye & Telescope” combined with the LFEP driver, the mount is moving to the chosen objects. If I try to adjust the object position in the middle of the ocular by HW handbox, the PC screen freezes. Is it not allowed, to use the HW handbox buttons during a connection to an application program? Or could it be possible, that my PC hardware hasn't enough performance?
CS
Heinz
Armando:
Hi Heinz,
the attached driver should solve the Extra and Date/time sync issues.
--- Quote from: Heinz-S on Saturday, 08.03.14 - 18:47:11 - CET ---
Using my preferred application program “Eye & Telescope” combined with the LFEP driver, the mount is moving to the chosen objects. If I try to adjust the object position in the middle of the ocular by HW handbox, the PC screen freezes. Is it not allowed, to use the HW handbox buttons during a connection to an application program? Or could it be possible, that my PC hardware hasn't enough performance?
--- End quote ---
With FW6 I had only to make the driver managing the unexpected data coming from LFEP while slewing by the HW handbox or while the HW handbox is showing the coords.
Maybe with FW5 LFEP simply doesn't answer at all to received commands while an handbox button is being pressed. ::)
You can check by RealTerm: send #:GV# or let's say #:GD# (to read current LFEP Declination) while pressing any HW handbox button and check if the expected answer appears.
You can also send a SerialMon log to let me figure out if the lock occurs on a specific command (start the connection and later on keep an HW handbox pressed). I need to figure out if this limitation can be managed by the driver...
CS
Armando
Armando:
As for GoToFlip and ParkFlip I suggest to use them currently only for test/debug purposes..
Currently I can't test it: my slewing speed is too low.
the_lizardking, who is is testing the driver, told me that it doesn't work as expected. ::)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version