ulrikhagstrom / datalinkengineeringcanopen Goto Github PK

Hi, I was wondering what the ARM compatibility of this API is?

After to make the changes, can setup these adapters on vci driver for windows?

Hi Ulrik,

Observing the CANbus when writing SDOs, a UINT32 with value 0xFFFFFFFF and then immediately writing a UINT8 with value 0x0C the value seen on the CAN bus is 0x0CFFFFFF. This creates a problem for the target CAN device I am using and throws it into an Emergency State.
To overcome this problem I have changed your code to reset to 0x00 the 4 data bytes in the buffer: not particularly elegant but it does seem to work.

canOpenStatus SDO :: setData(u32 val, u8 valid, u8 *n)
{
canOpenStatus ret = CANOPEN_ERROR;
if (valid > 0 && valid <= 4)
{
this->can_data_tx[4] = 0x00;
this->can_data_tx[5] = 0x00;
this->can_data_tx[6] = 0x00;
this->can_data_tx[7] = 0x00;
if (valid == 1)
{
::setU8Val((u8)val, this->can_data_tx, 4);
}
else if (valid == 2)
{
::setU16Val((u16)val, this->can_data_tx, 4);
}

I hope you can fix this issue for me, in the meantime I will use a modified version
Kind Regards
Guy Pender

It is unclear what units are used for the timeouts in e.g. the SDO client:

The scaling of the default values give an indication it might be microseconds.

Having to assume the units is unsafe. A suggestion is to rename the function parameters to e.g. timeout_microseconds, timeout_milliseconds etc and add suffixes to the default parameters.

Hi.

(sorry for using github issues, but contact form on http://www.datalink.se/ does not work at this time)

We recently purchased a license with no support but, after having completed library integration in our software, we hit a performance issue (i.e. time spent in a SDO transaction is about 75ms, much more than expected).

Could we extend license in order to get support about that issue?

Thanks.