Cannot run a default scheduler


41
views
0
5 months ago by
This is an output I am getting:

pi@raspberrypi:~/mep-master $ ls
LICENSE docs mep package-lock.json strategies
README.md install mep-master package.json test
config logs node_modules src validate
pi@raspberrypi:~/mep-master $ ./mep -c strategies/boilerplate/DefaulScheduler.js __ __ _ _
| \/ | ___ _ __ ___ _ __(_)___| |_ ___ _ __
| |\/| |/ _ \ |_ _ \| |__| / __| __/ _ \| __|
| | | | __/ | | | | | | | \__ \ || (_) | |
|_| |_|\___|_| |_| |_|_| |_|___/\__\___/|_| @2016-2017

17:09:18.818Z INFO mep: MEP (Memristor's Eurobot Platform) started!
17:09:18.821Z INFO mep: Active robot: big
17:09:18.822Z INFO mep: Active table: default
17:09:18.822Z INFO mep: Use simulation: false
17:09:18.823Z INFO mep: Scheduler terrain: strategies/boilerplate/DefaulScheduler.js
Cannot find device "can0"
DriverManager { Error: Command failed: sudo ip link set can0 down type can
Cannot find device "can0"

at checkExecSyncError (child_process.js:575:11)
at execSync (child_process.js:612:13)
at CanDriver._startCAN (/home/pi/mep-master/src/drivers/can/CanDriver.js:101:9)
at new CanDriver (/home/pi/mep-master/src/drivers/can/CanDriver.js:38:14)
at DriverManager._loadDriverBasic (/home/pi/mep-master/src/drivers/DriverManager.js:199:34)
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:190:28)
at DriverManager._resolveDependencies (/home/pi/mep-master/src/drivers/DriverManager.js:232:24)
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:184:32)
at DriverManager.init (/home/pi/mep-master/src/drivers/DriverManager.js:40:28)
at Function.init (/home/pi/mep-master/src/Mep.js:164:38)
status: 1,
signal: null,
output:
[ null,
<Buffer >,
<Buffer 43 61 6e 6e 6f 74 20 66 69 6e 64 20 64 65 76 69 63 65 20 22 63 61 6e 30 22 0a> ],
pid: 18379,
stdout: <Buffer >,
stderr: <Buffer 43 61 6e 6e 6f 74 20 66 69 6e 64 20 64 65 76 69 63 65 20 22 63 61 6e 30 22 0a> }
17:09:19.067Z ERROR mep:
DriverManager CanDriver is out of the order { Error: Command failed: sudo ip link set can0 down type can
Cannot find device "can0"

at checkExecSyncError (child_process.js:575:11)
at execSync (child_process.js:612:13)
at CanDriver._startCAN (/home/pi/mep-master/src/drivers/can/CanDriver.js:101:9)
at new CanDriver (/home/pi/mep-master/src/drivers/can/CanDriver.js:38:14)
at DriverManager._loadDriverBasic (/home/pi/mep-master/src/drivers/DriverManager.js:199:34)
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:190:28)
at DriverManager._resolveDependencies (/home/pi/mep-master/src/drivers/DriverManager.js:232:24)
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:184:32)
at DriverManager.init (/home/pi/mep-master/src/drivers/DriverManager.js:40:28)
at Function.init (/home/pi/mep-master/src/Mep.js:164:38)
status: 1,
signal: null,
output:
[ null,
<Buffer >,
<Buffer 43 61 6e 6e 6f 74 20 66 69 6e 64 20 64 65 76 69 63 65 20 22 63 61 6e 30 22 0a> ],
pid: 18379,
stdout: <Buffer >,
stderr: <Buffer 43 61 6e 6e 6f 74 20 66 69 6e 64 20 64 65 76 69 63 65 20 22 63 61 6e 30 22 0a> }
DriverManager Error: There is no driver with name CanDriver
at DriverManager.getDriver (/home/pi/mep-master/src/drivers/DriverManager.js:64:19)
at new MotionDriver (/home/pi/mep-master/src/drivers/motion/MotionDriver.js:98:47)
at DriverManager._loadDriverBasic (/home/pi/mep-master/src/drivers/DriverManager.js:199:34)
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:185:32)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
at Function.Module.runMain (module.js:705:11)
at startup (bootstrap_node.js:193:16)
at bootstrap_node.js:660:3
17:09:19.072Z ERROR mep:
DriverManager MotionDriver is out of the order Error: There is no driver with name CanDriver
at DriverManager.getDriver (/home/pi/mep-master/src/drivers/DriverManager.js:64:19)
at new MotionDriver (/home/pi/mep-master/src/drivers/motion/MotionDriver.js:98:47)
at DriverManager._loadDriverBasic (/home/pi/mep-master/src/drivers/DriverManager.js:199:34)
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:185:32)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
at Function.Module.runMain (module.js:705:11)
at startup (bootstrap_node.js:193:16)
at bootstrap_node.js:660:3
17:09:19.080Z ERROR mep: Cannot load driver `StarterDriver` because dependencies are out of order
Error: Cannot load driver `StarterDriver` because dependencies are out of order
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:187:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
at Function.Module.runMain (module.js:705:11)
at startup (bootstrap_node.js:193:16)
at bootstrap_node.js:660:3
17:09:19.082Z ERROR mep: Cannot load driver `RopePin` because dependencies are out of order
Error: Cannot load driver `RopePin` because dependencies are out of order
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:187:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
at Function.Module.runMain (module.js:705:11)
at startup (bootstrap_node.js:193:16)
at bootstrap_node.js:660:3
17:09:19.086Z ERROR mep: Cannot load driver `Lidar` because dependencies are out of order
Error: Cannot load driver `Lidar` because dependencies are out of order
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:187:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
at Function.Module.runMain (module.js:705:11)
at startup (bootstrap_node.js:193:16)
at bootstrap_node.js:660:3
17:09:19.090Z ERROR mep: Cannot load driver `LaserBackLeft` because dependencies are out of order
Error: Cannot load driver `LaserBackLeft` because dependencies are out of order
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:187:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
at Function.Module.runMain (module.js:705:11)
at startup (bootstrap_node.js:193:16)
at bootstrap_node.js:660:3
17:09:19.092Z ERROR mep: Cannot load driver `LaserBackRight` because dependencies are out of order
Error: Cannot load driver `LaserBackRight` because dependencies are out of order
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:187:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
at Function.Module.runMain (module.js:705:11)
at startup (bootstrap_node.js:193:16)
at bootstrap_node.js:660:3
17:09:19.093Z ERROR mep: Cannot load driver `LaserFrontCenter` because dependencies are out of order
Error: Cannot load driver `LaserFrontCenter` because dependencies are out of order
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:187:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
at Function.Module.runMain (module.js:705:11)
at startup (bootstrap_node.js:193:16)
at bootstrap_node.js:660:3
17:09:19.098Z ERROR mep: Cannot load driver `ColorSensor` because dependencies are out of order
Error: Cannot load driver `ColorSensor` because dependencies are out of order
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:187:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
at Function.Module.runMain (module.js:705:11)
at startup (bootstrap_node.js:193:16)
at bootstrap_node.js:660:3
17:09:19.106Z ERROR mep: Cannot load driver `ServoCollectorStopper` because dependencies are out of order
Error: Cannot load driver `ServoCollectorStopper` because dependencies are out of order
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:187:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
at Function.Module.runMain (module.js:705:11)
at startup (bootstrap_node.js:193:16)
at bootstrap_node.js:660:3
17:09:19.107Z ERROR mep: Cannot load driver `VacuumPump` because dependencies are out of order
Error: Cannot load driver `VacuumPump` because dependencies are out of order
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:187:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
at Function.Module.runMain (module.js:705:11)
at startup (bootstrap_node.js:193:16)
at bootstrap_node.js:660:3
17:09:19.109Z ERROR mep: Cannot load driver `Cylinder` because dependencies are out of order
Error: Cannot load driver `Cylinder` because dependencies are out of order
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:187:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
at Function.Module.runMain (module.js:705:11)
at startup (bootstrap_node.js:193:16)
at bootstrap_node.js:660:3
17:09:19.110Z ERROR mep: Cannot load driver `FunnyServo` because dependencies are out of order
Error: Cannot load driver `FunnyServo` because dependencies are out of order
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:187:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
at Function.Module.runMain (module.js:705:11)
at startup (bootstrap_node.js:193:16)
at bootstrap_node.js:660:3
17:09:19.111Z ERROR mep: Cannot load driver `ServoCollectorTrackLeft` because dependencies are out of order
Error: Cannot load driver `ServoCollectorTrackLeft` because dependencies are out of order
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:187:27)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:118:7)
at Function.Module.runMain (module.js:705:11)
at startup (bootstrap_node.js:193:16)
at bootstrap_node.js:660:3
17:09:19.112Z ERROR mep: Cannot load driver `ServoCollectorHandLeft` because dependencies are out of order
Error: Cannot load driver `ServoCollectorHandLeft` because dependencies are out of order
at DriverManager._initDriver (/home/pi/mep-master/src/drivers/DriverManager.js:187:27)
at <anonymous>
Community: Memristor

1 Answer


2
5 months ago by
If you look at
17:09:18.823Z INFO mep: Scheduler terrain: strategies/boilerplate/DefaulScheduler.js
Cannot find device "can0"
DriverManager { Error: Command failed: sudo ip link set can0 down type can
Cannot find device "can0"

You will see the issue, CAN driver doesn't work properly. Under the hood, it runs the following command and it is failing:
sudo ip link set can0 down type can

Please check the following link:
https://github.com/Memristor-Robotics/mep-master/tree/master/src/drivers/can
Please login to add an answer/comment or follow this question.

Similar posts:
Search »
  • Nothing matches yet.