hardbyte / hardbyte/python-can
Vector 1610 wont connect, XL will
- Dominant language
- Python
- Stars
- 1.6k
- Forks
- 697
- PR merge metrics
- No merged PRs in 30d
Description
### Describe the bug
I started using the CanCaseXL channel 1 and it worked right away. I moved to a Vector 1630 using Channel 3. Now I get the following error for using channel 1 or 3. The mapping looks correct, is there an issue with the 1630?
Exception has occurred: VectorInitializationError
xlGetApplConfig failed (Vector HW Config: Channel '1' of application 'mf' is not assigned to any interface) [Error Code 255]
can.interfaces.vector.exceptions.VectorInitializationError: xlGetApplConfig failed (XL_ERROR) [Error Code 255]
During handling of the above exception, another exception occurred:
File "D:\Users\mflood\OneDrive\CAN_Decoder\MFCan.py", line 78, in CAN_Driver
self.CANbus = can.Bus(interface='vector',
File "D:\Users\mflood\OneDrive\CAN_Decoder\Receive_all.py", line 76, in
MFCan.CAN_Driver() #attach the vector driver
can.interfaces.vector.exceptions.VectorInitializationError: xlGetApplConfig failed (Vector HW Config: Channel '1' of application 'mf' is not assigned to any interface) [Error Code 255]


### To Reproduce
### Expected behavior
### Additional context
OS and version: win10, py38
Python version: 3.8
python-can version: 4.1
python-can interface/s (if applicable): Vector 1630A
Traceback and logs
```python
def func():
return "hello, world!"
```
Contributor guide
Assessment
This issue has not been assessed yet.