You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stupidly, there is a copy-paste error in the CAN API Swift wrapper that prevents to set message flags other than standard frames for transmit messages.
Wrong:
publicstructMessage {
publicstructFlags: OptionSet {
// message flags as option setpublicstaticletStandardFrame=Flags([])
publicstaticletExtendedFrame=Mode(rawValue: 0x01)
publicstaticletRemoteFrame=Mode(rawValue: 0x02)
publicstaticletCanFdLongFrame=Mode(rawValue: 0x04)
publicstaticletCanFdFastFrame=Mode(rawValue: 0x08)
// message flags from C interface
...
Much better:
publicstructMessage {
publicstructFlags: OptionSet {
// message flags as option setpublicstaticletStandardFrame=Flags([])
publicstaticletExtendedFrame=Flags(rawValue: 0x01)
publicstaticletRemoteFrame=Flags(rawValue: 0x02)
publicstaticletCanFdLongFrame=Flags(rawValue: 0x04)
publicstaticletCanFdFastFrame=Flags(rawValue: 0x08)
// message flags from C interface
...
Stupidly, there is a copy-paste error in the CAN API Swift wrapper that prevents to set message flags other than standard frames for transmit messages.
Wrong:
Much better:
See also KvaserCAN issue #12
The text was updated successfully, but these errors were encountered: