make sure they have common grounds, testing from a PC though, the USB cable is already grounded to the PC so that will work for sure, but you need a ground from teensy to your device if you want them to talk
the contact has a miniscule resistance which wont beep, you should be able to see the value though if your reading the ohms, like taking a resistor and trying to check if the voltmeter beeps :)
that spammer who posted here i messaged him on facebook to stop flooding the forums and reported him, he “viewed” my message within a minute and never responded. He’s definately doing it on purpose
you need IFCT, Circular_Buffer, and CANquitto libraries installed in arduino user folders,
You can’t write to Node, it is a singleton class just for the master node config. You need to construct a node to talk to...
This looks really bad, you must have a typo somewhere that could be causing even primitives to be not declared in the scope :o
A thing I hate about the ESP is when I wrote a library with an array that was initialized...
Today's update for CANquitto:
Wire (I2C) has now been integrated into the protocol. It's based off Wire.h from Teensyduino. This week I plan to add i2c_t3 methods as well, the library will give you a choice to run...
Hi Paul, I'm poking around the Wire libraries for Teensy 3.x for user option choice for I2C over CANquitto, and noticed that i2c_t3.h has Wire3 declared but Wire.h throws a compile error, only Wire,Wire1,Wire2 are...
Hi all, I just finished adding buffered read support to Serial class!
myNode.Serial.read(buffer,len);
Just like the original function, a value is returned with whatever bytes came in that were available. If you...
Greetings, more stuff has been added!
Serial available, peek, and read have been added, and some minor misguided bugs have been removed :)
The Serial objects of all the nodes are now part of the Stream class! This...
reed relays are silent, to an extent, you'd have to be very close to it to actually hear it, like silent room with ear near it... when power is applied, a magnetic charge shifts a tube inside to make contact.
You probably only need a 74HCT4066(TTL) for that type of thing. Use a gpio to trigger a pin and the bilateral switch will join the contacts of the camera
CANquitto has been revamped with a new redesign! It's faster, lots less overhead, and hardware capabilities are now growing.
The new version also allows:
GPIO controls, currently digitalRead/digitalWrite,toggle.
...
you havn’t tried all libraries. there are multiple forks of those libraries some work some don’t. i believe the working one you need to search the forums for nmea2000 and you’ll find it. there is also a new one called...
Good evening everyone. In an effort to pull more performance and stability into CANquitto multi-master protocol, it's been in it's second redesign which is running pretty well. The nodes are written in 0ms loops...
SPI is the fastest you could get between 2 teensies, then your limited by the bandwidth of USB to PC at each end. If you do choose UART though it might be a good idea to attach the RTS & CTS lines and run it at 6megabaud
CANquitto now uses new feature of CBA which allows an updated list of active nodes to be kept track of. ::write uses it to check if a node is available before writing to it, otherwise it exits with a return value of 0....
I don't know about an entire single payload of 10MB, might not be feasable in terms of memory. The uart may be capable of delivering it but the controller wont be able to store it in memory. You'll have to send it as...
IFCT Update: now has a separated TX buffer for Can1, so written queued frames would be consumed by the ISR at their respective buffers, especially when sequential writes are used.
New feature added to Circular Buffer Arrays: findRemove.
This has the same capability as find and replace methods, however, instead of finding or replacing, this actually removes the item from the queue. This method...
you could send the data over mqtt, dont know what type of server you have planned? the teensquitto protocol can be manipulated at the ESP end if needed, where the entire payload you send from teensy appears as one big...
theres 3 libraries you can try:
1) CollinK’s FlexCAN Library with mailbox only support
2) Pawelsky’s FlexCAN Library fork with FIFO only support
3) IFCT, which is new, supports both, and has alot of advanced...
This thread has been unanswered so if you are still working on the project, the flexcan controller on teensy supports up to 16 mailboxes, 32 (2x16) on a Teensy 3.6 (if you run them in parallel).
The nice thing about...
https://github.com/SuperDroidRobots/Encoder-Buffer-Library/blob/master/Encoder_Buffer.cpp
According to the CPP:
Encoder_Buffer::Encoder_Buffer(int _slaveSelectEnc){
slaveSelectEnc = _slaveSelectEnc;
...
thats usually what i did for spi_mst when finding the port register for the spi cs pin, i set the pin as output asserted and checked the ports to see which had the bit set. in his case he could set all the ports to...
you could use a gpio pin to select which program starts/runs, or a comms signal/display touch activation
many possibilities.
If you write the code good enough, you can change back and forth during runtime without...
oduyong, I added bus reception support and transmit as well.
You can setup up to 127 nodes globally, NOT per bus.
To identify the bus in the callback from where the node originated, check the info.bus flag if it's 0...
Yes can0 only supported for now until stability is better, then will add Can1 :)
the problem is sharing the buffer, we need it stable first on one bus before combining both busses into same buffer for sorting
The event handling for CANquitto was redesigned to allow the ISR to be the only consumer/producer for both buffers while not processing, and while processing only the primary buffer was handled by the ISR. Next while...
Greetings all. Pushing out a library in development for a teensy to teensy communication over CANbus. It may probably contain bugs that will hinder it's operation, but looking into ressolving them over time...
The...
yes so you only need one teensy and either or another teensy OR uart adaptor (3.3V TTL)
the clicking can be done when you send keystrokes from the terminal app easily
what kind of mouse commands, moving the cursor using absolute positioning or just clicking at a specific location?
you can do this with one teensy you dont need both (if you have a 3.3v TTL uart adaptor).
teensy...
Ok.... so you want terminal on one pc to talk to terminal on other PC?
if this is correct you just need to connect the UART lines between both teensies and pass their data inputs over to USBserial
Here is a new video update of a Teensy 3.2 talking to a Teensy 3.6 and vice versa. They are sending their own data to each other.
The 3.2 is sending an array of 1234 bytes, while the 3.6 is sending a char array to...
does the motor have a separate supply? if you’re powering it off the same USB source as teensy that quick draw could be normal to reset. motors draw alot of current
Looks like we're getting better results! Will need to tweak a few more events but CANquitto is now able to transfer 8100 bytes over CANbus Teensy 3.2 <--> Teensy 3.6
PAYLOAD!!: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16...
No problem. If you have any issues or features you would like to be added, let me know.
For others, as a side note for CANquitto, it's updated and transferring payloads over CAN of 1500 bytes successfully
Here are...
yes ill keep notes and fix later to separate the callbacks for can0 and 1.
you could also do a msg.bus to show which bus it came from from the callback currently (which you already did), ill try to have it patched...
IFCT comes back with yet another new update, with a custom protocol in development and testing.
The library now (IFCT) has weak functions, one for events(), and one for raw canbus output (after the hardware filters)...
Since you have both controllers going to the same callback, you may differentiate the messages using msg.bus
Ex, to setup a 2-way gateway between 2 busses at same or different speeds a single line is all thats needed...
1) Fixed output with <B>INary numbers showing where Time was represented as <B>INary instead of <D>ECimal.
2) Added <W>indow spacing support, to look more like a console by having the text shifted up instead of down....
It's fine for separate ports, just not the same. If your going to use the same port, a mutex lock is required. I must mention though, do NOT use a mutex in an ISR, you WILL deadlock if it's locked elsewhere in loop().
...
You can get 5V 30A aluminum epoxy sealed powersupplies off fleabay, I use these with Teensy, the inputs are 8-40 volts, the output is 5V 30A
Pay close attention to the output listed, alot of those powersupplies have...
yes every time you press it it reloads the last compiled code, try recompiling again with the fixed code or blink code, then press the program button, should work :)
Yes if the bad code hard locks up the teensy on boot, the program button will force it into programming mode to help you reprogram it with good code
The last compiled code will be the one sent to teensy when you push...
IFCT sniffer demo has been updated with more helpful prints!
1) ASCII text is now shown in both <M>ain and <O>pen modes.
2) Time between frames is listed now to show how often the frame is triggered.
3) <T>...
I just added binary support to the CAN sniffer (B<enter>), this allows you to see the data as binary allowing you to see the exact bits being toggled when reverse engineering vehicles. This is alot easier to see than...
Added another demo of IFCT sniffer using Serial as input.
Led toggles on every input.
https://github.com/tonton81/IFCT/blob/master/examples/IFCTsnifferSerialInput/IFCTsnifferSerialInput.ino
Valid inputs are:
...
Awesome work Mike! :)
Hey everyone I'm currently writing a CAN sniffer to help reverse engineer vehicle data using the console screen, the data is very smooth, ordered, and I even added a count for the catched...
i doubt rf or wifi would be included on the onboard production due to size constrain and having effect on price point. You should have your own boards for that. For alot of people, 1-2 uarts isn’t enough, plus it...
if you look at BZ1 and BZ2 in back of PCB, you will see a trace going out of them, they most likely would be the correct place to put the ground wire between the module and teensy’s GND, BZ1 and BZ2 on other side of PCB...
im on my phone so its hard to help, or look at its eagle files, but on their site, i check front and back of that board with zoom, i dont see a trace of that pin being brought out, pretty sure it’s pass through
you are actuallly supposed to do nano.begin(Serial1) and then do nano.baud(38400), sorry i see now you used Serial1 way below in sketch, use nano.begin(Serial1) first :)
looks like ur doing it right, might just be a...
I uploaded a few very simple demo's to help people get up and running using the native functions of IFCT, using interrupts or polling as well.
IFCTsimpleFIFOPolling
IFCTsimpleFIFOwithInterrupt...
The acceptance filter printout has been updated on github: https://github.com/tonton81/IFCT/commit/01c373331523bb3aeeb112e6af6ed1f0f3a017c8
Due to the amount of IDs that could be captured in TableC using a quad ID...
Here is the output when I call upon 3 mailboxes
Can0.acceptedIDs(MB8);
Can0.acceptedIDs(MB9);
Can0.acceptedIDs(MB10);
Mailbox: 8
In standard frame format, only the 11 most significant bits (28 to 18)...
Table A is finished, here is the output for it:
FIFO Table A:
Specifies an ID to be used as acceptance criteria for the FIFO. In the standard frame
format, only the 11 most significant bits (29 to 19) are used...
I'm currently adding FIFO support to the acceptedID() acceptance filter since mailboxes are currently only implemented. I think I am pretty much done with table B then I will have to work on Tables A and C.
The...
Find latest posts