Linux support

[Kevin C]

Hey all, just received my spectra, hardware looks great, and the software looks nice.

The problem is I can't get them to work together.

I have the spectra connected via USB port.

I have the requirements installed into a virtualenv and can run it regularly or as root.

But it does not see as though pyserial is able to find the device.

The error is:

```

(eit) user@computer:~/python/OpenEIT$ sudo /home/user/.virtualenvs/eit/bin/python app.py 

2019-10-05 15:50:34,221 JAC mesh set up 

completed jac reset

2019-10-05 15:50:36,289 JAC mesh set up 

completed jac reset

d

2019-10-05 15:50:36,390 openeit_server_started

 * Serving Flask app "app" (lazy loading)

 * Environment: development

 * Debug mode: off

none

connecting to:  none

could not connect

2019-10-05 15:50:47,433 Cannot connect to none

problem

```

I have tried to search for serial devices with:

```

python -m serial.tools.list_ports -v

no ports found

```

Additionally, it does not seem as though any devices are available under `dmesg`.

Does it require a battery to run? Do I need particular drivers? Is there another switch to put it in serial mode?

Is there anything else I should be doing?

Thanks!

[Jean Rintoul]

Thanks - the fact that no ports are found is pretty suspect. For reference - each and every device has been tested to detect a com port before being sent out, so try the following.

1. Firstly, check if your device is turned on(See attached picture to this email): 

https://github.com/OpenEIT/OpenEIT

This will enable bluetooth and serial comms on the device, and the remaining question is whether your linux install is supporting FTDI VCP drivers, and can see other com port devices. 

2. I've been running Ubuntu which had the VCP drivers pre-installed, but I can't speak to all Linux installs. What Linux variant and version are you using? Have you tried these drivers? (https://www.ftdichip.com/Drivers/VCP.htm)

3. Pause on the dash install(it sounds fine) and just focus on the serial connection. Install another terminal program and try connecting to the device - can you see a com port now? Alternatively, try another serial device if you have one handy - does it show up with a com port(this will tell you if your serial drivers are working on your OS at all)? 

Please post your results so we can all learn. 

Best, 

--
You received this message because you are subscribed to the Google Groups "OpenBiomedicalImaging" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openbiomedicalim...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openbiomedicalimaging/48b5c44b-af01-4be5-80e1-8fb2f335b241%40googlegroups.com.

[Kevin C]

Thanks for the fast response!

It was totally the switch - I had only moved it to the middle position, and not to the full on position.

The LED was on in all positions, so I was a little unsure if it was actually running or not.

For reference, I was using Ubntu 18.04 and with it on it showed up as a serial port;

```

$ python -m serial.tools.list_ports -v

/dev/ttyUSB0        

    desc: FT230X Basic UART

    hwid: USB VID:PID=0403:6015 SER=DM033OKR LOCATION=3-1

1 ports found

```

The application was able to query it and start on reconstructions.

Really looking forward to using this - thanks for all the hard work, I'll report back with some interesting experiments.