BGE5510 type DeEnKe motor controller manufacturer direct supply

BGE5510 type DeEnKe motor controller manufacturer direct supply

German Dunkermotoren Motor Controller BGE 5510

Compact 4-quadrant controller for controlling brushless DC motors with a continuous output power of up to 250 W

Standard configuration includes 2 RJ45 plugs and terminal connections for bus interfaces

Connection options for additional encoders and brakes

Free programmability (C)

Safe Torque Off is available upon request

Control through CANopen (CO) or independent operation (IO) through digital and analog inputs

Dukermotoren motor controller BGE 5510 detailed parameters:

Electronic device power supply voltage VDC 9-30

Rated voltage of power supply VDC 9-55

Peak output current Apk 30

Continuous output current A 10 24VDC 6 48VDC

Electronic current consumption mA~70

Operation mode - Slave (CO), Independent (I/O)

Standard Interface - CANopen (DSP402)

Safety Function - STO

Motor encoder input - Hall, incremental

Digital Input -6

Digital output -3

Analog input (-10V+10V) -1

Dimensions (length x width x height) mm 100x35x120

Weight kg 0.17

The function of the Dunkermotoren controller is to command and coordinate the operation of various computer components. The controller consists of a program counter, instruction register, instruction decoder, timing generator, and operation controller.

What is a Dunkermotoren controller?

DeEnKe controller refers to a master command device that controls the starting, speed regulation, braking, and reverse of an electric motor by changing the wiring of the main circuit or control circuit in a predetermined order and changing the resistance value in the circuit. Composed of program counters, instruction registers, instruction decoders, timing generators, and operation controllers, it is the "decision-making body" that issues commands, that is, it completes the coordination and command of the entire computer system's operations.

Dunkermotoren controllerBasic functions:

Data buffering: Due to the low speed of I/O devices and the high speed of CPU and memory, a buffer must be set up in the controller. When outputting, use this buffer to temporarily store data transmitted from the host at high speed, and then transfer the data in the buffer to the I/O device at the rate that the I/O device has; During input, the buffer is used to temporarily store data sent from the I/O device. After receiving a batch of data, the data in the buffer is quickly transmitted to the host.

Error control: The device controller also manages the transmission from I/O devices

Perform error detection on the incoming data. If an error is found during transmission, the error detection code is usually set and reported to the CPU. The CPU then cancels the data transmitted this time and performs a new transmission. This ensures the accuracy of data input.

Data exchange: This refers to the exchange of data between CPUs and controllers, as well as between controllers and devices. For the former, data is written to the controller in parallel by the CPU through the data bus, or read from the controller in parallel; For the latter, the device inputs data into the controller or transmits data from the controller to the device. For this purpose, data registers must be set up in the controller.

Status description: The controller that identifies and reports the status of the device should record the device's status for the CPU to understand. For example, the CPU can only start the controller to read data from the device when it is in the ready to send state. For this purpose, a status register should be set up in the controller, where each bit reflects a certain state of the device. After the CPU reads the contents of the register, it can understand the status of the device.

Receive and recognize commands: The CPU can send multiple different commands to the controller, and the device controller should be able to receive and recognize these commands. For this purpose, the controller should have corresponding control registers to store received commands and parameters, and decode the received commands. For example, a disk controller can receive 15 different commands such as Read, Write, Format, etc. sent by the CPU, and some commands also have parameters; Correspondingly, there are multiple registers and command decoders in the disk controller.

Address recognition: Just like every unit in memory has an address, every device in the system also has an address, and the device controller must be able to recognize the address of each device it controls. In addition, in order for the CPU to write (or read) data to (or from) registers, these registers should have addresses.

BGE5510 type DeEnKe motor controller manufacturer direct supply