I am sending this information on behalf Of kurtus_h who originally discussed this issue with You. Your response to him was: To kurtus_h I believe there is something else wrong than just changing to extended ID. 255 XL_ERROR means the driver doesn't know what went wrong. When this error appears (mostly during development) I unplug the hardware and plug it back in again to fully reinitialize the driver. I can assure you that both STD and EXT CAN settings work properly. If you have modified the code and there is something wrong with it you will have to attach it. Kurtus has asked me to forward this information to you. As you can see the “Receive” VI seems to be working correctly even though the idRange is “STD” If I switch To “EXT”, I get an error which is shown in the next example. The code has not been modified in either example. See Images 1-3 With regard to the transmit example: As you can see by the next two images, I modified the Baudrate from 250 to 500 K and I changed the id and message to something that is valid for my device. Everything else remained unchanged. See Images 4-5 I then switched from “STD” to “EXT” with the following results: As you can see the error code is different. I am including the diagram to show that the only thing changed was “STD” to “EXT” along with the baud rate. See Images 6-7 At this point I switched back to run the “receive” example and as you can see the “receive” no longer works. See Image 8 After cycling of the power to the CANcaseXL it functions correctly. See Image 9 Any assistance you can provide would be graeatly appreciated.

I think my last post answers your question. I may have posted my answer while you were composing your last question. If you transmit a CAN message with ID 0x88FF8201 from the vxlapi it will appear on the bus as an extended CAN message with an ID of 0x8FF8201. If you transmit a CAN message with ID 0x80000001 from the vxlapi it will appear on the bus as an extended CAN message with an ID of 0x1.

ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

vxlapi

Solved!

Author

Yes thats exactly what happened

Thankyou

Message 11 of 11

(1,034 Views)

LabVIEW

vxlapi

Re: vxlapi