Hi @glennra,

Are you connecting the local USB of SOLO to your PC or you are using a UART to USB converter in between?

Milad

Hi Milad,

This is when using the onboard USB of the SOLO and a USB C to A dongle on laptop.

Glenn

Based on a recommendation on another post I tried to connect using an FT2232H USB-UART module.

This doesn't work by itself either but while it is connected the onboard USB connection seems to function correctly.

Glenn

Hi @glennra,

Two notes:

- While using the onboard USB of SOLO, the Baudrate doesn't matter and the Motion terminal can work with it on any baud rate, however, once you use a UART to USB converter, the baud rate matters for the Motion terminal, as in that case Motion terminal will only work with the baud rate of 937500 bits/s.

So if you've changed the baud rate of the UART line, you can get connected to the unit using the onboard USB and there change the Baudrate back to 937500, then after doing a power recycling, now you can get connected through the motion terminal and your UART to USB converter to SOLO, basically using a UART to USB converter is not necessary if your goal is to only use Motion terminal.

Posted by: @glennra

↑

This doesn't work by itself either but while it is connected the onboard USB connection seems to function correctly.

 

So you mean the onboard USB works only when the UART module is also connected? -- to this end may I know what is the firmware version of your device?

Milad

Hi Milad,

Model: MINI v2 [U]
Firmware: 0003B00E

So you mean the onboard USB works only when the UART module is also connected?

Yes, that is what it was doing. However today it has connected on the first try as expected via the virtual COM port, but after a disconnection it is now giving the "serial port is already open" error.

@glennra

Posted by: @glennra

↑

Yes, that is what it was doing. However today it has connected on the first try as expected via the virtual COM port, but after a disconnection it is now giving the "serial port is already open" error.

 

I believe this is probably related to Motion Terminal, I'm forwarding the request to the software team to check it up.

We have also released the latest firmware and the team is working on releasing it, maybe that can help too in some rare cases, we hope in a couple of days we have it ready, we will keep you posted.

Milad

Hi @glennra,

We have released a new Firmware version, please go to Motion Terminal, press Crt+F5 to update your cache, and download the latest firmware from there, and by following the guides you should be able to update your device to firmware '0000B00F".

Please test this and let me know if the connection issue is still there or not.

Milad

According to https://www.solomotorcontrollers.com/resources/updating-solo/ Motion Terminal should offer a firmware update.

This is not happening. Ctrl+F5 and Cmd+R5 do nothing. Motion Terminal is v2.3.1.

I assume that you meant that the firmware should update to '0003B00F' rather than '0000B00F'

Hi @glennra

Below is the URL to the latest Motion terminal: https://www.solomotorcontrollers.com/SOLO-motion-terminal/

Seems your Browser URL is fixed at V2.3.1 -- the best is to use https://www.solomotorcontrollers.com/SOLO-motion-terminal/   and then there pressing Crt+F5

FW 3B00E was the older version, with Motion Terminal 2.4.0 you should be able to update your unit to 000B00F.

Please test this and if after updating you still had the issue, get in touch with us on support[at]solomotorcontrollers.com

Milad

Hi Milad,
The update hasn't helped. It still won't connect.

Motion Terminal 2.4.0 log:

usbProductId: 2 usbVendorId: 7358
app.e8e5f789.js:1 NO READING
app.e8e5f789.js:1 Port Open Failure
app.e8e5f789.js:1 DOMException: Failed to execute 'open' on 'SerialPort': The port is already open.
at Proxy.init ( https://www.solomotorcontrollers.com/SOLO-motion-terminal/)
at async Proxy.soloConnect ( https://www.solomotorcontrollers.com/SOLO-motion-terminal/)

Hi Glennra,

the problem you see it show when the communication is not fully closed between PC and the Unit and you try to open again the communication.

- The first recommendation is to try to use only 1 Motion terminal page, and when you want to reconnect you refresh the page too.

- The second consideration is to try to use the communication between the Unit and PC without have external hardware as hub/dongle to see if it stable in that case. 

- The last less probably is about the USB cable too, have a test with different USB data cable to ensure there are no external noise, but I suppose you are not using an abnormal long cable for the tests 

Please have a check about this considerations.