#CAN bus transceivers

[johu2buss]

https://www.futureelectronics.com/p/semiconductors--comm-products--can/mcp2551-e-sn-microchip-8463747

High-Speed CAN Transceiver, CAN Transceiver, Ethernet controller

MCP2551 Series 5.5 V 1 Mb/s Surface Mount High-Speed CAN Transceiver - SOIC-8

[bitstream24]

ESP32 Development Kits with Onboard CAN Bus Controller

The ESP32 includes a CAN Bus controller compatible with the NXP SJA1000, making it compliant with the CAN 2.0B (ISO 11898, also known as Classical CAN) specification.

Nevertheless, as with the SJA1000, the ESP32 CAN Bus controller only provides the data link layer and the physical layer signaling sublayer. As a result, an external transceiver module is needed to convert the ESP32's CAN-RX and CAN-TX signals into CAN_H and CAN_L bus signals.

[knet2thorn]

https://www.futureelectronics.com/p/semiconductors--comm-products--i2c/pca9532pw-118-nxp-5033862

16-bit I2C-bus LED Dimmer, Embedded communication, image processing,

PCA9532 Series 5.5 V 350 uA 400kHz SMT 16-bit I2C-bus LED Dimmer - TSSOP-24

[rbrte2don]

https://www.futureelectronics.com/p/semiconductors--comm-products--can/mcp2551-i-sn-microchip-5584800

Can Power Systems, Ethernet controller, High-Speed CAN Transceiver

MCP2551 Series 5.5 V 1 Mb/s Surface Mount High-Speed CAN Transceiver - SOIC-8

[rch2llardd]

https://www.futureelectronics.com/p/semiconductors--comm-products--can/mcp2551t-i-sn-microchip-5971353

High-Speed CAN Transceiver, can transceiver circuit, Can Power Systems

MCP2551 Series 5.5 V 1 Mb/s Surface Mount High-Speed CAN Transceiver - SOIC-8

[stlle2ista]

https://www.futureelectronics.com/p/semiconductors--comm-products--i2c/pca9532pw-118-nxp-5033862

I2c bus, Embedded communication, Isolated CAN Transceiver ICs

PCA9532 Series 5.5 V 350 uA 400kHz SMT 16-bit I2C-bus LED Dimmer - TSSOP-24

[red2nichs]

https://www.futureelectronics.com/p/semiconductors--comm-products--can/mcp2551-i-sn-microchip-5584800

Radio Management Products, High-Speed CAN Transceiver, can transceiver circuit

MCP2551 Series 5.5 V 1 Mb/s Surface Mount High-Speed CAN Transceiver - SOIC-8

[tobiasdrake]

There's no getting away from it now, bucko. We have our killer pegged.

He could still be a co-conspirator, but unlikely. Servan was necessary for the bombing ploy, since he must have designed the bombs and the fancy transceiver. Especially if Icardi wasn't selling out to Amaterasu and this was, in fact, a Resistance leadership coup.

Which, at this time, seems the most plausible explanation. Even if it doesn't explain the minigame runaround.

But while Servan most certainly was involved, it's not clear what Margulaw would have even contributed if he had been complicit. There's nothing to suspect him of, and by extension no reason to suspect him.

Iruka is by far the most "not possible to be involved" out of the entire group. Completely out of the question.

And while I do think that Servan was involved in the bombing, he can't have made the jump. He also couldn't have shot Shachi from an equal height. Have you seen his stature? He's like three and a half feet tall.

My first thought had been that he's an Amaterasu fink, but at this point, I feel like that possibility can be eliminated. If he was working with the Peacekeepers to create an excuse for wiping out the Resistance, he could have left through the door and high fived his fellow cops on the way out.

Instead, he went for this elaborate escape mechanism so he could vanish from a district that's utterly saturated in jackboots. Fubuki and I had more than a few run-ins with them. So. No. He can't be in Amaterasu's pocket.

The other explanation is that he wanted control of the Resistance. He was spinning a narrative. "Unfit leader Shachi launched a terrorist threat against Kanai Ward and tried to murder civilians. Peacekeepers swarmed his hideout and cornered him. With no way out, he took his own life. I, Icardi, will better lead our organization into a far more prosperous future!"

This was a coup.

That could explain the minigame runaround too. To make his coup work, he needed only a terror threat, not a full-scale terror attack. He needed the first bomb to detonate in order to disguise the sabotage at the power plant. After that, easily disarmed bombs in fairly out-of-the-way locations with a supremely generous time limit would ensure that nobody was seriously harmed.

Icardi may have disagreed with Shachi's leadership, but I don't think he was a polar-opposite bomb-chucking anarchist stereotype.

A distraction. It's the smoke disguising Icardi's coup, creating a reason for Peacekeepers to raid the Resistance HQ.

That's also why Servan phoned in an anonymous tip to CTU. They wanted everyone to know that Yuma Kokohead is launching terror attacks against the city, in the name of the Resistance.

Sabotaging the power plant in order to create the escape channel they'd need, following their coup, of course. While Servan was manipulating Yuma and phoning tips to CTU, Icardi had to be on-site at the power plant to set the drainage bomb as well as to sabotage the valve handle and keep the water flowing.

Oh, we're moving towards the final confrontation? Huh.

Maybe Servan is innocent? That seems unlikely. He designed the camera-bombs and the transceiver-disarming device, and has a noted history of being a bomb specialist. Then he gave Yuma the transceiver signal that would arm the bombs and set everything in motion.

It's hard to imagine that he's unrelated to these events.

What. Talk fast, man, 'cause that's gonna be a hard fucking sell.

Yeah, I'm gonna stop you right there because that's not what you did. You didn't make it look like Peacekeepers shot him. You made it look like he shot himself, in a fit of ideological despair. You're spinning bullshit right now and I'm not buying it.

Also that. But he might have assumed an evacuation of Marunomon would have prevented anyone from being hurt. There was enough time, while it was taking place, for two separate alerts in the form of printed-out paper documentation to be distributed among power plant staff, so it's not like a huge wave of water buried the district in seconds. The flooding happened gradually.

In order to be effective, an act of protest must be disruptive. I could see Shachi believing that flooding the economic district would be a massively disruptive demonstration against Our Capitalist Overlords with low risk of harm to human life.

Problem is, Icardi's claim of "I made it look like the Peacekeepers did it" doesn't hold water.

...hang on, what? Yuma, where are you going with this?

Oh my god, it was a bank robbery.

I was fucking joking when I proposed that. WHAT. WHY. WHAT.

...why would he even need to kill Shachi to make that happen? How could that possibly contribute to pilfering safes from Marunomon? What the actual fuck?

Once he already had Yuma running around town disarming bombs and CTU chasing down Yuma as well as rooting out the Resistance in Dohya, he could just. Like. Go to the Power Plant and do the thing. Shachi's death is completely unnecessary. This makes no sense.

Apparently Servan was totally uninvolved somehow despite clear reasons to suspect his involvement! It was you and only you! The world's dumbest overcomplicating bank robber who got caught because he tacked on a pointless murder for shits and giggles!

[techav]

Introducing Wrap030-ATX

New Boards Day!

They're here!

This is a project that has been a long time coming, and something I have wanted to do for a long time.

This is the largest, most complex PCB I have ever designed — a 9.6x9.6 inch (244x244mm) square, 4-layer, complete motherboard for my MC68030 homebrew computer project.

It is designed to support the Motorola MC68030 CPU, MC68882 FPU, two 72-pin SIMM sockets, 512kB ROM, two serial ports, one parallel port, PS/2 keyboard, 4-bpp VGA video, IDE hard drive, and three ISA expansion slots. A complete system all in a microATX form factor.

This builds on my previous work with the 68030, based heavily on my wire-wrap project and the boards that followed. It's a project over four years in the making. I have made a few improvements on the old design, like 16550-compatible serial ports and an updated memory map to support much more RAM in a contiguous space.

Keeping with my existing system designs, I've combined most of the logic into a set of CPLDs. This makes things like PCB layout and logic debugging so much easier. Most of the remaining discrete logic on the board is 74'245 bus transceivers for driving memory and the ISA slots.

I've kept the name "wrap030" in honor of the project's origin as a wire-wrapped prototype, despite the move to proper PCBs. It's just what I've been calling the project in my own head (and design files) all this time, so at this point no other name would feel right.

I of course wasted no time starting to assemble one, but I did stop myself from getting too carried away with the soldering iron. I want to be methodical and test each section before moving on to the next.

I have already found one major error in my board layout — the footprint for the VGA connector is backwards. I may need to bodge together some kind of adapter.

So far I've confirmed the minimalist AT power supply section works with no major shorts on power supply rails, and the reset circuit is working as expected. Next step is to try a free run test with the CPU to ensure the system clock and CPU are working. Once that is confirmed working, I can start loading logic for accessing ROM. My goal is to have it at least running BASIC on a serial terminal by VCFSW in June.

I've forked my existing wrap030 repository on GitHub for this new Wrap030-ATX, since it does make some breaking changes that will require updates to logic and programs. New repo is here:

[bitstream24]

Teensy 4.0 CAN FD And LIN Bus Breakout Board For Automotive Applications

This is a CAN FD breakout board for use with the Teensy 4.0 (included in the scope of delivery). It comes with an onboard 5 VDC regulator with reverse voltage protection and a CAN FD transceiver. The LIN Bus connection is provided by the Microchip MCP2004A chip. The Teensy is a complete USB-based microcontroller development system, compatible with Arduino software and libraries. It comes in a minimal footprint, capable of implementing a great variety of projects. All programming is accomplished via the onboard USB port.

[ainow]

Buy CP2102 USB to TTL MODULE at Affordable Price in Ainow

CP2102 USB to TTL MODULE

This is the CP2102 USB to TTL module UART serial converter. This is a great little tool for embedded systems that require a serial connection to a computer. The board can simply attach to a USB bus and will appear as a standard COM port. This CP2102 USB to TTL Module doesn’t require any external oscillator, it onboard-board voltage regulator, and it even uses a reprogrammable internal EEPROM for the device description. The full hardware UART has flow control for baud rates from 300bps to 921600bps. This breakout also allows you to connect the TX/RX pins of your favorite microcontroller or serial application to the RX/TX pins of the breakout, creating a simple serial cable replacement.

Supported operating systems:

Windows 98/Me/2000/7

MAC OS-9

MAC OS

X-Windows CE

Linux 2.40 or later

Features:

Brand new and high quality

Included USB transceiver, without external circuit device

Includes a clock circuit and power-on reset circuit

With 3.3V and 5V dual power output

With three LEDs: power indicator, data reception indicator, the data transmission indicator, working status

Meet the USB2.0 specification requirements

SUSPEND pin supports USB suspend state

With self-recovery fuse. In the event of the accidental short circuit, it can effectively protect your computer USB port and Downloader

With reset signal output, etc. directly to the Arduino board Promini download!

Asynchronous serial data bus compatible with all handshake and modulation controller interface signals

The supported data format is 8 data bits, 1 stop bit and parity bits

Connotation 512 byte receive buffer and 512 bytes transmit buffer

Supports hardware handshaking or X-ON/X-OFF

[dorleco]

Error Detection And Correction In CAN

June 3, 2024

by dorleco

with no comment

eMOBILITY CONTROLS

Edit

INTRODUCTION

Communication is vital in the ever-evolving world of automotive technology. Modern automobiles are outfitted with a variety of technical components that must work seamlessly together. One of the foundations of this communication is the Controller Area Network (CAN), a robust and dependable protocol that allows data to be sent across different components. However, mechanisms for error detection and correction in CAN are required to maintain this reliability. In this blog article, we will go extensively into the topic of error detection and repair in CAN, understanding how important these procedures are in ensuring the safety and dependability of modern vehicles.

The significance of CAN in contemporary automobiles

Before we go into error detection and correction in CAN, let’s look at how it works in modern automobiles.

What exactly does CAN stand for? The Controller Area Network, a robust serial communication protocol, enables vehicle electronic control units (VCUs) to connect. Why is it important? By allowing real-time data sharing between ECUs in charge of activities like as engine control, transmission management, and safety systems, CAN has emerged as the core of automotive communication.

1. The vulnerability of CAN.

Even though CAN is extremely reliable, errors can still occur. Several factors can result in communication mistakes, including:

Noise and interference: The electromagnetic interference created by multiple electrical components in the vehicle environment, which is noisy, can contaminate CAN signals. Defects in transceivers or other hardware components can cause CAN communication problems.

Electromagnetic Compatibility (EMC): Communication issues might arise when different ECUs and components are not compatible.

2. Basics of Error Detection in CAN

Various types of error detection CAN mechanisms are utilized to ensure dependability.

The Cyclic Redundancy Check (CRC) algorithm generates a checksum based on the transmitted data. To detect errors, the receiving node computes its CRC and compares it with the transmitted CRC.

The FCS field of the CAN frame, like the CRC, contains checksum information that is used to detect errors.

Bit Stuffing: You can use bit stuffing to ensure that the sender and receiver are in sync. The bit packing pattern may deviate, indicating an issue.

3. Error Correction in the Can

Error Detection in CAN is necessary, but it is not always sufficient. Error-correcting methods go one step further:

Retransmission: If an error is detected, the sender sends the message again. This ensures that the message is appropriately delivered to its intended recipient.

The CAN protocol includes an acknowledgment mechanism that allows the receiver to acknowledge that a message was properly received. If no acknowledgment is received, the sender retransmits, assuming an error.

4. Error Recovery and Handling.

It is critical to understand how to handle CAN faults and recover to assure system dependability.

Error Flags: CAN uses error flags to identify a variety of issues. These warning flags help you discover and fix problems. Error Passive and Error Active Modes: Depending on the number of errors detected, CAN nodes can switch between error passive and error active modes. This reduces the risk that errant nodes may disrupt the network as a whole.

5. Advanced Error-handling Strategies

Advanced error-handling mechanisms are occasionally utilized to ensure continuous communication.

Fault-Tolerant CAN (FTCAN) is a redundancy-based method that uses two CAN buses running concurrently to ensure that communication continues even if one bus fails. Flex Ray is a communication standard for automotive networks that improves error management; however, it is not a CAN protocol.

6. Security and Error Detection in CAN.

As linked and autonomous vehicles become more common, security concerns have grown. It is vital to understand how error detection relates to security.

Cyber security: To avoid unwanted access and manipulation, robust error detection in CAN and repair mechanisms are required. Malicious attacks on CAN networks are a possibility, emphasizing the need for these measures.

Intrusion Detection Systems: Advanced intrusion detection systems are being integrated into CAN networks to identify and respond to security threats.

7. Future Error Detection and Correction in CAN

The Future of Error Detection As vehicles get more intricate and networked, there are exciting improvements in CAN and CAN correction.

AI-based machine learning algorithms can help discover and rectify problems in real-time, as well as adjust to changing situations and threats.

Blockchain Technology: Researchers are looking into how blockchain may be used for tamper-proof and secure data collection and transfer.

Conclusion

The Heartbeat of Contemporary Vehicles

In conclusion, the Controller Area Network (CAN) is the unsung hero of modern automobiles because it enables critical electrical component communication. Error detection in CAN and corrective methods are unheralded heroes who fight behind the scenes to ensure that this communication is trustworthy, secure, and safe. The importance of effective error management in CAN will only grow as vehicles evolve and incorporate new technology. It’s critical to get from point A to point B safely, effectively, and with the confidence that all of your vehicle’s systems are working properly. This is made feasible by error detection in CAN and repair, which will remain critical to the industry’s future progress.

[tobiasdrake]

The final camera. Tension continues to build. Who's going to die? How? Why?

Yup. Here we are. Setting up a secret spycam at the entrance to an all-girls' school for what Shachi assures me are definitely freedom-fighting reasons. Most certainly.

On the plus side, that camera is super visible, especially when you consider the stairs leading up offscreen to my right, giving people an easy vantage from which to see the poorly-concealed cam. Yuma didn't even bother to try and stick it in the bushes.

So there's a strong chance that, within a couple days, someone will stomp on it while screaming "FUCKING PERVERT." An assessment that I'm not entirely sure I disagree with.

None of these places seem to be bustling with police activity, which makes me really suspicious about why you sent me here, bruh.

Sure, I can call and let him know it's done. We'll see if he picks up. He has a pretty high chance of being either the killer, the victim, or the falsely-accused by Amaterasu in this case. For a man of his grand importance, who we've been told has one of two guns in play on his person, and who is the nicest cinnamon roll ever to lead a rebellion? Yeah, there's no way he's going to be a mere witness.

Plus he seems to know a lot about homunculi, which is either good or bad for his chances for survival. If he lives, he can tell us things like Kurumi did. But if he dies, he can take his knowledge with him and leave us fumbling around in the dark some more.

...oh, or maybe Serval is trying to kill us in order to tie up loose ends. That's also a possibility. I'll admit, I did not see that coming.

Wait, is Shachi's transceiver going to explode? I thought that meant ours was going to explode.

Well. Fuck. The game is afoot. That happened abruptly. Serval is immediately suspicious, but in that "too suspicious" sort of way. Like, the only person who could possibly be responsible for this is Serval, which makes Serval's culpability way too obvious to be true.

Yeah, I didn't think we were crossing two separate districts in five minutes' time. Okay, time to go find Shachi's smoldering corpse and begin asking the questions. Like. Why was he in the phone booth where we planted the first cam?

But there doesn't appear to be a body in it. So maybe the bomb wasn't Shachi's transceiver. Maybe the cameras are the bombs.

That would explain the bizarre placements, if the Resistance wants to do some shock-and-awe property damage bombings but without hitting any civilians in the process. These are all in locations that are remote enough that they could be detonated without hitting anyone but close enough that people would notice.

Like, if they wanted to kill people, we'd set the bomb inside the cafe. Not at a bus stop outside the cafe.

Y'know what? I support this. They're making a public spectacle and being disruptive without hurting anyone in the process. This is way better than anything they might have done with those cameras.

I assume they probably still have a camera built-in, so Serval can tell when there's no one in the blast radius.

...okay, so they just got lucky that there was no one in the blast radius. My bad.

My dude isn't wrong when he suggests that there will be casualties on the road to revolution. In a fascist dictatorship, there are few if any non-violent roads to change, and violent means lead to violent consequences.

But he's saying it with the Wicked Bad Guy tone and language, so he's obviously talking about the Resistance killing civilians rather than rallying soldiers to die for liberation. You know how media is. "Anti-fascists are JUST AS BAD as the fascists! Maybe worse!" Writers sure do love their aggressive centrism.

Which brings us right back around to "Meet the new boss, same as the old boss." This is not a democracy. These people have no power over their government, and their government is cruel and corrupt enough to not care about collateral damage. There is nothing to be gained by targeting civilians for reprisal.

[techav]

Wrap030-ATX First Tests

The best place to start with assembling and testing a board like this is the power supply. If there's a catastrophic error, like a direct short between supply rails, it's best to find out before wasting other components. Thankfully on this project, I'm using a standard PC power supply so all I need is some basic filtering capacitors. Not much to screw up there except maybe some backwards electrolytics.

Next is generally reset and CPU clock. These are essential for getting the CPU up and running and should be confirmed operational before continuing. Here again I'm using stock modular components — a brownout reset signal generator and a can oscillator — so debugging was minimal.

Finally, the CPU should be tested with these signals to see if it will free run (tie the CPU data bus to a known value, usually something like 0b00000000, and watching to see if the address bus increments freely).

The CPU free run test is an important one. It confirms the most basic functions of the board and the CPU are functional. A board that can't free run at this stage likely has some significant problem that must be solved before anything else will work.

Luckily, it passed this test!

I used the data bus transceiver sockets to attach test wires to, so I could tie all the data bus signals low. On the 68k architecture, $0000,0000 corresponds to the instruction ORI.b #0,D0 which is a 16-bit opcode ($0000) for an OR instruction followed by an immediate constant word ($0000). So for every 32-bit bus access, the CPU is fetching one complete instruction, incrementing the Program Counter by 4, then repeating. The result of the instruction is stored in the D0 register, so nothing is ever written to the bus.

This behaviour can be confirmed with a logic analyzer, but it's easiest to visualize by connecting LEDs to some of the higher address bits and watching them count up in binary (which is what I did here).

On the 68030 there is a bit more to do than just grounding the data bus. In particular, the CPU's asynchronous bus expects peripherals to report they are ready and have placed valid data on the bus by asserting the Data Strobe Acknowledge signals (DSACKn#). In normal operation, the system will delay asserting these signals to give the peripheral device enough time to do its job, signalling the CPU to insert wait states until the data is ready. For free run though, these signals can be tied low to signal to the CPU that the data it's requesting (all 0s) is ready immediately (because the data bus is tied to ground).

Here is where a last-minute addition to my PCB layout really came in handy. I removed the solder mask on these small sections of important signal traces so I would have a clear place to probe these signals on the top of the board. This also gave me just enough room to solder some 30 gauge wire to the DSACKn# and address signals for running the free run test.

Now that I know the most basic functions of the board are working, I can move on to the next step — running first code. To run real code I'll need ROM working, which will also require the bus controller CPLD to be minimally functional.

I am hoping to have this project at least running BASIC in time to exhibit it at VCF Southwest in Dallas at the end of June this year. I've got a lot of work still to do to reach that goal, but passing these first tests does give me hope that there are no huge show-stopping problems with my PCB (at least nothing that can't be worked around with a bodge wire or two)

[bitstream24]

Dual-CAN Shield for Arduino Due

This shield is a prototyping module specifically designed to support the CAN Bus capability on the Arduino DUE. The board includes dual CAN transceivers required by the two integrated CAN ports on the DUE, and also provides a large prototyping area. The shield is pin-for-pin compatible with the Arduino DUE and features a 3.3 VDC bus, 5 VDC bus, SOIC breakout, full digital breakout, CAN termination resistors, and terminal blocks for CAN connections.

[roadrunnerposting]

tonight i will scope the SPI and CAN bus either side of the can controller-transceiver pair and see if it seems to be doing anything