Quantcast
Channel: Recent Topics - INDI Forum
Viewing all 14088 articles
Browse latest View live

FS-2 won't slew - by: Herrhausen

$
0
0
Hi, I'm currently re-activating equipment that was stowed away for a couple of years. Got a FS-2 (V1.21) control box and an Alt AD-5 mount. Kstars and Stellarium both have the same problem, SLEW doesn't work. Crosshairs move along nicely when I move the mount using the FS-2 handbox though. As soon as I try to SLEW in KStars or Stellarium, the FS-2 displays "schwenke" (=slew) for maybe 1/10th of a second and then nothing happens. I can repeat that as often as I want. All conncections are OK, INDI says everything was OK, too.

I remember the same problem had occurred many years ago when I first tried INDI. At the time I made a slight modification to the source code after which INDI worked perfectly. I had forwarded my modification to the maintainer but somehow the old version must have made its way back. Unfortunately I can't remember as to what the modification was.

Are there any other FS-2 users out there who can confirm my problem? Many thanks for replies.

CS
Alfred

Raspberry files: missing indi_asi_driver - by: sbothe

$
0
0
Hey,
I have installed the indiserver on my Raspberry and everything is fine and works, but the ZWO ASI indi driver is missing.
Maybe someone can tell me where I can find it?

Greetings,

Sebastian

Unable to connect EQ6 Synscan Pro to Ubuntu - by: Agis

$
0
0
Hello!
I am trying to control a EQ6 Synscan Pro mount with a laptop, running Ubuntu 14.04. I use an EQdir interface with a usb to serial cable to connect the mount to the laptop and everything works fine on windows with EQMOD ASCOM drivers.

• On Ubuntu I installed INDI library and Kstars with no errors and everything seems to work fine.
• Ubuntu recognize the serial cable and mount it on ttyUSB0.
• With minicom I set up the connection like this: 96000 8N1.
• On Kstars I choose EQMOD mount and set /dev/ttyUSB0 port.
• After a while the software returns "connection failed, probably timed out"

Should I set up the connection with a different way, or is there any other mistake I make?

Thank you for your help!

EQMod snoop "Site Management" from a GPS Driver - by: Besson

$
0
0
I’m working to add snoop function on EQMOD driver to update local position and local time from another drivers whose get these information from a GPS via an Arduino module. Like the Astroberry project done on indi_rpi driver Thanks to rkaczorek for the idea.

Today it build to work with my own specific driver.

I think it could nice if this function is going to be integrated in the original EQMod driver. For that and to do a clean job, I think create a kind of “generic” function and publish the definition of the XML items required to send data to EQMod driver.

Sure I’ve to ask if the EQMod maintainer if he would include in the driver itself.

I would like to open the discussion for vector name, elements name, format of value/text and other idea about this topic.
Till now I use these information in my draft:
- Longitude In sexagesimal
- Longitude in sexagesimal
- Elevation in meter
- Date as yyyy-mm-dd
- Time as hh:mm
- IPState to know if the GPS is valid

First think I will change is to use two vectors for GPS Data. One for position data, and second one for Date/Time.

It looks that I program it correctly to have change done in the EQMod driver, but I’m not so familiar with the relations between LST, Julian date, EQ. Coordinates, UTC Time and scope location yet to be sure all changes are implemented.
Any help and support would be welcome.

As I’m not experimented programmers, I hope writing a correct and good usable code..

Here you are my code proposal:

bool EQMod::ISSnoopDevice (XMLEle *root)
/* This function expect that all datas from the GPS are in the same Text Vector
* We expect that the setting of time or position could be selected separatly by the user
* In usual the time is provide quite faster by the GPS than the localisation
* Philippe Besson
* V0.1 - 20th of August 2015
*/

{
time_t t0;
struct tm st={0}, lt={0};
int rc;
double dGpsLon, dGpsLat, dGpsElev;
char year[5], month[3], day [3], hour[3], min[3], sec[3];

// Wich device send the message
//TODO Could be used to do a self registration as subsrider to sent acknwoledgement back!
const char *propDevice = findXMLAttValu(root, "device");
DEBUGF(INDI::Logger::DBG_WARNING, "Received a snoop message from device : %s", propDevice);

/* XML Tag received by the GPS driver
2015-08-17T18:01:02: Date
2015-08-17T18:01:02: Heure GMT
2015-08-17T18:01:02: Altitude (m)
2015-08-17T18:01:02: Latitude
2015-08-17T18:01:02: Longitude
2015-08-17T18:01:02: Satellites
2015-08-17T18:01:02: Antenne
*/

const char *propState = findXMLAttValu(root, "state");

// GPS Value OK? Defined IPS_OK state of vector as GPSFix
if (!strcmp(propState, "Idle")) gpsdata.state = IPS_IDLE;
else if (!strcmp(propState, "Ok")) gpsdata.state = IPS_OK;
else if (!strcmp(propState, "Busy")) gpsdata.state = IPS_BUSY;
else if (!strcmp(propState, "Alert")) gpsdata.state = IPS_ALERT;

DEBUGF(INDI::Logger::DBG_DEBUG, "GPS State received : %s", propState);
DEBUGF(INDI::Logger::DBG_DEBUG, "GPS State received value : %d", gpsdata.state);

const char *propName = findXMLAttValu(root, "name");

if (!strcmp(propName, "GPS-SYNC"))
{
DEBUGF(INDI::Logger::DBG_DEBUG, "%s", "GPS-SYNC Message received !");
// Identified the GPS data as valid
if (gpsdata.state == IPS_OK)
{
XMLEle *ep=NULL;
for (ep = nextXMLEle(root, 1) ; ep != NULL ; ep = nextXMLEle(root, 0))
{
const char *elemName = findXMLAttValu(ep, "name");
DEBUGF(INDI::Logger::DBG_DEBUG, "Snooping property received %s", (char *)elemName);

if ((!strcmp(elemName, "GPSPOS")) && (!strcmp(pcdataXMLEle(ep), "On")))
// Mannage Local position value
// Convert Gps data coord to double value
{
if (f_scansexa(gpsdata.Lon, &dGpsLon) != 0)
{
DEBUGF(INDI::Logger::DBG_DEBUG, "Convertion error from sexagesimal to double for longitude from GPS %s", gpsdata.Lon);
return 0;
}
if (f_scansexa(gpsdata.Lat, &dGpsLat) != 0)
{
DEBUGF(INDI::Logger::DBG_DEBUG, "Convertion error from sexagesimal to double for latitude from GPS %s", gpsdata.Lat);
return 0;
}
dGpsElev = atof(gpsdata.Elev);

DEBUGF(INDI::Logger::DBG_DEBUG, "LONG %f", dGpsLon);
DEBUGF(INDI::Logger::DBG_DEBUG, "LAT %f", dGpsLat);

//strncpy(gpsdata.Lat, pcdataXMLEle(ep), sizeof(gpsdata.Lat));
// Here we set the new site postion from the GPS
if (updateLocation(dGpsLat, dGpsLon, dGpsElev))
{
LocationN[LOCATION_LATITUDE].value = dGpsLat;
LocationN[LOCATION_LONGITUDE].value = dGpsLon;
LocationN[LOCATION_ELEVATION].value = dGpsElev;
LocationNP.s=IPS_OK;

// Update client display
IDSetNumber(&LocationNP,NULL);
}
else
{
LocationNP.s=IPS_ALERT;
// Update client display
IDSetNumber(&LocationNP,NULL);
}
}

else if ((!strcmp(elemName, "GPSTIME")) && (!strcmp(pcdataXMLEle(ep), "On")))
// Mannage Time snoop value
{
// Here we set the new time from the GPS
//We are looking for time offset and time zone; GPS provide UTC time
t0 = time(NULL);
localtime_r(&t0, &lt);

DEBUGF(INDI::Logger::DBG_DEBUG, "Offset to GMT is %d", lt.tm_gmtoff);
DEBUGF(INDI::Logger::DBG_DEBUG, "The time zone is %s", lt.tm_zone);

/* initialize time from snopped device*/

DEBUGF(INDI::Logger::DBG_SESSION, "TIME = %s, DATE = %s", gpsdata.Time, gpsdata.Date);

rc = sscanf(gpsdata.Date, "%[^-]-%[^-]-%[^\n]", year, month, day);
DEBUGF(INDI::Logger::DBG_DEBUG, "rc DATE : %d", rc);
if (rc == 3)
{
rc = sscanf(gpsdata.Time, "%[^:]:%[^:]:%[^\n]", hour, min, sec);
DEBUGF(INDI::Logger::DBG_DEBUG, "rc TIME : %d", rc);
if (rc == 3)
{
// all extration data has been successfull (rc result OK)
// Reuse partially the init code for time initialisation
st.tm_year = atoi(year) - 1900;
st.tm_mon = atoi(month) -1;
st.tm_mday = atoi(day);
st.tm_hour = atoi(hour);
st.tm_min = atoi(min);
st.tm_sec = atoi(sec);
st.tm_isdst = 1; // Is DST on? 1 = yes, 0 = no, -1 = unknown

lasttimeupdate.tv_sec = mktime(&st) + lt.tm_gmtoff; // compensate with local time offset to UTC time
lasttimeupdate.tv_usec = lasttimeupdate.tv_sec * 1000;
// now gmtime give the UTC time from the GPS
gmtime_r(&lasttimeupdate.tv_sec, &utc);
lndate.seconds = utc.tm_sec; + ((double)lasttimeupdate.tv_usec / 1000000);
lndate.minutes = utc.tm_min;
lndate.hours = utc.tm_hour;
lndate.days = utc.tm_mday;
lndate.months = utc.tm_mon + 1;
lndate.years = utc.tm_year + 1900;
// Set the new value of the lastclockupdate value
clock_gettime(CLOCK_MONOTONIC, &lastclockupdate);
} //if (rc == 3)
} //if (rc == 3)
} //else if ((!strcmp(elemName, "GPSTIME")) && (!strcmp(pcdataXMLEle(ep), "On")))
} //for (ep = nextXMLEle(root, 1) ; ep != NULL ; ep = nextXMLEle(root, 0))
} //if (gpsdata.state == IPS_OK)
} //if (!strcmp(propName, "GPS-SYNC"))

if (!strcmp(propName, "GPS-INFO"))
// Getting GPS data throughtthe snoop of the text vector who's contain these
{
if (gpsdata.state == IPS_OK)
{
XMLEle *ep=NULL;
// Store values received by the GPS module on BoxControler
for (ep = nextXMLEle(root, 1) ; ep != NULL ; ep = nextXMLEle(root, 0))
{
const char *elemName = findXMLAttValu(ep, "name");
DEBUGF(INDI::Logger::DBG_DEBUG, "Snooping property received %s", (char *)elemName);

if (!strcmp(elemName, "Latitude"))
{
strncpy(gpsdata.Lat, pcdataXMLEle(ep), sizeof(gpsdata.Lat));
DEBUGF(INDI::Logger::DBG_DEBUG, "Latitude OK %s", gpsdata.Lat);
}
else if (!strcmp(elemName, "Longitude"))
{
strncpy(gpsdata.Lon, pcdataXMLEle(ep), sizeof(gpsdata.Lon));
DEBUGF(INDI::Logger::DBG_DEBUG, "Longitude OK %s", gpsdata.Lon);
}
else if (!strcmp(elemName, "Altitude (m)"))
{
strncpy(gpsdata.Elev, pcdataXMLEle(ep), sizeof(gpsdata.Elev));
DEBUGF(INDI::Logger::DBG_DEBUG, "Altitude OK %s", gpsdata.Elev);
}
else if (!strcmp(elemName, "Heure GMT"))
{
strncpy(gpsdata.Time, pcdataXMLEle(ep), sizeof(gpsdata.Time));
DEBUGF(INDI::Logger::DBG_DEBUG, "Heure GMT OK %s", gpsdata.Time);
}
else if (!strcmp(elemName, "Date"))
{
strncpy(gpsdata.Date, pcdataXMLEle(ep), sizeof(gpsdata.Date));
DEBUGF(INDI::Logger::DBG_DEBUG, "Date OK %s", gpsdata.Date);
}
} //for (ep = nextXMLEle(root, 1) ; ep != NULL ; ep = nextXMLEle(root, 0))
} //if (gpsdata.state == IPS_OK)
} //if (!strcmp(propName, "GPS-INFO"))

return true;
} //EQMod::ISSnoopDevice

EKOS change request - by: Kaczorek

$
0
0
After using KStars and EKOS many times I came to the following conclusions:
1. Instead of Capture&Solve button and Sync, Slew to Target, Nothing switches I suggest using just three buttons in the top section, replacing existing Capture&Solve button with three buttons: Solve, Solve&Slew (or Solve&Goto), Solve&Sync. With this solution GOTO section is obsolete. No more jumping with your eyes among buttons and switches.Just click and go.
2. Set maximum slewing rate should be available for goto operations. Under heavy load some mounts starting with full speed sound really bad due to vibrations. Presetting maximum slewing speed would prevent this behaviour and ensure smooth and silent operations.

BTW. What are these annoying XML files in default fits directory? All of them are corrupted. I believe that they are written to disk at any preview (CCD or Alignement)
BTW2. Recent version of KStars (bleeding) crashes in any attempt to save image coming from focus or ccd preview.

SBIG ST-7XME doesn´t work on Raspberry - by: sbothe

$
0
0
Hey,
I have installed the indiserver on my Raspberry, but the SBIG driver doesn´t start.
On my laptop everything works fine.
Because I´am a beginner with Linux and Indi maybe someone could help me

Greetings,

Sebastian

Here is the output from the console:

pi@raspberrypi ~ $ lsusb
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 006: ID 0d97:0101 Santa Barbara Instrument Group SBIG Astronomy Camera (with firmware)
Bus 001 Device 004: ID 03c3:120a
pi@raspberrypi ~ $ sudo indiserver -v indi_sbig_ccd
2015-08-22T16:51:33: startup: indiserver -v indi_sbig_ccd
2015-08-22T16:51:33: Driver indi_sbig_ccd: pid=3586 rfd=3 wfd=6 efd=7
2015-08-22T16:51:33: listening to port 7624 on fd 4
2015-08-22T16:51:33: Driver indi_sbig_ccd: stdin EOF
2015-08-22T16:51:33: Driver indi_sbig_ccd: restart #1
2015-08-22T16:51:33: Driver indi_sbig_ccd: pid=3587 rfd=0 wfd=6 efd=7
2015-08-22T16:51:33: Driver indi_sbig_ccd: stdin EOF
2015-08-22T16:51:33: Driver indi_sbig_ccd: restart #2

INDI::Weather class - by: knro

$
0
0
I am planning to standardize weather devices & services in INDI, and would appreciate your input before I embark on the actual development. Basically the idea is to design a class that encapsulates most weather parameters of interest to astronomers along with their range & units. For each parameter that is supported by the device, the user should be able to pick a "maximum" and/or "minimum" range which the value must fall within for it deemed "acceptable". Once the value is exceeded for a certain time threshold (also configurable), then the status of the overall "Weather Parameter" property is ALERT and this should cause the observatory to interrupt any operations and go into "panic mode".

All parameters shall have:

1. Actual value + unit if any
2. Current % of Maximum Range?
3. Minimum/Maximum "Acceptable" range?

This could even apply to rain (descriptive and mm). If we define rain conditions as RAIN_DRY, RAIN_LIGHT, RAIN_HEAVY (just an example, the actual enumeration range can be more complex) then we have just 3 values (0, 1, 2). The % would be 0%, 50% and 100%. The minimum/maximum acceptable range could be 0%/0%. If the rain is measured in mm, the same principle applies.

There will be a primary LIGHT property which holds the state of the various parameters. Green OK, Yellow Warning (10% within range, if applicable), and Red for Alert.

Weather: [X] Rain [X] Wind [X] Clouds

If Rain is ALERT, then the whole Weather property is ALERT, and the observatory can go into safe mode. As it stands now, it is either OK (continue observing), or full panic mode (stop observation, close dome shutter, park..etc). We can have a "Medium" risk mode which we would have to define someway. Perhaps something like, if Warning state last more than 5 minutes, or only if parameters X, Y, Z are all warning then the overall state becomes warning, otherwise, it is OK...etc.. For the "Medium" risk, it can cause the observatory to cease operations, until the weather improves, but it doesn't need to go into panic mode.

This might seem complex, but remember we are trying to create a generic weather interface for _any_ devices or service, with any number of parameters, descriptive or physical in nature. Furthermore, we need to formalize what is the overall state of the weather device, and how it can affect the observatory. Is OK/Alert enough? or OK/Warning/Alert? Or perhaps something else completely?

Any thoughts appreciated!

Atik 16HR support - by: gerardvs

$
0
0
Hi All,

Does anyone know is the Atik 16HR (artemis 285) is supported by indi? I installed the Atik drivers but the camera is seen as a model 383L. Of course this doesn't work so I wander if the 16HR is usable bij INDI.

Please let me know if someone has some info on this device.

Kind regards,
--Gerard

Losmandy Titan/Gemini support - by: gerardvs

$
0
0
Hi All,
Today I tried to connect to my Losmandy Titan (Gemini 1controller). Connecting to Gemini goes fine but I'm unable to control the mount and I even think not all parameter are read from the mount. Btw, the LX200 basic driver gives the same result.

I've seen users successfully using Gemini with a G11 but I would like to know if the Titan also should work.

All info is welcome.
Thanks,
--Gerard

Kstars Version and PPA - by: Vecchietto

$
0
0
Hello,

I've tried to track down exactly what should work together but I don't seem to be able to find an answer. Should the latest INDI drivers from the Debian PPA, not bleeding edge, work with Kstars V2.2.0 installed on Xubuntu (Ubuntu 14.04.3) ? Specifically for controlling the Celestron Nexstar. If not, can I roll back to the previous drivers. They worked fine before I tried the PPA drivers.

Thanks,

Jerry

EQMod driver not working after update - by: Kaczorek

$
0
0
It looks like the latest changes of eqmod (or indi telescope?) introduced fatal error to the code. You cannot unpark a mount, slew, track or goto. The client just freezes at any of these operations with no debug info returned by indi.

OS Ubuntu Mate on Raspberry Pi v2
INDI version 1.1.0+r814.221~ubuntu15.04.1
indi-eqmod version 0.2+r68.221~ubuntu15.04.1
kstars-bleeding version 5:15.04+r5191.213~ubuntu14.10.1

[File Attachment: eqmod_log.txt]

Connecting ekos to multiple INDI servers - by: sarkkipas

$
0
0
Can you make ekos connect to mutipe INDI servers running different gear sets? i.e one server has mount, guider and focuser and another has imaging ccd.
Kstars has this ability allready in device manager but not in Ekos?

Astroberry drivers for Raspberry Pi devices - by: Kaczorek

$
0
0
INDI Astroberry 1.0.2 provides:
* Astroberry Focuser - stepper motor driver with absolute and relative position capabilities and autofocus with INDI client such as KStars and Ekos
* Astroberry GPS - GPS driver for easy scope location and UTC time setting
* Astroberry AltIMU - accelerometer, magnetometer, gyro, atmospheric pressure sensor driver
* Astroberry Board - power switch board allowing for remote powering on/off up to 4 devices.

The latest changes include:
indi_rpigps - Rewrite fo the driver to sync with libindi changes (GPS::INDI)
indi_rpigs - Adding Polaris Hour Angle for easy polar alignment
indi_rpibrd - Shutdown button added for secure system power off

You can download source and binary package from here

eqmod not working - by: bmorrelltx

$
0
0
I am running the latest Ubuntu with KStars nleeding and have done a software update
I get an error when connecting to the EQ8 mount with EGMOD driver
2015-08-27T01:41:21: Error: -> Error connecting to port /dev/ttyUSB0: Port failure Error: Permission denied. Try adding your user to the dialout group and restart (sudo adduser $USER dialout)
2015-08-27T01:41:21: connecting to port /dev/ttyUSB
I have done the dialout user and still no improvement
My mount connects to the windows ascom eqmod no problem

Any ideas??
,,, Bruce

Alignment fail - by: sbothe

$
0
0
Hello,
after updating my system today the alignment tool in EKOS doesn´t work.
When I test the solver with the CCD-Simulator, I became this output: 2015-08-27T09:39:40 Solver failed. Try again. 2015-08-27T09:39:39 Starting solver...
Two days ago everything has worked without problems and I have nothing changed.

The online solver works.

Docking windows - by: seanhoughton

$
0
0
I seem to be constantly battling the window layout with kstars/ekos/fits/etc. For example:
  • Clicking on the kstars main window and the Ekos window disappears
  • INDI control panel is always drawn over kstars
  • FITS previewer is always drawn over kstars, but can alternate focus over the INDI control panel

I haven't looked at the code yet, but it would be really convenient if we could dock/tab these windows to create a control panel with a predictable layout. Is anyone else dealing with this? Have I missed some window layout technique?

Clestron mounts and hibernate - by: dokeeffe

$
0
0
Just wondering, has anyone found some way of hibernating (and waking from hibernation) celestron mounts.
I have a CPC1100 and would like to use INDI for remote use. I'd like to power off the mount but I think I need to enable hibernation first....
I know I can do this with the nexremote software on windows, but I'd prefer some way to do this from linux and eventually script it.
Has anyone managed to reverse engineer the serial traffic that happens when hibernate is enabled?

Thanks,
Derek

Issue with ZWO ASI120MM - by: klaus

$
0
0
I'm again facing problems with my ASI120MM. Having connected it directly to my PC and using Telescope Simulator in Kstars/Ekos, I get the following error messages and taking an image is impossible.

2015-08-31T09:07:21: ASIStartExposure error (14)
2015-08-31T09:07:21: ASIStartExposure error (14)
2015-08-31T09:07:21: ASIGetExpStatus timeout out (0)
2015-08-31T09:06:15: ASIGetExpStatus timeout out (0)
2015-08-31T09:05:47: ASIGetExpStatus timeout out (0)
2015-08-31T09:02:41: Device configuration applied.
2015-08-31T09:02:41: ASISetROIFormat (1280x960 @ 1) error (9)
2015-08-31T09:02:41: ASISetROIFormat (1280x960 @ 1) error (9)
2015-08-31T09:02:41: Upload settings set to client only.
2015-08-31T09:02:41: Loading device configuration...
2015-08-31T09:02:41: CCD is online. Retrieving basic data.

The software is up to date from Jasem's ppa and the cam works just fine with oacapture so it isn't a hardware issue.

Any ideas?

Klaus

Building astrometry.net - by: Besson

$
0
0
I'm installing a fresh Kubuntu 15.04 on my PC and then start to install, INDI, KSTARS and ASTROMETRY. I've followed the topic HOWTO: Building latest libindi & Ekos

On the step , 5. "Building Astromery.net" I've got few errors related to python configuration. To solve that I've added these packages as indicate on the astrometry site.

sudo apt-get install libcairo2-dev libnetpbm10-dev netpbm libpng12-dev libjpeg-dev python-numpy python-pyfits python-dev zlib1g-dev libbz2-dev swig cfitsio-dev

cfitsio-dev seems not available for K15.04, but it my be replaced by libcfitsio3-dev already installed in step 2 "Building INDI from Source"

If I'm correct it could be great to added this instruction on the topic.

cheers Philippe.

indi_eqmod_telescope not starting - by: klaus

$
0
0
Software is up to date on my Kubuntu 15.04 Laptop and worked several weeks ago. It is not a hardware issue as the mount works correctly on Windows/ASCOM.

klaus@sirius:~$ indiserver -vvv indi_eqmod_telescope
2015-09-03T16:55:59: startup: indiserver -vvv indi_eqmod_telescope
2015-09-03T16:55:59: Driver indi_eqmod_telescope: pid=3867 rfd=3 wfd=6 efd=7
2015-09-03T16:55:59: listening to port 7624 on fd 4
2015-09-03T16:55:59: Driver indi_eqmod_telescope: sending msg copy 1 nq 1:
<getProperties version='1.7'/>

2015-09-03T16:55:59: Driver indi_eqmod_telescope: stderr EOF
2015-09-03T16:55:59: Driver indi_eqmod_telescope: restart #1
2015-09-03T16:55:59: Driver indi_eqmod_telescope: pid=3871 rfd=0 wfd=6 efd=7
2015-09-03T16:55:59: Driver indi_eqmod_telescope: sending msg copy 1 nq 1:
<getProperties version='1.7'/>

2015-09-03T16:56:00: Driver indi_eqmod_telescope: stderr EOF
2015-09-03T16:56:00: Driver indi_eqmod_telescope: restart #2
2015-09-03T16:56:00: Driver indi_eqmod_telescope: pid=3875 rfd=0 wfd=6 efd=7
2015-09-03T16:56:00: Driver indi_eqmod_telescope: sending msg copy 1 nq 1:
<getProperties version='1.7'/>

and so on ...

lsusb shows the serial adapter, /dev/ttyUSB0 is there and dialout, well, yes. So where is the problem?

Can anyone confirm this or has a running system comparable to mine?

Klaus
Viewing all 14088 articles
Browse latest View live