Pololu Simple High-Power Motor Controller 24v12 + Nvidia Jetson tx2

Support Motor controllers/drivers and motors
1

Hi. I connected Pololu Simple High-Power Motor Controller 24v12 to Nvidia Jetson tx2 (Ubuntu 16.04). Result lsusb:
nvidia@tegra-ubuntu:~/Downloads/smc_linux$ lsusb

Bus 002 Device 002: ID 2109:0813 VIA Labs, Inc.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 015: ID 1ffb:009a
Bus 001 Device 016: ID 1ffb:00a1
Bus 001 Device 005: ID 046e:52cc Behavior Tech. Computer Corp.
Bus 001 Device 004: ID 1c4f:0034 SiGma Micro
Bus 001 Device 003: ID 14cd:8601 Super Top
Bus 001 Device 002: ID 2109:2813 VIA Labs, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

But the Control Center determines and connects to the controller.

2

Hello.

What is the issue you are having with the Simple Motor Controller (SMC)? Can you please clarify your question(s)?

Judging from the pattern of your lsusb command output, it seems like you are expecting to see a manufacturer and device name for the Simple Motor Controller (SMC) in that list. We are not listed in the database that lsusb uses to find those names, so you will not see that added description. The SMC USB devices are the two starting with 1ffb, which is our vendor ID.

- Amanda

3

I want to manage these controllers.
In your example, Cross-platform C Example, the path to the controller “/ dev / ttyACM0”, but there is no such device:

nvidia@tegra-ubuntu:~$ ll /dev/tty*
crw-rw-rw- 1 root   tty       5,  0 Aug 16 06:39 /dev/tty
crw--w---- 1 root   tty       4,  0 Aug 16 06:39 /dev/tty0
crw--w---- 1 root   tty       4,  1 Aug 16 06:39 /dev/tty1
crw--w---- 1 root   tty       4, 10 Aug 16 06:39 /dev/tty10
crw--w---- 1 root   tty       4, 11 Aug 16 06:39 /dev/tty11
crw--w---- 1 root   tty       4, 12 Aug 16 06:39 /dev/tty12
crw--w---- 1 root   tty       4, 13 Aug 16 06:39 /dev/tty13
crw--w---- 1 root   tty       4, 14 Aug 16 06:39 /dev/tty14
crw--w---- 1 root   tty       4, 15 Aug 16 06:39 /dev/tty15
crw--w---- 1 root   tty       4, 16 Aug 16 06:39 /dev/tty16
crw--w---- 1 root   tty       4, 17 Aug 16 06:39 /dev/tty17
crw--w---- 1 root   tty       4, 18 Aug 16 06:39 /dev/tty18
crw--w---- 1 root   tty       4, 19 Aug 16 06:39 /dev/tty19
crw--w---- 1 root   tty       4,  2 Aug 16 06:39 /dev/tty2
crw--w---- 1 root   tty       4, 20 Aug 16 06:39 /dev/tty20
crw--w---- 1 root   tty       4, 21 Aug 16 06:39 /dev/tty21
crw--w---- 1 root   tty       4, 22 Aug 16 06:39 /dev/tty22
crw--w---- 1 root   tty       4, 23 Aug 16 06:39 /dev/tty23
crw--w---- 1 root   tty       4, 24 Aug 16 06:39 /dev/tty24
crw--w---- 1 root   tty       4, 25 Aug 16 06:39 /dev/tty25
crw--w---- 1 root   tty       4, 26 Aug 16 06:39 /dev/tty26
crw--w---- 1 root   tty       4, 27 Aug 16 06:39 /dev/tty27
crw--w---- 1 root   tty       4, 28 Aug 16 06:39 /dev/tty28
crw--w---- 1 root   tty       4, 29 Aug 16 06:39 /dev/tty29
crw--w---- 1 root   tty       4,  3 Aug 16 06:39 /dev/tty3
crw--w---- 1 root   tty       4, 30 Aug 16 06:39 /dev/tty30
crw--w---- 1 root   tty       4, 31 Aug 16 06:39 /dev/tty31
crw--w---- 1 root   tty       4, 32 Aug 16 06:39 /dev/tty32
crw--w---- 1 root   tty       4, 33 Aug 16 06:39 /dev/tty33
crw--w---- 1 root   tty       4, 34 Aug 16 06:39 /dev/tty34
crw--w---- 1 root   tty       4, 35 Aug 16 06:39 /dev/tty35
crw--w---- 1 root   tty       4, 36 Aug 16 06:39 /dev/tty36
crw--w---- 1 root   tty       4, 37 Aug 16 06:39 /dev/tty37
crw--w---- 1 root   tty       4, 38 Aug 16 06:39 /dev/tty38
crw--w---- 1 root   tty       4, 39 Aug 16 06:39 /dev/tty39
crw--w---- 1 root   tty       4,  4 Aug 16 06:39 /dev/tty4
crw--w---- 1 root   tty       4, 40 Aug 16 06:39 /dev/tty40
crw--w---- 1 root   tty       4, 41 Aug 16 06:39 /dev/tty41
crw--w---- 1 root   tty       4, 42 Aug 16 06:39 /dev/tty42
crw--w---- 1 root   tty       4, 43 Aug 16 06:39 /dev/tty43
crw--w---- 1 root   tty       4, 44 Aug 16 06:39 /dev/tty44
crw--w---- 1 root   tty       4, 45 Aug 16 06:39 /dev/tty45
crw--w---- 1 root   tty       4, 46 Aug 16 06:39 /dev/tty46
crw--w---- 1 root   tty       4, 47 Aug 16 06:39 /dev/tty47
crw--w---- 1 root   tty       4, 48 Aug 16 06:39 /dev/tty48
crw--w---- 1 root   tty       4, 49 Aug 16 06:39 /dev/tty49
crw--w---- 1 root   tty       4,  5 Aug 16 06:39 /dev/tty5
crw--w---- 1 root   tty       4, 50 Aug 16 06:39 /dev/tty50
crw--w---- 1 root   tty       4, 51 Aug 16 06:39 /dev/tty51
crw--w---- 1 root   tty       4, 52 Aug 16 06:39 /dev/tty52
crw--w---- 1 root   tty       4, 53 Aug 16 06:39 /dev/tty53
crw--w---- 1 root   tty       4, 54 Aug 16 06:39 /dev/tty54
crw--w---- 1 root   tty       4, 55 Aug 16 06:39 /dev/tty55
crw--w---- 1 root   tty       4, 56 Aug 16 06:39 /dev/tty56
crw--w---- 1 root   tty       4, 57 Aug 16 06:39 /dev/tty57
crw--w---- 1 root   tty       4, 58 Aug 16 06:39 /dev/tty58
crw--w---- 1 root   tty       4, 59 Aug 16 06:39 /dev/tty59
crw--w---- 1 root   tty       4,  6 Aug 16 06:39 /dev/tty6
crw--w---- 1 root   tty       4, 60 Aug 16 06:39 /dev/tty60
crw--w---- 1 root   tty       4, 61 Aug 16 06:39 /dev/tty61
crw--w---- 1 root   tty       4, 62 Aug 16 06:39 /dev/tty62
crw--w---- 1 root   tty       4, 63 Aug 16 06:39 /dev/tty63
crw--w---- 1 root   tty       4,  7 Aug 16 06:39 /dev/tty7
crw--w---- 1 root   tty       4,  8 Aug 16 06:39 /dev/tty8
crw--w---- 1 root   tty       4,  9 Aug 16 06:39 /dev/tty9
crw------- 1 nvidia tty       4, 64 Aug 16 06:39 /dev/ttyS0
crw-rw---- 1 root   dialout   4, 65 Aug 16 06:39 /dev/ttyS1
crw-rw---- 1 root   dialout   4, 66 Aug 16 06:39 /dev/ttyS2
crw-rw---- 1 root   dialout   4, 67 Aug 16 06:39 /dev/ttyS3
crw-rw---- 1 root   dialout 238,  1 Aug 16 06:39 /dev/ttyTHS1
crw-rw---- 1 root   dialout 238,  2 Aug 16 06:39 /dev/ttyTHS2
crw-rw---- 1 root   dialout 238,  3 Aug 16 06:39 /dev/ttyTHS3

Accordingly, there is no way to open the connection.

4

Can you make sure the cdc-acm kernel module is available by running modinfo cdc_acm and modprobe -c | grep cdc_acm?

If it is, can you disconnect and connect one of your SMCs from your Nvidia Jetson TX2 and run dmesg immediately after? Please post the output here. If the operating system connected the SMC as a serial port, running dmesg should show which port it is connected on.

- Amanda

5

Thanks for the help! Yes, this was the problem, I already decided!:+1: