LFEP ASCOM driver - bug reports

[Armando]

Hi the_lizardking,

I have some problems with the focuser,... seems that the fast mode does not work... cant use it.

try to use the focuser with "Enable silent mode" checked; you find the option by a click on focuser setup (position tab). I hope it helps.

CS
Armando

[gpaolo]

Ciao gpaolo,

Anyway, I noticed that, after the window "Telescope is parked" appears, the setup window does not refresh and remains as if the telescope were not parked. To have the Unpark button available, I have to close the setup window and open it again.

Please let me know if the attached driver solves the issue. ;-)

CS
Armando

Thanks! I will try it as soon as I can!

[the_lizardking]

I had the silent mode activated, so maybe thats the problem,... I will try today and let you know.

[Armando]

Hi the_lizardking,

I had the silent mode activated, so maybe thats the problem,... I will try today and let you know.

I hope you're referring to the Silent mode that can be enabled next to the ASCOM handbox. If so, then disable it... ;-)
The Silent mode I was referring to is the one available in the focuser setup (Position tab). If enabled, it reduces traffic while focusing.
I suggested Rajiva to implement this focusing mode to solve a limitation that made FAST focusing not possible at all with LFEP connection over Ethernet. It can obviously be used also when connection is over USB/RS232 and frankly I see no reason why it should be disabled (the only thing to note is that this mode is not Robofocus compliant).

CS
Armando

[the_lizardking]

No i mean the one in Focuser Setup,...
This one was selected,... I will try other way round today, maybe there is some issue but let me test first.

[gpaolo]

Hi Armando, sorry if I disappeared, but between vacations and bad weather I was able to use the telescope just a few days ago.
The driver now works perfectly to me, thanks for looking into that!   

[Armando]

Hi @all,

I noticed last night that a click on North (ASCOM handbox) button made the mount moving to the South.
Even if I've no access to my mount now, I can modify the code to manage this issue.
But I need someone can make the following tests:
1. Check if ASCOM N button moves the mount to S;
2. Press N & S buttons at the same (on the hardware handbox, not the ASCOM one);
3. Check if ASCOM N button still moves the mount to S.

It's a good idea to repeat the test after a change of SideOfPier.

Please let me know.

CS
Armando

P.s. There is no need to make a test under the sky: you can simply check if Dec coordinates (shown by ASCOM handbox panel) increases/decreases while keeping N button pressed...

[Armando]

Ok,
I just checked. The command to move to N moves to S if PierSide is East; and the command to move to S move to N if PierSide is East.
In a few words if PierSide is East the mount moves in the wrong direction...
The attached driver solves this LFEP bug. 

But now I'm in doubt: maybe pulseGuide command is affected by a similar bug!
I can't really check it. I'll gladly appreciate a confirmation. This possible bug could be related to the issues found by gpaolo...
When a flip occurs there is no need to recalibrate the guider. But we need to know if the controller takes into account the change of PierSide when executing the PulseGuide command... In case of bug I can make the controller executing a PulseGuide command in the opposite direction to solve the issue... But I need a confirmation...
The required test is the following one:
1. calibrate the guider;
2. make a flip;
3. start guiding without guider recalibration and check if the tracking error on Dec is properly managed.

Thank you!
Armando

[Armando]

Ok,

I made another test by a JS script. North and South PulseGuide commands work as the N and S moving commands: a North PulseGuide makes Dec decreasing on East SideOfPier (and increasing on West SideOfPier).

This working mode can be the right one for PulseGuide: if guider calibration is made only on one side, after a pier flip the reverse (let's say "wrong") motion caused by a PulseGuide command will automatically manage the occurred flip...
But the guiding software is to be properly configured since this implementation of PulseGuide is not ASCOM compliant.

As for example, If you're using Maxim DL you have to enable Auto Pier Flip (in guide panel) and Reverse X in Guider Motor Control settings (Guider advanced settings) to eliminate the need of new guider calibrations after a flip...

CS
Armando

[drknoppi]

Hello Armando,

today i tried to test your new driver from Nov. 4 th.
Thank  you very much !!!!
The direction N,S,E,W now are correct , but the pier side is the opposite of the side
i can read in my Handbox.
HB is "W"  and ascom driver says "E" , its my issue ?

Best regards Rainer

b.t.w. attachment sun from today 

[Armando]

Hi Rainer,

HB is "W"  and ascom driver says "E" , its my issue ?

What is the real side of pier?

CS
Armando

[Armando]

Hi Rainer,

if the SideOfPier reported by the HB was wrong I think the attached driver can solve the issue.
To test it you have to change rotation on Dec. If you're using normal mode on Dec then set reverse mode; if you're using reverse mode on Dec then set normal one.
Please change Dec rotation by the HB (Display menu -> Controller -> Mount Setup -> Axis Dir -> Dec -> ...) and then connect the controller by ASCOM.
While testing the driver (mainly GoTo, flip and parking commands) please be ready to stop the mount in case of need!

Thank you for your help!
Armando

[drknoppi]

Hello Armando -
o.k. so i will do it after rain stops  tomorrow morning !
Thank you !
Regards Rainer

[Armando]

Hi Rainer,

I made other small changes and uploaded the new driver on SourceForge:
http://sourceforge.net/projects/lfepascom/files/LFEP%20ASCOM%20Driver%20%281.5.3%20Beta%29.exe/download

I hope you'll find it working as expected.

Thank you again and Clear Skies!
Armando

[drknoppi]

Hello Armando, because of to much rain drops in the air,
I will Test the new driver on Weekend - i will report the result .
B.t.w  a Great digital Click with startime - Local time would be fine
inside the LFEP -Controll panel
Best regards Rainer .

[Armando]

Hi Rainer,

B.t.w  a Great digital Click with startime - Local time would be fine
inside the LFEP -Controll panel

Local hour angle is already shown. What do you mean by star time?

CS
Armando

[drknoppi]

Hallo Armando,
Local Hour angle is o.k., you are right,
But a nice digital clock black background and
Red digits  mmmh,
Best regards
Rainer

B.t.w. Many rain drops , to many 

[Armando]

Hi Rainer,

in the meantime I applied other changes to improve the driver.
I'm trying to make the (hardware) handbox causing no ASCOM communication issues.
Now the driver should be able to communicate to the controller even if the handbox is displaying current coords (with the handbox update interval set at 2s or more). 
Let me know...

CS
Armando

[Armando]

Ok, I solved other driver bugs.

Making the handbox working while LFEP is connected by ASCOM obliged me to evaluate if the generic answer (received by ASCOM) is corrupted. There is the need of managing unexpected data available in the input buffer (because of the handbox showing current coordinates on the display).

So I opted for a drastic driver change: if after a readout (of the expected number of bytes) from the input buffer there is still some data available, then the driver discards the input buffer content and resends the command...
Now I see the driver working as expected on my LFEP.   

Unfortunately I found a new firmware bug: sending the command #14:VX# the answer length is 8 bytes (it should be 4 bytes)!
I hope this bug affects every LFEP unit and is not related to the firmware stored in my LFEP... If so the driver will work also with your LFEP units without the need of other changes...
So please let me know the length of the answer after you've sent the command #14:VX# and your LFEP firmware release.

Clear Skies
Armando Beneduce

[Armando]

Some LFEP firmwares don't properly implement IntellyTrack. In this case it's a good idea to keep IntellyTrack OFF. Maybe all LFEP are affected by this bug.

So I added an option (Telescope -> Extra) to keep IntellyTrack OFF.
http://sourceforge.net/projects/lfepascom/files/LFEP%20ASCOM%20Driver%20%281.5.3%20Beta6%29.exe/download

If you enable this option then the IntellyTrack checkbox will be disabled. Then the only way to enable IntellyTrack will be the hardware handbox but the change will be temporary: the ASCOM handbox will take care of keeping IntellyTrack OFF. 

I just discovered that IntellyTrack is not available at all while using UserRate. This is another good reason (together with drift compensation working only in user rate mode) to prefer User rate in place of Sidereal one.

CS
Armando Beneduce