![]() Though reading through this now it sounds like from the constructor this is used to just send a set amount of data to the certain device as the Constructor takes care of most of the 29 bits and you are just finishing up the API portion of the message system and then providing specific data to the CAN device or receiving data from that device specifically if its not part of the normal WPI Library. Public boolean readPacketNew(int apiId, ) Public void writePacket(byte data, int apiId) Or is this a separate part of information that is sent over the network? I am guessing that the API Class and the API Index basically act as my message or my data that is being sent right? Because in the CAN Class you have a data amount of 8 bits that can be sent. I see how the messageID is built in the 29 bits. Specifically, FRC CAN devices use the 29-bit ID field, with an FRC-specific segmentation of the 29 bits into things like device ID and manufacturer. Well, the messages do in fact contain the address of a specific device on the bus, but they’re also received by all of the nodes. But that maybe easier to work with since the granular side of it might get to complex. Now I look at the CAN Class and its a lot easier but maybe not as granular for working with. It seems like we have multiple terms that mean the same thing and I just want to fully grasp the information provided. Desktop Editor for Online version of ScreenSteps The latest version is 4.5.0 build 716 released FebruFor instructions on installing and configuring the desktop application please refer to How to Download and Connect the desktop software to your account article in the ScreenSteps manual. Is this correct? If so how would you ID a second device that is similar? or is the messageID the whole 28bit arbitration ID? Lastly what would the messageIDMask be? Same with bytebuffer timestamp and the int Periodms? I just want to make sure I am fully understanding all the terms. Public static byte FRCNetCommCANSessionMuxReceiveMessage( messageID,Īnother question I have is the messageID since I am looking at the CAN Device Specs sheet you linked I want to clarify that the messageID is just the 10 bit value needed to id a particular command or message type. ![]() But with the following line I can send info out and there is another for receive.įRCNetCommCANSessionMuxSendMessage(int messageID, Thanks I saw that api and was not sure it was the same thing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |