Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CAN_MONI stopped working after updating to Ventura 13.7.1 #20

Open
TorstenRobitzki opened this issue Nov 12, 2024 · 4 comments
Open

CAN_MONI stopped working after updating to Ventura 13.7.1 #20

TorstenRobitzki opened this issue Nov 12, 2024 · 4 comments
Labels
analyzing Investigation required to understand the problem

Comments

@TorstenRobitzki
Copy link

Currently can_moni isn't working on hardware, I'm sure it is working.

  • No messages where reported
  • It takes unusual long for a newly connected peak can adapter to be recognized by the mac book (can_moni stops with an error message [+++ error: CAN_SetValue PCAN-USB1 (PCAN_LISTEN_ONLY=0) returned 0x1400])
  • In one case, only the "Hardware=PCAN-USB1...OK!" message was shown up, the following "Baudrate=1000kbps...OK!" was not shown.

This all happened, after updating to Ventura 13.7.1 (22H221).

Any idea, what the problem could be here?

@mac-can
Copy link
Owner

mac-can commented Nov 12, 2024

The issue cannot be reproduced.

I ran the stripped-down test suite with two CAN devices; only the known issues showed up here. I also ran the program can_moni from the Utilities repo and from the Wrapper repo; here, too, the CAN device was successfully initialized and all CAN messages sent were received in the correct order.

Test environment:

  • MacBook Pro (Intel, 2019)
  • macOS Ventura 12.7.1
  • PCAN-USB (product code: IPEH-002021)
  • PCAN-USB FD (product code: IPEH-004022)

@mac-can mac-can added the analyzing Investigation required to understand the problem label Nov 12, 2024
@TorstenRobitzki
Copy link
Author

Hi Uwe,
thanks for the fast response. can_moni worked fine till today. I can not even say for sure, that the update to Ventura 13.7.1 caused this issue. Are there some loggings I could switch on, or some other means to gather more informations?

best regards
Torsten

@TorstenRobitzki
Copy link
Author

I even updated the MacBook to 15.1., but can_moni still show no received data.

My application, that works with PCBUSB does not receive any error, when using the API, except for when I try to enable the logging of the library.

When I try to CAN_SetValue() for PCAN_LOG_TEXT or PCAN_LOG_CONFIGURE, I receive PCAN_ERROR_ILLOPERATION.

But the application stopped receiving any CAN messages.

@mac-can
Copy link
Owner

mac-can commented Nov 25, 2024

I even updated the MacBook to 15.1., but can_moni still show no received data.

My application, that works with PCBUSB does not receive any error, when using the API, except for when I try to enable the logging of the library.

When I try to CAN_SetValue() for PCAN_LOG_TEXT or PCAN_LOG_CONFIGURE, I receive PCAN_ERROR_ILLOPERATION.

But the application stopped receiving any CAN messages.

Parameter PCAN_LOG_* are not supported; see https://github.com/mac-can/PCBUSB-Library/blob/main/Binaries/Universal_64/README

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analyzing Investigation required to understand the problem
Projects
None yet
Development

No branches or pull requests

2 participants