This is expected if they are separate nodes, though, that communicate by gige (as on the diagram), it was already discussed.yup totally missed that. That log only shows one set with the six cores.
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
This is expected if they are separate nodes, though, that communicate by gige (as on the diagram), it was already discussed.yup totally missed that. That log only shows one set with the six cores.
I am also speculating that Tesla is betting on that the current unit is sufficient for EAP and some FSD functionality which will be sufficient for some time. They will then do an upgrade for those who paid for FSD when needed, and also switch to the next generation (Xavier) at some point.
Really nothing in production? That's hypocrisy. You attack others for speculation but that's all you do other than shill for mobileye.
Tesla has a system of hardware and sensors that they are convinced is adequate for Level 5 in production and in customer's hands - and has for more than six months.
Others have, Volvo for example went from pilot Assist 1 to 2 with a software update.They're also the only player in the game with a history of significant capability improvements to the fleet to firmware upgrades.
eAP may be Level 2 now, but that's subject to change at any time. Unless Tesla is badly confused about the potential of the system, what makes you think they won't have a level 3 capability in restricted environments like Audi is promising by the time the Audi and Nissan cars with that are actually released? That would then roll out to all cars built since last October if they have the eAP and FSDC options...
Beat me to it. Yes, it's expected if they are separate nodes. Another thing I should add is that if "lb" really stands for "load balancer", the two nodes may even be practically identical.This is expected if they are separate nodes, though, that communicate by gige (as on the diagram), it was already discussed.
no, I am practically convinced lb is some sort of a dumb gps thingie.Beat me to it. Yes, it's expected if they are separate nodes. Another thing I should add is that if "lb" really stands for "load balancer", the two nodes may even be practically identical.
Yes, figuring what lb is would really help. The only thing I'm worried about in terms of going the software route to figure the configuration out is if Tesla left the other SoC unused for EAP, then that may not show up in the software.no, I am practically convinced lb is some sort of a dumb gps thingie.
I plan to research it in more detail real soon now
In AP2-cars, the GPS-signal from the antenna in the trunk lid terminates directly in the AP2ECU ("PX2") on a dedicated connector. How the "PX2" processes and sends this to the MCU is a big mystery thus far. All I know is that the Ublox device in the MCU is a LEA-6R-0-001 in AP1-cars. (BTW in AP1-cars, the antenna cable terminates directly in the MCU.) That said, the MCU was not updated with AP2, so it should be the same GPS-module. The latest code dump from @verygreen mentions Ublox:OT, Anyone know what Ublox device they are using?
# CONFIG_SERIAL_UBLOX_GPS is not set
Yes, but the reference board has the Tegras on one side, and the two GPUs on the other side, which require cooling (heatsinks/fans) on both sides:
FIRST PICTURES - Tesla Autopilot 2.0 ECU (Nvidia PX 2)
The Tesla board seems to only have one heatsink on the top side with two 80mm fans, and based on what can be seen from outside it is in my opinion too small for a 2x Tegra + 2x GPU setup (or anything else powerful that require a lot of cooling).
Neither can I, that's why I started this thread allready back in DecemberI can't wait for the first person to post photos of the board.
Dang this thread just exploded while I was sleeping
In AP2-cars, the GPS-signal from the antenna in the trunk lid terminates directly in the AP2ECU ("PX2") on a dedicated connector. How the "PX2" processes and sends this to the MCU is a big mystery thus far. All I know is that the Ublox device in the MCU is a LEA-6R-0-001 in AP1-cars. (BTW in AP1-cars, the antenna cable terminates directly in the MCU.) That said, the MCU was not updated with AP2, so it should be the same GPS-module. They did update the antenna, though.
I totally agree with @bjornb here.
First off, one needs to understand the difference between the "Autochauffeur" and "Autocruise" boards:
"Autocruise" only consists of a "Parker" chip, which has 6 CPUs (2 x Denver + 4 x Coretex A57) and an integrated GPU (iGPU). This chip is also known as Tegra X2 or T186.
"Autochauffeur" has that times two (i.e. two "Parker" chips, totalling 12 CPU cores and 2 iGPUs). ADDITIONALLY it has two discrete GPUs (dGPUs) -- probably MXM 3.1s -- mounted on the flip side of the board. Each of these two dGPUs is accompanied by dedicated video memory @4GB (Elpida W4032BABG-60-F). Check this out: Need for Speed. In conclusion: "Autochauffeur" (the so-called full board) is not merely a double "Auocruise" board - it's far more than that.
The enclosure pictures taken by me, @bjornb and others show that the board is mounted almost flush with the bottom of the steel/aluminium enclosure. Not much room for dGPUs on the bottom! Also, where's the cooling for these?
Certainly Tesla has a very modified version of the PX2, if it really can be called PX2 at all. Elon certainly didn't mention PX2 in his press conference speech. Yet Nvidia has boasted that it is indeed a PX2 in there.
Neither can I, that's why I started this thread allready back in December
@lunitiks Re the board, I just heard from a reliable source that on the AP board there are two nvidia chips. "one big, one small", the big one is on a daughterboard similar to cid, small one is on the main board.
Pictures do exist, but my source cannot release them.
Not quite Teslas I/Os are totally different from Nvidias dev board. Tesla uses a combination of Rosenberger 59Z115 (double connectors), Rosenberger 59Z113 and D4Z001 (single connectors), plus a couple of Japanese(?) connectors like Sumitomo 6098-5611 and 6098-4008. Furthermore, the Tesla unit does not have a OBDII-connector, SD-slot or the "double decker" USB-port.The Tesla unit seems to be a combination of the two: it has the inputs of the Autochauffer reference board but a form factor (and CPU count) that suggests Autocruise.
Not quite Teslas I/Os are totally different from Nvidias dev board. Tesla uses a combination of Rosenberger 59Z115 (double connectors), Rosenberger 59Z113 and D4Z001 (single connectors), plus a couple of Japanese(?) connectors like Sumitomo 6098-5611 and 6098-4008. Furthermore, the Tesla unit does not have a OBDII-connector, SD-slot or the "double decker" USB-port.
"Counting I/Os" actually gets you nowhere. According to this source (see p. 6), the Autocruise variant is able to "connect & fuse data from up to 8 cameras", plus radar and lidar. I've seen pictures of the Autocruise with two and three camera connectors.
Teslas AP2ECU is custom indeed
On your pictures there's an odd space next to usb-c that looks like sdcard slot that was just not put in placeNot quite Teslas I/Os are totally different from Nvidias dev board. Tesla uses a combination of Rosenberger 59Z115 (double connectors), Rosenberger 59Z113 and D4Z001 (single connectors), plus a couple of Japanese(?) connectors like Sumitomo 6098-5611 and 6098-4008. Furthermore, the Tesla unit does not have a OBDII-connector, SD-slot or the "double decker" USB-port.
The sticker just tells you Teslas part no (1078321-XX-X).Did any of your pics have Nvidia's SKU on them? Can see a sticker on one but cant read it.
Yes this is true. Same thing on this Autocruise dev board (see bottom right):On your pictures there's an odd space next to usb-c that looks like sdcard slot that was just not put in place
How does discussing mobileye which is a big part of tesla history equates to shilling and no they have a L2 system in production.
Tesla and Elon has made outlandish claims like these every time and have failed to deliver. The only thing in customers hands is a L2 system. Infact it was only like last month that partial payment from EAP were recognized. FSD payments haven't even been recognized yet.
Unlikely because tesla actually said: "That said, Enhanced Autopilot should still be considered a driver's assistance feature with the driver responsible for remaining in control of the car at all times."
I think what alot of people are confused about is what EAP actually is. Alot will be surprised that Its not based on FSD code development, for lane changing on highway for example, its simply replacing the usage of ultrasonics with the two rear cameras. EAP is only meant to accomplish the promises of AP1 that never happened. Smart Summon will also do what summon was promised to do and also on-ramp/off-ramp, etc. EAP is literally a glorified AP1.
All I know is that the Ublox device in the MCU is a LEA-6R-0-001 in AP1-cars. (BTW in AP1-cars, the antenna cable terminates directly in the MCU.) That said, the MCU was not updated with AP2, so it should be the same GPS-module. The latest code dump from @verygreen mentions Ublox: