Jasem Mutlaq thanked Philippe in topic Optec Gemini Focuser/Rotator 3 months ago
Philippe replied to the topic 'Optec Gemini Focuser/Rotator' in the forum. 3 months ago

Dear Schwim.
I've looked at the documentation. Yes, the working way of the Gemini is based on the same kind of syntax as the FocusLynx HUB, but unfortunately, one big difference is a "transaction id" in the string not present in FocusLynx hub. Using a Transaction ID allows multi-threaded client (From page 5 of the "Gemini Command Reference, Revision 2.1")
That means you couldn't use as it is the Focuslynx driver even for focusing only. Now I'm working on some changes on the drivers to add full support for both focus driving and network support (With Optec support as a timeout issue is present on network connection), but I look too difficult(for me :-( ) to integrate the Gemini rotator/focuser on it and I think a new driver has to be written for that, based on the existing one for FocusLynx.
My proposal, if you're not in a hurry, is to let me finish the new version of FocusLynx one and published it (I hope for the end of August. Then we use it as base' driver for your device.
Do you coding and could do it? OR shall we have look to work on it?
@Jasem: The main difference is the transaction ID present in command string and in Gemini's acknowledge.
If not in hurry I could work on it, but as written behind, first I should publish a new FocusLynx version, then I could work on Gemini one. That means nothing for first testing before the first week on October, depending on my work and family load.
One question Ekos related. For Ekos Focuser and rotator have to be seen as two devices, havn't it? If yes I suppose we have to use the same trick as FocusLynx's driver with two main objects on it.

@both: let me know what you think of my proposal.

Best regards and clear sky.

Read More...

Philippe replied to the topic 'focuser and lx90 crash' in the forum. 11 months ago

Hi Jon.
Looks strange you're in dialout group and have to change the permission. I don't have enough knowledge to guess what could occur. No clue.

Related to the udev's folder, I had an issu within Ubuntu 16.10 and I've copied the rules files in /etc/udev/rules.d and then it works, but no idea why. I've don't find explanation about that.
Unfortunatelly I don't have other suggestion for you.

Regards

Read More...

jon thanked Philippe in topic focuser and lx90 crash 11 months ago
Philippe replied to the topic 'focuser and lx90 crash' in the forum. 11 months ago

Jon.
You wrote both tty interfaces are in dialout group that correct but what about your user account?
Did you add your user account in the dialout group?
If I'm correct the command is :
sudo usermod -a -G dialout yourusername

For udev are you sure the serial number of your connected unit is "A501T0P9" ? That could be your issue.
Regards
Philippe

Read More...

Philippe replied to the topic 'Mutiple devices handling by a single driver' in the forum. 11 months ago

For the focuslnx driver I met similar issue. The difference with you is that the focuslynx hub could manager two focusers via one serial connection. Due to that the code is a while complicate for an Indi driver.
Anyway maybe you will find an idea for yours. In fact in the driver I created two focusers object. Each one implement it own getDefaultName () function. With that you have two focusers available in Ekos and lunch it via webmannager.
Please have look at code in indi code.
Philippe.

Read More...

Philippe replied to the topic 'ZWO EFWmini (filter wheel)' in the forum. 11 months ago

Dear all.
I had a similar issue and was it solved to edit the rule in /etc/udev/ instead of /lib/udev. Unfortunately both exist in the system I don't know why but it was success for me.
Kind regards
Philippe

Read More...

Philippe thanked Ken Self in topic [SOLVED} Kstars crashing 12 months ago
Philippe replied to the topic 'I am giving this a try - question about developmen' in the forum. 1 year ago

Thanks Gonzo to have shared this sad news. Have a though to his familly.

Read More...

Philippe replied to the topic 'Moonlite focuser clone problem' in the forum. 1 year ago

Hi Jon.
Looks the unit mount correctly and with same link device on both computer . As from fresh install you have the issue let me ask you if you tried as 'root' user ?
Maybe you have to add to your used account to
The dialout group. I don't have PC with me to check the command syntax. Of 'addgrp' command. By users are not allowed ro access to tty ports.
Good luck
Philippe

Read More...

Philippe replied to the topic 'Moonlite focuser clone problem' in the forum. 1 year ago

Hello,
When you plug in your arduino in the Dell computer did you check with dmsg command if it is mount in /dev ? Maybe not some mojnt point as on Toshiba config.
Regards.
Philippe

Read More...

Philippe created a new topic ' indi_getprop issue. Some prop are displayed twice' in the forum. 1 year ago

I'm close to be ready to provide a new driver for the Optec IFW filter wheel, and have to finish the manual for it. When I've used the indi_getprop to list all available properties within this drivers I've got a surprise as some properties are displayed twice. I've done the same check with indi_simulator_wheel and indi_eqmod_telescope. In all cases some properties are displayed twice.
For Filterwheel and Telescope they are:
- XXX.DEVICE_PORT.PORT
- XXX.USEJOYSTICK.ENABLE
- XXX.USEJOYSTICK.DISABLE

Existing only on FilterWheel (For sure :-) )
- Filter Simulator.FILTER_SLOT.FILTER_SLOT_VALUE
- Filter Simulator.FILTER_NAME.FILTER_SLOT_NAME_1
- Filter Simulator.FILTER_NAME.FILTER_SLOT_NAME_2
- Filter Simulator.FILTER_NAME.FILTER_SLOT_NAME_3
- Filter Simulator.FILTER_NAME.FILTER_SLOT_NAME_4
- Filter Simulator.FILTER_NAME.FILTER_SLOT_NAME_5

Checked on one Latop with Ubunto mate 16.04 and on VM INDI
Any idea? A bug or specific raison?

Regards

Read More...

Philippe replied to the topic 'Ekos setFilterNames() on connect() ?' in the forum. 1 year ago

Thanks Jasem.

This is correct and if from device I load the config I get the same issue. Then I've overided the INDI::DefaultDevice::loadConfig() to be sure I load ONLY property not saved in EEPRom of the IFW.
I've added new Switch property to allow the user to select if he wants to check the entry versus chars who could be display on IFW screen, or if he prefers to use any chars only readable via the serial connection.

Need more test, mainly related to wheel changing and Ekos but it looks fine. Then write a manuel to be ready to be published, if you accept.

Read More...

Philippe replied to the topic 'How to get if a specific DEBUG Level is active?' in the forum. 1 year ago

Thanks Jasem for your quick answer, but I wouldn't like write a statment but take a different action in my code, depend of the debug level. As in my example, I would set the tty_set-debug actif or not fron the user selection.
Kind regards.

Read More...

Philippe created a new topic ' How to get if a specific DEBUG Level is active?' in the forum. 1 year ago

I would like to have a specific debug level to use within my drivers.
First one I use addDebugLevel() successfully;
I can check with isDebug() if Debug is active or not, good
But How could I check to know if a specific Debug level is active? like the new I create.

In my drivers I would like to be able to activate TTY Debug with the function "tty_set_debug(true)" but only if the Debug level I've created is (DBG_TTY) is active.
Something like :
//ctor
int DBG_TTY = addDebugLevel("TTY Verbose", "TTY");
....
::connect()
{
tty_set-debug(DBG_TTY);
....
How to do that? How to take the checkbox status?

Read More...

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!