COM Schnittstelle wird nicht erkannt

[Heinz-S]

Hello Armando,

you will find attached in Pic1 and Pic2 the answers of the LFEP on the commands #:GV# and #:VS#.

When I started SerialMon and afterwards the LFEP starter utility the error message in Pic3 appears. Starting RealTerm and then the LFEP driver the same message was displayed (Pic5). It seems, that both applications couldn't run together at the same time.

So I used the LFEP starter utility quite alone. In opposite to the first modified driver, this time the progress bar runs till its end, but the handbox was not displayed. Instead the message in Pic4 could be seen.

CS
Heinz

[Armando]

Hi Heinz,

you will find attached in Pic1 and Pic2 the answers of the LFEP on the commands #:GV# and #:VS#.

I suggested to send #:GV# just to let you figure out how RealTerm works (you can see your FW is 5.88 Rev.B - each ASCII character is displayed also in Hex).
Anyway RealTerm now is properly configured.

When I started SerialMon and afterwards the LFEP starter utility the error message in Pic3 appears. Starting RealTerm and then the LFEP driver the same message was displayed (Pic5). It seems, that both applications couldn't run together at the same time.

SerialMon is obviously to be set to sniff traffic (View->Preferences->Cable connection-> Software monitoring).
RealTerm will never be able to communicate to LFEP while LFEP is connected by ASCOM. This is  the same reason why I suggested to use FocusMax to have many clients able to control LFEP. SerialMon, while sniffing, will show you the traffic between LFEP and the only one connected client (LFEP ASCOM server).

So I used the LFEP starter utility quite alone. In opposite to the first modified driver, this time the progress bar runs till its end, but the handbox was not displayed. Instead the message in Pic4 could be seen.

I fixed #0:VX# but something wrong occurs later. I need a SerialMon log.

CS
Armando

[Heinz-S]

Hello Armando,

in the attachment you will find two log – files. The first file had been created with the LFEP in non-operating state. The second file shows the situation of LFEP after starting up the tracking. I hope, that these informations are helpfully.

CS
Heinz

[Armando]

Hi Heinz,

I hope, that these informations are helpfully.

Yes 

Ok, I modified the code and I think now the handbox should be properly shown...
Unfortunately the code sent by Gerald about #0:VX# command is not good for your firmware.  I need to decipher the answer by LFEP to #0:VX# command in several LFEP states (synced/not synced, tracking/not tracking, slewing/not slewing, East/West Pier side).
I mean to make the driver working. But, before going on, please let me know if the handbox now is displayed. If you don't see the ASCOM handbox or if you see the driver "freezes" please send me SerialMon logs...

CS
Armando

[Heinz-S]

Hello Armando,

unfortunately I can't report the appearance of the ASCOM handbox. The progress bar again runs properly, but at it's end the error messages shown in Pic1 and Pic2 appeared.

So I recorded the two attached SerialMon Logs, the first again in LFEP non operating state, the second in tracking mode.

Good luck!
Heinz

[Armando]

Hi Heinz,

OK, I found no communication issues in the logs but I think a pair of unhandled exceptions occurred that could be the cause of the crash.
Please let me know if the handbox appears...
Obviously keep the option "Show handbox on connection" (Telescope->Setup) enabled.

CS
Armando

[Heinz-S]

Hooray Armando,

the handbox appeared (Pic1 and Pic2). As you recommended me, I didn't test any presented command. Let me know, what's to do next.

CS
Heinz

[Armando]

OK Heinz,

you can make some tests still by the ASCOM handbox.
Click on Show Meridian Flip and start giving a look at pointing state and side of pier:
1. power on LFEP, connect and check them;
2. sync on any object by the hardware handbox and check if they change accordingly;
3. click on Invert Dec and check if side of pier changes;
4. send a GoTo command by the HW handbox, make the HW handbox not showing the coords (just to exclude possible issues), and check if ASCOM  slewing led blinks. It should not blink when slewing has finished (you can stop slewing simply by the hardware handbox by a click on any moving button...).

You can move the trackbar located next to Silent checkbox in the middle to reduce the ASCOM state polling period (i.e. to increase the ASCOM polling rate, to reduce the delay that occurs between a LFEP state change by the HW handbox and its detection by the ASCOM driver).

You can also check if reported PEC state is right playing the same way by the HW handbox (to check if the reported PEC state changes accordingly...).
Keep in mind the detection delay...

Please let me know... 

CS
Armando

[Armando]

Heinz, keep also in mind I disabled Sidereal/Solar/Lunar rate distinction. Also all setting commands won't work.
I gave higher priority to LFEP states required to make the driver working.
So make the tests described in my previous message.
Later on we'll try to make everything else working, if possible.

CS
Armando

[Heinz-S]

Hello Armando,

after syncing on some objects the information under “Pointing state” changed from East to West. Also the coords, shown in the information window, are changing accordingly. The information under “Side of pier” didn't change, neither on sync commands nor on slewing the mount by HW handbox.

A click on “InvertDEC” also didn't change the “side of pier” state.

After sending a goto command the slewing led starts blinking, but it goes on to blink after stopping the movement. Also after a few minutes the blinking was displayed. In my manual, I couldn't find a command, that allows a modification of the HW handbox, not showing the coords after a goto movement.

The PEC state didn't change. Any time I could read “Active” and “Valid”.The button right beside it displayed “PEC off”. A click on it does not change it to “PEC on”.

CS
Heinz

[Armando]

Hi Heinz,

after syncing on some objects the information under “Pointing state” changed from East to West. Also the coords, shown in the information window, are changing accordingly. The information under “Side of pier” didn't change, neither on sync commands nor on slewing the mount by HW handbox.

OK.

A click on “InvertDEC” also didn't change the “side of pier” state.

Not OK.
#>D# (resp. #<D#) are used to set East (resp. West) side of pier.
So Sync on any object by the handbox and use RealTerm (no ASCOM connection) to communicate to LFEP and:
1. send #>D# (to set East side of pier) and #0:VX# and tell me the answer;
2. send #<D# (to set West side of pier) and #0:VX# and tell me the answer...
I'll try to figure out how to recognize the side of pier...

After sending a goto command the slewing led starts blinking, but it goes on to blink after stopping the movement. Also after a few minutes the blinking was displayed.

Not OK.
Use Realterm and tell me the answer to #0:VX# command while mount is slewing and while it's not slewing...

In my manual, I couldn't find a command, that allows a modification of the HW handbox, not showing the coords after a goto movement.

OK, I modified the driver in the past and so it should be able to manage/discard unwanted data coming from the handbox (sent by LFEP itself while the handbox display is showing current coords).

The PEC state didn't change. Any time I could read “Active” and “Valid”.The button right beside it displayed “PEC off”. A click on it does not change it to “PEC on”.

Not OK.
To read PEC state you should use #:VS# command (always by RealTerm) in place of #0:VX#.
So you should change PEC state by the HW handbox, send #:VS# and tell me the answer (while PEC is Off, while PEC is ON and finally during PEC training).

You can use RealTerm screen shots to report the answers...

CS
Armando

[Heinz-S]

Hello Armando,

in the attachments you will find three screen shots, that are returned on the RealTerm commands:

Screen shot 1:
Line 1 was returned after the Sync on an object by the HW handbox.
Line 2 and 3 are the results of sending #>D# (#<D#) and then #0:VX#

Screen shot 2:
I started the mount slewing and send #0:VX#. After some seconds I stopped the mount by a click on a moving button of the HW handbox. Although the mount was tracking now (not slewing) the screen writing goes on. So the first package of characters was displayed.

After sending #0:VX# for the second time (during the mount was tracking), the second package was created. I stopped the writing on the screen by disconnecting the LFEP with a push on the On/Off button.

Screen shot 3:
Here you will find the answers of the LFEP on the #:VS# command while PEC is off (line 1), while PEC is on (line 2) and while PEC training is enabled (line 3).

CS
Heinz

[Armando]

Hi Heinz,

to be sure I need also the answer to #0:VX# when LFEP is not synced and not slewing (after it has only been powered on, with no sync and no GoTo commands...).
Anyway probably the attached driver works...
As for PEC state, please let me know the answer to #0P and #1P .

CS
Armando

[Heinz-S]

Hello Armando,

in screen shot 1 you can see the answer of the LFEP on #0:VX#, after it has only been powered on.

To test PEC state, I sent #0P and #1P always three times to the LFEP, after setting by HW handbox PEC OFF, PEC ON and PEC TRAINING. Every time I missed the answer. RealTerm only displayed my input (screen shot 2).

Your new driver reacts very pleasant. A click on INVERT DEC changes Side of pier accordingly, also corresponding on the HW handbox.

I synced an object with the HW handbox and started a GOTO to a second object. The slewing led started blinking. At the end of the movement, the blinking stops and a sound could be heard.

The PEC on/off button now is reacting, the ACTIVE letters turned from grey to black, also corresponding to the HW handbox (red LED is on). That is also working the reverse way. If I change a PEC function by HW handbox, these changes are displayed on the screen. The same behaviour could be observed by PEC TRAINING.

CS
Heinz

[Armando]

Hi Heinz,

OK. 
I still need a confirmation: while keeping N (resp. S) button pressed you should see DEC increasing (resp. decreasing). This should happen both on East and West pier sides.
Please let me know if you see something different: I need to figure out if FW5 is affected by the same bug as FW6 and if I have to reverse West/East pier sides...

If you see N/S buttons working as expected then you can start using the driver...
Keep in mind currently you can't configure your LFEP by ASCOM!
As for the parking feature, please don't use the Controller parking but prefer the PC parking (you can select it in the parking settings group)! You can try to set home position and see if parking/unparking works as expected.
You can also enable automatic flip if you see manual flip works.

But before playing with parking and flip commands you need to be sure N/S buttons move the mount in the right direction...

As for the moving speeds, You should be able to move by the ASCOM handbox at guider rate, 2X, 8X and 16X paddle speeds.
I don't know all the other speeds that are supported by FW5. So, if you agree with me, I could simply remove all the other speeds from the list to let you select only hand paddle speeds (you should associate any of the available speeds at each of the hand paddle speed)... You can also tell me the speeds supported by FW5 but then we should check if the selection works as in FW6...

CS
Armando

[Armando]

Hi Heinz,

I'd like also to know LFEP answer to #0:VX# after you've set tracking rate to Sidereal, Solar, Lunar, User and Disabled by the HW handbox...

CS
Armando

[Heinz-S]

Hello Armando,

the bug, you've told about, couldn't be seen by using my equipment.  The N button pressing lets increase DEC display on east and west pier side.

The parking commands and the flip functions I couldn't test previously, but I send feedback to you in the near future.

To configure the LFEP, the HW handbox does a good job and ASCOM is not necessary.

The moving speeds 2x, 8x and 16x are functioning properly. I also tested some of the other offered speeds (100x, 250x, 320x). The mount moves every time with the same speed (16x paddle), but the stored GOTO speed changes from 250x to 32x anyway. As you proposed, it would be the best to remove all these other speeds.

In the attachment you will find the RealTerm answers to the several tracking rates: Line 1: sideral, Line 2: solar, Line 3: lunar, Line 4: disabled. A user mode wasn't offered in the tracking rate menu of the HW handbox.

In the description of the driver for FW6xx I found a function, that allows to synchronize the date/time of the LFEP control unit with the PC clock. Is that function also available by FW5xx driver?

CS
Heinz

[Armando]

Hi Heinz,

the bug, you've told about, couldn't be seen by using my equipment.  The N button pressing lets increase DEC display on east and west pier side.

Well... FW5 is affected by the same bug and, as hoped, the code that manages FW6 bug is good also with your LFEP. 

The parking commands and the flip functions I couldn't test previously, but I send feedback to you in the near future.

OK.

To configure the LFEP, the HW handbox does a good job and ASCOM is not necessary.

I agree with you. 

The moving speeds 2x, 8x and 16x are functioning properly. I also tested some of the other offered speeds (100x, 250x, 320x). The mount moves every time with the same speed (16x paddle), but the stored GOTO speed changes from 250x to 32x anyway. As you proposed, it would be the best to remove all these other speeds.

OK. As you can see by the warning message, using the other menu speeds, even if possible on FW6, is not a good idea. So I really see no limitations in this case...

In the attachment you will find the RealTerm answers to the several tracking rates: Line 1: sideral, Line 2: solar, Line 3: lunar, Line 4: disabled. A user mode wasn't offered in the tracking rate menu of the HW handbox.

OK. I'll have also to hide drift compensation groups for FW5.

In the description of the driver for FW6xx I found a function, that allows to synchronize the date/time of the LFEP control unit with the PC clock. Is that function also available by FW5xx driver?

I kept it enabled and probably FW5 supports the required commands. You can check (by intentionally and temporarily setting a wrong date/time on your PC...).
Please let me know if it doesn't work: I can hide the checkbox...

CS
Armando

[Armando]

Hi Heinz,

OK, I just built a new driver. You find it attached...
You should see only paddle speeds in the handbox, no drift compensation and no user rate available and Sidereal/Solar/Lunar tracking rate properly detected.

CS
Armando

[Armando]

Please use the attached driver...