LittleFoot Elegance Photo Community Forum
LittleFoot Elegance Photo => LFEP ASCOM => Topic started by: Heinz-S on Monday, 27.01.14 - 14:09:51 - CET
-
Hallo liebe Sternfreunde,
auf der Messe 2012 in Villingen – Schwenningen hatte ich die LFEP entdeckt und mir nach kurzem Gespräch mit den Betreibern des Messestands einen Flyer mitgenommen, der die Vorzüge der Steuerung beschrieb. Was ich dort las, gefiel mir, so daß ich im April 2013 über den Fachhandel eine Steuerung erwarb.
Der Bezug der Montierung und das Errichten der Säule zogen sich bis November hin. Die Zeit nutzte ich zum Studium der Anleitung und zur Eingabe von Daten in die Steuerung. Zunächst wollte ich mit der LFEP über die Polar-Align-Funktion die Montierung einnorden, was mir jedoch auch nach Stunden nicht gelang. So suchte ich Hilfe im Internet und mußte erfahren, daß diese in der Anleitung beschriebene Funktion nicht zum Ziel führt.
Darüber hinaus war veröffentlicht, daß die Steuerung nicht mehr weiterentwickelt wird. Da mein Kaufprodukt die Firmwareversion 5.88 beinhaltet, konnte ich nicht mehr updaten, obwohl eine aktuellere Firmware bereits programmiert worden war.
Nachdem das Einnorden über die klassische Methode erledigt war, stand die Anbindung an den PC an. Hierzu versuche ich nunmehr seit einer Weile zu einem Ergebnis zu kommen, scheitere aber stets, weshalb ich auf eure Hilfe angewiesen bin.
Zunächst hatte ich den aktuellen LFEP Treiber installiert, bekam aber stets eine Fehlermeldung mit dem Hinweis, eine Firmwareversion 6.10 oder höher würde benötigt. Diese Meldung erfolgte auch bei Treibern bis hinab zu den Versionen 1.3.
Nun habe ich den Treiber 1.1.3 aufgespielt, erhalte aber eine andere Fehlermeldung: „Please select COM/LAN settings in SETUP first“. Obwohl ich vorab immer die COM Schnittstelle auswähle (über die ASCOM Plattform oder CdC oder direkt im Treiber) will die Fehlermeldung nicht weichen. Mittlerweile habe so oft alle Komponenten installiert und wieder deinstalliert, daß ich mit meinem Latein am Ende bin.
Zugleich war der Versuch, mit dem Generic LX200 Treiber (Version 5.0.1) die LFEP anzusprechen von Erfolg gekrönt. Nach Auswahl der COM Schnittstelle und dieses Treibers verbinden sich PC und LFEP. Die Koordinaten der Steuerung werden in CdC angezeigt. Wegen schlechten Wetters konnte ich das Zusammenspiel jedoch noch nicht testen.
Es ergibt jedoch keinen Sinn, daß man einen Fremdtreiber benutzt, wenn für die Steuerung ein eigener Treiber entwickelt wurde. Habt ihr eine Erklärung für das Problem?
Folgende Komponenten sind bei mir zur Zeit installiert:
WIN7 Home Premium SP1; ASCOM Plattform 6 – SP3 – 6.0.3.0; LFEP Firmware 5.88; LFEP Treiber 1.1.3; FTDI – Treiber 2.08.30; Microsoft NET Framework 4.5.1; Ansteuerung über die virtuelle COM2 Schnittstelle; Verbindung über USB-Kabel mit USB2 Standard ohne USB-Seriell-Wandler.
Beste Grüße
Heinz
-
Hi Heinz,
Polar Alignment was not implemented.
LFEP ASCOM driver requires firmware >=6.1
LFEP makes use of LX200 protocol for some commands (e.g. GoTo and sync) so that you can control your mount by LX200 but you'll be not able to use all LFEP features by LX200. By hardware handbox you can manage all LFEP settings.
I may be wrong but I remember that LFEP 5.xx firmware makes use of an older bootloader; in this case a firmware update is not possible without the help of Rajiva. :(
Clear Skies!
Armando Beneduce
-
Hello Armando,
thank you very much for the informations. The LFEP project has been started in 2009. The programming of the first ASCOM driver began at 2010. So there must exist some driver versions, that also will work together with the LFEP firmware 5.88. I hope, the version I'm already using (ASCOM driver 1.1.3) is one of them.
So there should be a chance to connect the LFEP with the laptop also with my firmware conditions. Using the LX200 Generic driver, the move commands from CdC arrive at the LFEP. Therefore I have no explanation, why the error message occurs, when I'm using an original LFEP driver.
Clear skies
Heinz
-
Hi Heinz,
if you've a pdf about the protocol used by your LFEP I could try to define what is missing in LFEP 5.xx firmware.
Maybe disabling some features in current ASCOM driver can make it working with 5.xx firmware too...
CS
Armando
-
I just gave a look at ASCOM driver revision history and I found nothing about 5.xx FW support. So I think FW had been deeply changed with 6.xx release. ::)
Anyway what features do you mean to use on your LFEP?
CS
Armando
-
Hello Armando,
currently I need only the standard features like move commandos, park position, meridian flip. They are partly supported by the generic LX200 driver. For the moment the situation is acceptable.
When I have a look at the promotion of “Teleskopsteuerung.de” in the “Astrotreff-Forum”, where all the features of the original LFEP driver are presented, I'm unhappy not to have access on them.
When I bought the LFEP, I didn't know, that my firmware cannot work together with that driver.
If I need more features in the future, I have to buy another control unit. Thanks again for your help an the best wishes.
Clear skies
Heinz
-
Hi Heinz,
I perfectly understand your point of view.
While keeping current ASCOM development on, I found 6.xx FW affected by some (not documented) bugs that made developing a little annoying.
I'd like to make current ASCOM driver compatible with 5.xx FW releases but having no 5.xx FW documentation makes developing pretty difficult...
I can "reduce" current ASCOM driver by removing some code trying to make it working with 5.xx release.
We could ignore all ASCOM commands used to configure LFEP (mount settings, focuser settings, ...) and limit to make the main controls available by ASCOM...
But you'll have to test, debug, send me some logs, ...
I asked you about the features you mean to use to define if a quick solution is possible.
If you mainly need only GoTo functions I suggest to use FocusMax: FocusMax will connect to LFEP by LX200; so all the clients you mean to use to control your LFEP (e.g. SkyChart, MaxIm, ...) can connect to FocusMax hub contemporaneously...
Let me know ;)
CS
Armando
-
Hello Armando,
I send you my deep respect for the willingness in spending your time to make the driver compatible with 5.88 firmware. I'm not the only user with that firmware version. I agree with you, that all features could be ignored, setting by the handbox at starting up the LFEP for the first time.
The features, I'm needing particularly are the follows:
Automatic Meridian Flip
Safety function for remote operations
Controlling the time setting of the LFEP
Displaying the handbox on the screen with the coordinates
Sync and move commandos
Controlling the LFEP by using the LAN interface
I'm willing to participate in some tests, but I'm not an IT specialist. Furthermore I'm not sure if these tests are possible, because my laptop didn't connect to the LFEP by using the original LFEP driver (error message: „Please select COM/LAN settings in SETUP first“).
The software FocusMax was yet unknown to me. Thank you for that tip.
CS
Heinz
-
Hi Heinz,
I'm pretty sure the main troubles will come from #0:VX# command. It's used to read LFEP state and everything else moves around it.
Current solution is an ASCOM server making multiple connections possible.
Because of this choice there is the need to manage commands coming from many clients.
Just for example you won't focus while moving the mount. If only one software was used to control LFEP, the software itself will never send a focusing command while the mount is moving since the same software will have sent the GoTo command and will be waiting for the end of the GoTo...
But if an ASCOM server solution is adopted then the ASCOM server has to take into account a client can ask to focus while the mount is moving because of a GoTo command sent by another different client...
Furthermore you can control your LFEP also by handbox! And this is the reason why the server has to poll LFEP internal settings to know and refresh LFEP state to exclude possible issues...
#0:VX# is the command periodically sent to LFEP to know its state.
The answer is binary and each bit has its own meaning...
I think #0:VX# command or an equivalent command is implemented in 5.xx firmware. There is the need to test it in different conditions to reverse engineer the binary answer...
Maybe because of missing features in LFEP 5.xx FW the answer length is different too...
I'm willing to participate in some tests, but I'm not an IT specialist. Furthermore I'm not sure if these tests are possible, because my laptop didn't connect to the LFEP by using the original LFEP driver (error message: „Please select COM/LAN settings in SETUP first“).
If you try the ASCOM driver for 6.xx FW, you have to set the COM port number (by a click on setup) before being able to connect to LFEP...
As soon as you connect the LFEP by USB cable a new serial port is available; you can figure out its number by Windows control panel...
Then, after executing the LFEP ASCOM launcher, you have to click on setup to set the right port number. Then a click on connect will start communication by using the appropriate port...
I think the same is valid also for the old driver...
Port choice is saved; so setting the port number is required only for the 1st connection after the driver has been installed or, obviously, in case of port number change...
The software FocusMax was yet unknown to me. Thank you for that tip.
I suggested this solution since with no efforts and without an ASCOM server solution (i.e. by a simple ASCOM LX200 driver) thanks to FocusMax you'll be able to communicate to LFEP by many clients ...
CS
Armando
-
Hello Armando,
the problem is, that the connection of the LFEP with my laptop dose not work at all by using the original driver (version 1.1.3 or any other version). I proceeded exactly as you described it, but the error message occurs again and again. That was the reason to open that thread.
After plugging in the USB cable, the COM2 port appears, I change it and try to connect the LFEP. But every time the Laptop reports: Please select COM/LAN settings in SETUP first. When I'm using the Generic LX200 driver and fulfil the same procedure, Laptop an LFEP connect without the report of any error message.
An especially LFEP ASCOM launcher is not implemented in my driver version. I start the connection with my client software (E&T or CdC). These programs firstly displayed an ASCOM telescope chooser. I set the little food photo telescope hub. Then I click on the properties button and the little foot photo telescope setup appears. In that window I set my COM2 port. Then I click the connect button and the error message appears. If I choose the Generic LX200 driver in the same way, the connection is successful.
Do you have an idea, why the driver reacts in that way.
CS
Heinz
-
Hi Heinz,
the problem is, that the connection of the LFEP with my laptop dose not work at all by using the original driver (version 1.1.3 or any other version). I proceeded exactly as you described it, but the error message occurs again and again. That was the reason to open that thread.
did you try also the driver for FW 6.xx (v1.5.3)?
I obviously know that some changes are required to make it working with FW 5.xx; but 1.5.3 driver should show a message about the need for a 6.xx FW...
After plugging in the USB cable, the COM2 port appears, I change it and try to connect the LFEP. But every time the Laptop reports: Please select COM/LAN settings in SETUP first. When I'm using the Generic LX200 driver and fulfil the same procedure, Laptop an LFEP connect without the report of any error message.
An especially LFEP ASCOM launcher is not implemented in my driver version. I start the connection with my client software (E&T or CdC). These programs firstly displayed an ASCOM telescope chooser. I set the little food photo telescope hub. Then I click on the properties button and the little foot photo telescope setup appears. In that window I set my COM2 port. Then I click the connect button and the error message appears. If I choose the Generic LX200 driver in the same way, the connection is successful.
Do you have an idea, why the driver reacts in that way.
Maybe administrator privileges are required to store the port number in the ASCOM profile created by your driver; in this case probably the port number is missing. Give a look at the ASCOM profiles stored in your machine (by executing ASCOM profile explorer utility). Search for the keys related to the driver you mean to use (under Telescope Drivers group). Maybe there is no data associated to the port number...
I think a screenshot of my profile settings can be of help... Look for something similar related to the serial port number that your driver expects to find in your ASCOM profile; maybe only the port number is missing.
CS
Armando
-
Hello Armando,
I also tried the drivers for FW 6.xx (like v.1.5.3 or 1.4.x or 1.3.x). You're right: In all that cases the result was a message, that FW 6.xx is needed.
Today I started again the LFEP test client tool: Clicking on “Setup Telescope” the COM/LAN settings appear; after choosing the COM2 interface I click on connect with the same result as before. Then I started the ASCOM profile explorer 6.0.0.0 and had a look to the LFEP COM settings: The COM2 interface was displayed at the same place as I find it in your screenshot.
Perhaps the older LFEP drivers are only compatible to an older version of the ASCOM platform. That possibility I'm not able to test, because I couldn't find an older version of ASCOM for a download.
You have told about a chance to make working the driver v1.5.3 together with FW 5.xx. That would be the solution for all the problems.
In the appendix you will find some log-files, created by the ASCOM diagnostics program.
CS
Heinz
-
Hi Heinz,
I also tried the drivers for FW 6.xx (like v.1.5.3 or 1.4.x or 1.3.x). You're right: In all that cases the result was a message, that FW 6.xx is needed.
...
You have told about a chance to make working the driver v1.5.3 together with FW 5.xx. That would be the solution for all the problems.
I just received a confirmation by Gerald: as expected, #0:VX# answer is deeply different between the two FW versions.
So it is to be reverse engineered to try to make current driver working with 5.xx FW.
In 6.xx FW the answer length is 22 bytes. Not so easy to decipher without the documentation...
I've no idea about the answer with 5.xx FW. You should start the hard work of deciphering it... You could download RealTerm (It's a good utility to send commands to LFEP) and give a look at its GUI... It's user friendly and offers many options. You'll have to set the right port number and appropriate port settings (9600bps, 8-N-1) to open the port and send #0:VX# string (in ASCII mode). RealTerm will show you the LFEP answer. Playing with LFEP (e.g. locking the mount or sending a GoTo command) you should see what changes in the answer. This way you'll be to recognize if the mount is slewing, is parked, is tracking, is flipped, ... Then I'll adapt the code accordingly.
CS
Armando
-
Hello Armando,
I tried to exercise your instructions. In the appendix you will find some screenshots, the LFEP replies while I'm using the handbox:
Pic1: After move to home position.
Pic2: After sending #0:VX# without tracking.
Pic3: After GotoTourM13-Set.
Pic4: After move to a star.
Pic5: After sending #0:VX# while LFEP is in tracking mode.
Perhaps these informations will be useful. I've no know how in such special programming features.
If the screenshots are useless, please let me know, if there is a chance to download an older version of the ASCOM platform. I cannot find a corresponding link.
CS
Heinz
-
Hi Heinz,
...
Perhaps these informations will be useful.
...
Gerald sent me some sources that could be of help to properly, but only partially, read 5.xx 0:VX answer.
I'm going to evaluate the changes required to adapt the ASCOM driver to 5.xx FW. Then I'll let you know if supporting 5.xx is feasible. In that case I'll surely need some tests by you by RealTerm.
I'll provide you further details about the required tests: you can see from your screenshots that moving your mount by LFEP handbox makes the LFEP writing on serial port by itself. You won't have to play by the handbox to control LFEP, you'll have to send some commands by RealTerm itself and report the answers... To properly read the answers you will have to set Hex+Space or Hex + ASCII mode and enable half duplex (in Display panel) to make Realterm showing both commands and answers. Hex mode is required to properly show binary answers, the ones we need to read. ASCII mode is good for "text". Enabling \n Before and \n After makes RealTerm showing each command/answer on a new line and can make the screenshots more understandable. If you send #:GV# you can figure out what I mean...
Keep in mind LFEP is case sensitive and the commands are to be sent by a click on "Send ASCII" button.
If the screenshots are useless, please let me know, if there is a chance to download an older version of the ASCOM platform. I cannot find a corresponding link.
I think the driver for Little Foot at http://ascom-standards.org/Downloads/ScopeDrivers.htm can work.
Anyway it's possible that ignoring some LFEP features (e.g. disabling tracking rates reading, assuming current speed is sidereal one, disabling IntellyTrack/KingRate management, PEC state check, ...) can make the driver working without too much effort. Maybe reading if mount is synced, if it's tracking or slewing and the side of pier is enough to start making the driver working...
I'll let you know. ;)
CS
Armando
-
Hello Armando,
thank you for your explanations. Of course I'm ready to send the test commands to the LFEP, if you tell me, what I have to enter. When the final result will be a working driver, that controls the automatic meridian flip and the safety functions for remote operations, all 5.xx users would be happy, not to depend on the Generic LX200 driver any longer. Hopefully you will be successful!!
So I'm waiting to your further informations.
CS
Heinz
-
Hi Heinz,
let me know if connection works by installing the attached driver. I hope/think ASCOM handbox is properly displayed.
We need to make the ASCOM handbox working by itself, without playing with it for now...
Install SerialMon, execute it and make it sniffing traffic on the port associated to LFEP...
Then start LFEP starter utility and start the ASCOM connection: SerialMon will show traffic to/from LFEP...
In the past, to improve communication, I had to force the driver to resend a command when the received answer length was not as expected.
The length of the answers can be different between FW5.xx and FW6.xx for some commands. :(
This is the case with #0:VX# and I modified the driver accordingly (and now I think the answer is properly managed to detect slewing, tracking and sync state of the mount).
But maybe other commands are affected by the same kind of change. In this case as soon as the issue occurs you can see the driver loops endlessly sending always the same command...
Maybe this is the case with #:VS# command. If so, I need to know the length of the answer. We'll decipher the content of the answer afterwards... We need to solve communication locks if they occur.
You can also use RealTerm to let me know the content of the answer causing issue (in Hex + ASCII mode...) and post SerialMon logs to allow me to figure out what is wrong...
CS
Armando
-
Hello Armando,
unfortunately the LFEP didn't connect properly. The connection begins and was interrupted during the execution, displaying the error message, you will find in the appendix (Pic1 and Pic2).
Executing RealTerm I send #:GV# and get the answer: 23 3A 47 56 23
After sending #:VS# I could read: 23 3A 56 53 23
I installed and run SerialMon with administrator rights, but at the program start the message showing in Pic3 appears. After restart and reinstalling the message appears again. On it's screen no information was recognizable when I execute the LFEP starter.
Perhaps the detection of FW 5.88 is more easier to you, when I send my LFEP hardware by mail to you at home. Would that be an option?
CS
Heinz
-
Hi Heinz,
unfortunately the LFEP didn't connect properly. The connection begins and was interrupted during the execution, displaying the error message, you will find in the appendix (Pic1 and Pic2).
I need SerialMon log or SerialMon screenshot.
Executing RealTerm I send #:GV# and get the answer: 23 3A 47 56 23
It's not the answer, it's the command shown in ASCII mode by RealTerm. (e.g. # is coded as 35 in ASCII and 35=2*16+3=0x23; : is coded as 58 in ASCII and 58 = 0x3A).
You need to set duplex mode to see both commands and answers.
After sending #:VS# I could read: 23 3A 56 53 23
It's still the command...
I told you to send #:GV# to figure out how RealTerm works. The answer by LFEP to #:GV# is the firmware number. Playing with RealTerm settings you'll figure out how to set it to properly read the answers (text or binary).
Set Hex + ASCII and you'll see each byte answer in Hex and ASCII... RealTerm will show you also the command in the same mode.
Perhaps the detection of FW 5.88 is more easier to you, when I send my LFEP hardware by mail to you at home. Would that be an option?
I think you need only to figure out how to play by SerialMon... ;)
CS
Armando
-
Please let me know with the attached driver.
CS
Armando
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
Please use the attached driver...
-
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
-
Hi Heinz,
The synchronization function is only working partially. The date information was applied perfectly. The PC time unfortunately was not detected by LFEP.
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...
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.
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
-
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
-
Hi Heinz,
the attached driver should solve the Extra and Date/time sync issues.
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?
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
-
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. ::)
-
Hello Armando,
the new update has solved all problems I reported last.
The PC date and time are applied properly.
A click on the Extras button returns no longer an error message.
I sent #:GV# and #:GD# to the LFEP while pressing several move buttons. RealTerm didn't log any answer. Anyway the problems while using my application program didn't appear furthermore. I can use all HW handbox buttons. E & T shows a cross at the position of the telescope. While moving the telescope by HW handbox this cross followed those movements.
CS
Heinz
-
Hi Heinz,
you can refer to http://forum.lfep.de/index.php?topic=15.0 to keep your driver updated.
CS
Armando
-
Hello Armando,
your final update is doing a good job. Now every FW5.. user is able to enjoy the hobby in association with the LFEP. So I send you a big thank-you for the invested time and your patience.
I just had a look on sourceforge. In the description of the driver only FW6.. is listed as supported firmware. Would you be so kind to change the description in order that FW5.. users will notice the driver modifications.
CS
Heinz
-
Hello Heinz,
I just updated the driver's description on Sourceforge.
I also added a link to this forum in support page since I think it's the best place to get support. I also take the opportunity to thank Roman for maintaining the forum.
I'm glad to have been of help.
CS
Armando Beneduce