The *control board* (which is where you connect the power) is designed to gracefully handle and meter both positive and negative rails. In other words, it was designed to be able to handle a future expansion module which is capable of negative rails. It does currently need at least one of the rails to be positive, but fixing that shortcoming is on the future features list.
As, the current injection board is descended from the syncinjector, it can only utilize positive rails. If you were to hook up +24 +48 and -48 to the control board, the injection board would happily coexist with the -48VDC rail, but would only be able to power from the +24V or the +48V rails. At some future date there will most likely be a version of an injection board which will utilize -48VDC gracefully. I don't want to be very forthcoming on that part of the roadmap for various reasons including the fact it isn't very much firmed up. But, yes -48VDC native support is on my radar. In relation to the din rail unit... it has fallen victim to the phrase 'pick your battles'. We had our hands full with this rack injector and I heard far more people asking about it than the din unit. Once this is shipping and settles down a bit, we'll be circling back to both the 12 port din rail unit and also cambium sync. Timing of those products is currently up in the air. There is a good chance I'll do cambium sync first for the rackinjector, then figure out how to fit it into the din rail product line. On Mon, Jan 30, 2017 at 6:43 PM, George Skorup <[email protected]> wrote: > So... three power rails. Cool. Are the returns isolated? Is your thinking > +12, +24 and +48 rails? Or what I'm asking is, is a -48 rail a possibility? > +24, +48 and -48 would be awesome. > > The thing that I would've liked to have seen is a SiteMonitor exp. port so > I could add a module or two, like the 2-relay/3-switch to monitor the Traco > BCMs and other basic stuff. Or if you'll have cards to do some of these > things, then I'm fine with that. I don't really have many sites that need > 16 POE ports anyway. > > Still interested in the DIN rail 12 port PowerInjector+Sync as well. In > fact, I could use the shit outta that right now. > > On 1/30/2017 9:30 AM, Forrest Christian (List Account) wrote: > > Yes. Currently there is only one board type for the slots... You will be > able to order it with any number of slots filled - the rest will have > blanks put in place. It is designed so end users can add, remove or swap > each board. > > The current board is essentially our current powerinjector+sync in that > form factor - 4 ports, each jumperable for any gigabit-compatible power > scheme, and each jumperable to select one of the three voltage input > sources. > > There are two additional board types on the drawing board. The one most > interesting to my existing customers will add support for cambium sync > which is compatible with the 450i and 450m. > > > > On Mon, Jan 30, 2017 at 8:12 AM, That One Guy /sarcasm < > [email protected]> wrote: > >> is this mix and match for the 4 slots? >> >> On Mon, Jan 30, 2017 at 8:35 AM, Forrest Christian (List Account) < >> [email protected]> wrote: >> >>> For those eagerly waiting for the RackMount Injector.... >>> >>> The engineering validations I mentioned before have been completed. I >>> discovered one minor board error, which has been corrected. I also took >>> advantage of the additional board revision to make another minor circuit >>> revision which will improve performance. At this point, what we hope are >>> the final verification boards are on order. Because of how minor the >>> revision was to the boards, we have decided to go ahead and release this to >>> part purchasing - which basically means we're buying everything we need to >>> actually build these. We should be able to validate the final board >>> revision and have actual production boards here before all of the other >>> parts arrive. This will also give us a chance to modify the circuit board >>> if we discover a parts availability issue during the purchasing process. >>> >>> We've issued almost all of the purchase orders for parts for the first >>> production run - we're now waiting for final confirmation of delivery >>> dates. I expect these this week, with the caveat that in a couple of >>> cases we're dealing with the non-joys of trying to get things done during >>> China's spring festival holiday. At least one vendor is shut down >>> completely until the 3rd, and I'm sure there will be a bit of backlog when >>> everyone returns to work. >>> >>> Once I have confirmed orders with estimated ship dates and validated >>> pricing for almost everything, I'll get the unit up on the website to do >>> pre-orders with a semi-definite ship date. At this point, I'm guessing >>> either just before or just after WISPAMERICA. We're hoping for just >>> before since I would much rather tell people that the product is shipping >>> than explain why it isn't. But the reality is that there isn't much time >>> before WISPAMERICA so I'm guessing I'll be explaining. >>> >>> One more teaser image is attached. >>> >>> -- >>> *Forrest Christian* *CEO**, PacketFlux Technologies, Inc.* >>> Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602 >>> [email protected] | http://www.packetflux.com >>> <http://www.linkedin.com/in/fwchristian> >>> <http://facebook.com/packetflux> <http://twitter.com/@packetflux> >>> >>> >> >> >> -- >> If you only see yourself as part of the team but you don't see your team >> as part of yourself you have already failed as part of the team. >> > > > > -- > *Forrest Christian* *CEO**, PacketFlux Technologies, Inc.* > Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602 > [email protected] | http://www.packetflux.com > <http://www.linkedin.com/in/fwchristian> <http://facebook.com/packetflux> > <http://twitter.com/@packetflux> > > > -- *Forrest Christian* *CEO**, PacketFlux Technologies, Inc.* Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602 [email protected] | http://www.packetflux.com <http://www.linkedin.com/in/fwchristian> <http://facebook.com/packetflux> <http://twitter.com/@packetflux>
